Say a device have very large number of entries (in millions) that need to be exported over NETCONF. Exporting such a big data at one go (and that too periodically) causes a performance penalty.
Conceptually this can be averted if manager can query for next N elements starting form a last known key. So one large query can be split into smaller queries of N elements.
Is there anyway to provide this query count and starting key etc over NETCONF rpc requests? Are there any other ways to achieve the same.
Xpath predicates should do what you want… see e.g. https://www.w3.org/TR/1999/REC-xpath-19991116/ and
By updating your get(-confg) request paths to something like:
/path/to/huge-list[position() < 100]
< due to escaping special XML characters…)
and subsequent request for:
/path/to/huge-list[position() > 99 and position() < 200]
etc. should give you sort of “batch” processing…
Related also to this question: