Hi community,
We have an SNMP table. Cube flags an error saying the table contains over 100k rows and no more rows will be added. Is there a way to handle such cases in case the user needs to have all rows?
Fenta Alemahu [SLC] [DevOps Enabler] Selected answer as best 2 days ago
The warning should also prompt a reflection on whether a table is the right format to present this data. Why does the user need access to all rows? How will they use this information?
Would it be sufficient to only display rows that include a tunnel name, while keeping the full SNMP table (presumably) in SLProtocol with RTDisplay set to false? By marking the table as volatile and setting RTDisplay = false, the limit is approximately 1 million (see RN39836 mentioned in another answer)
Laurens Moutton [SLC] [DevOps Enabler] Posted new comment 2 days ago
To further add to that: hopefully the table has the partialSNMP option added to poll the table in smaller chunks, as described here https://docs.dataminer.services/develop/schemadoc/Protocol/Protocol.Params.Param.SNMP.OID-options.html#partialsnmp