Extend maximum recommended datapoints in TimeseriesDataExport

[hernil]

You hit the limit of 10000 datapoints - some data may be omitted

When selecting a broad enough span of time together with a high enough resolution of data points one may run into this limitation. It is sort of unclear where this limit originates.

Our use case requires export of hourly data, usually ten years back in time. Some back of the napkin math dictates that is pushing the ~90k mark of datapoints per timeseries.

Some explenation of the 10 000 point limit would be good as a starting point so we can help looking into potential bottlenecks!

[mrtraser]

SDK doesn't support ability to request more than 10 000 points for now, so it is nothing we can do here. We need to wait for backend implementation of this feature.

[muradsater]

Was this requested against Cognite / SDK team?

[polomani]

The ticket was created on DEVX board DEVX-195 but we might be blocked by api

[nalaka]

@hernil @polomani @mrtraser @muradsater - Since from DEVX-195 it seems that this should be handled in the JS SDK, I am closing this for now. Please reopen if we need to handle this inside Gearbox.

[polomani]

Please, don't close this issue, it's an ongoing problem. And since it's not prioritized on sdk yet, we might need to implement it on the component here

And it's quite important for @hernil project

[nalaka]

@polomani & @hernil - shall we implement doing multiple queries and aggregating the results in TimeseriesDataExport component itself then?

Also we still need a maximum that our component will handle - is 100,000 enough?

I think we may be able to incorporate this into our next sprint if confirmed.