Hi!Almost three years ago we made a feature request regarding search. Specifically we want to:Have support for paging. Do grouping on metadata-fields. Define which fields yields relevance to the search-results. Inclusive search-terms using AND instead of OR.I do understand that satisfying the search-requirements of all your users is a daunting task, but perhaps it would be easier to let us do the job instead? I believe it would be very beneficial if we were able to access ElasticSearch directly in some manner.And please keep in mind that the data itself defines relevancy. No two customers are alike and therefore a good generic solution likely doesn’t exist. @Knut Vidvei @Andreea Pastinaru
More details here: https://github.com/cognitedata/react-auth-wrapper/issues/15Perhaps it could be removed all together?
It would be really nice if we could control these log-messages in a more granular way:
Browser is none too happy: https://github.com/cognitedata/auth-wrapper/issues/19
What is best practice for global error-handling in the JS-SDK?
Hi! If one or more of the source-timeseries are missing data-points they will also be missing in the synthetic timeseries output..We would like an option to default to zero for missing values so that the API will use the available values to calculate a partial result. Example:TS1: [1,2,3]TS2: [3, undefined, 4] Output now if calculating a sum of TS1 + TS2:[4, undefined, 7] What we would like:[4, 2, 7]
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
