Split large table into smaller query over netconf

[mghosh]

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.

Regards,

[josephm]

Xpath predicates should do what you want… see e.g. https://www.w3.org/TR/1999/REC-xpath-19991116/ and position()…

By updating your get(-confg) request paths to something like:

/path/to/huge-list[position() < 100]

(note < vs < 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…

[mnovak]

Related also to this question:

Is it possible for netconf to retrieve partial list from data-provider?

In our implementation, the max elements of list is 65535 and the server providing the data would take much time to update the stutus before send the data to data-provider. Is it possible for netconf to only retrieve partial list, e.g. 20K~30K?