Versions Compared

Old Version 13

changes.mady.by.user Ahila P

Saved on

compared with

New Version 14

changes.mady.by.user Toine Siebelink

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DateParticipantsTopics

 

Toine Siebelink arne.chrestin Lena Peuker (DT) Ahila P Priyank Maheshwari Joe K 

  • Open Issues, Roadmap, resouring, Wow

...

 

Ahila P arne.chrestin Lena Peuker Toine Siebelink Andras Zoltan Kiss Joe K Levente Csanyi Luke Gleeson (Unlicensed) Seán Beirne Tony Finnerty 

  • Ahila P demonstrated her current solution based on storing prefix (module-name) upfront i.e as part of data in fragment table.
  • Pros
    • seems to work for all output use-cases
    • compatible with SDNC behavior (arne.chrestin confirmed too)
  • Cons
    • Client needs to specify prefix when using xPath requests
    • Backward incompatible
    • cpsPath (search) capabilities broken
    • Impacts on performance (unclear)
    • modulename prefix not per Yang RFX(see decision #5) above (TBC)
  • Actions
    • Toine Siebelink to check prefix v. modulename RFC guideline
    • Ahila P store 'xPath-with-prefixes' in a  new field in fragment table  to maintain backward compatibility
    • Ahila P break down required functionality in smaller user stories including
      • make xPath queries check both possible paths (with and with prefixes) if needed
      • use of prefixes with cpsPatrh functionality 
      • performance impact of new solution

Road Map 

Team agreed on 2 step approach (first step or short term solution was deemed unnecessary although some of the code develop as part of the PoC can be re-used in the 'proper' DB solution)

...