Replies posted by Thomas Sjølshagen

118 Replies

P
Committed
Pedersen Jon-RobertCommitted

Cognite Data Fusion: Add metadata on RelationshipsClosed

Thank you for the request @Pedersen Jon-Robert Your input has been added to our product management prioritization tool (Productboard) for evaluation.

6
Anita Hæhre
Seasoned Practitioner
7 months ago
Ben Brandt
Seasoned
Ben BrandtSeasoned

Cognite Data Fusion: Document Contract/Expectations of a Cursor Returned From The APIImplemented

When a nextCursor value is returned from an API call, is this cursor value valid forever or does it expire? Unless we change something in the api w.r.t content in the cursor, or encryption key, it is valid forever. Doesn’t store info like cluster, project or filter parameters. I.e. it’s “valid until it breaks”. If it expires, how long is it guaranteed to be valid? (This documents part of the contract of the API.)Doesn’t expire, but we’re considering the viability of making it time out (maybe an hour without accesses = let it expire ..?)When we call an API subsequent times with the same parameters and provide a cursor value, are we getting data at the time of the current API call or cached data from the first time the API was called with those parameters? Not using a cached copy of data so if you use a cursor but change the parameters, the API might serve data you’re not expecting.If subsequent calls to the API with a cursor are NOT returning results of a cached copy and data has been i

5
C
Seasoned Practitioner
1 year ago
R
Seasoned
RobersoSNSeasoned

Cognite Data Fusion: I want to maintain versions of my data-products in CDF.Gathering Interest

@RobersoSN Thank you for summarizing the insight. We’ve captured similar insights and will add this in our Productboard for processing in the context of our Flexible Data Modeling initiative.

3
Shakya Ganguly
Practitioner
1 year ago
A
Seasoned
Andreas KimsåsSeasoned

Cognite Data Fusion: Bigger maximum limit on description fieldGathering Interest

@Andreas Kimsås - Is there an average size of the description field where you typically would not need to truncate the data?

2
T
Practitioner
1 year ago
R
Seasoned
RobersoSNSeasoned

Cognite Data Fusion: Deprecate internal-ids from all objects in the CDF APIs.Planned for development

Hi Robert, This is a request we have captured as part of previous discussions with y’all. Thank you for the additional detail.

4
Anita Hæhre
Seasoned Practitioner
1 year ago
Ben Brandt
Seasoned
Ben BrandtSeasoned

Cognite Data Fusion: Support Dates Prior to 1970 in API and Python SDKImplemented

It seems logical that the API would be able to support the same range of timestamps that the underlying codebase supports. Agreed @Mark Felder. We do need to make sure we’re not breaking anything when we allow dates based on the fully refactored, multi-cloud support capable software stack that is now underlying the Time Series API. The constraints w.r.t to dates prior to 1971 are from the old stack (which we migrated off of before the holidays). So we’re having to plan some work in order to implement support for dates prior to 1971 and up to (potentially) Dec 31. 2150.

9
Anita Hæhre
Seasoned Practitioner
1 year ago
Ben Brandt
Seasoned
Ben BrandtSeasoned

Cognite Data Fusion: Support Dates Prior to 1970 in API and Python SDKImplemented

Hi Ben,This is actually an API limitation that the Python SDK steps into.We do not currently support timestamps prior to Jan 1st, 1971 for a time series (so “no” to your 2nd question).The underlying codebase can support timestamps from 1900 to 2150, but changing the API is being evaluated (impact to the API, existing solutions, etc).I’m creating a ticket for the request so our engineers can start thinking more structured about it, and describe possible workarounds, etc. Thank you for the report! 

9
Anita Hæhre
Seasoned Practitioner
1 year ago
Ben Brandt
Seasoned
Ben BrandtSeasoned

Cognite Data Fusion: Document Contract/Expectations of a Cursor Returned From The APIImplemented

Thanks Ben! Will both create a ticket so we can update documentation / clarify, and respond with some answers after I’ve collected authoritative responses across the teams.

5
C
Seasoned Practitioner
1 year ago
A
Practitioner
Anders AlbertPractitioner
asked in Developer and User Community

Support for 100 requests in Cognite-SDK

Hi @Anders Albert,I’ve added your feedback as a bug report in our internal ticketing system, against the Python SDK. Engineering will consider the impact of modifying the current behavior, and can update this topic once we know more about if/how and when we may be able to address it. Sorry about the delay in getting back to you!

3
A
Practitioner
2 years ago
Ben Brandt
Seasoned
Ben BrandtSeasoned
asked in Developer and User Community

Similar to 365d-ago for historical, how do we specify relative time for future?

Additionally, we have a feature defined to expand short notation for data point retrieval to support the same notation for the past as well (i.e. negative short notation values). It’s in the Product Management queue for consideration in 2H2022, but we do not have an explicit schedule, nor a committed plan for delivery right now.

4
Ben Brandt
Seasoned
2 years ago
Ben Brandt
Seasoned
Ben BrandtSeasoned

Cognite Data Fusion: Full Support for Auth0 as Identity ProviderPlanned for development

Hi @Ben Brandt,Thank you for the insight and feedback!At present, our focus is to enhance our Azure AD (AAD) support. Auth0 is one of the options we’re considering in the context of expanded IdP support, but we do not currently have that specific expansion planned and committed for an upcoming CDF release.Your feedback and request will be added to help us prioritize IdP support expansion relative to other Cognite Data Fusion platform enhancements.

7
Anita Hæhre
Seasoned Practitioner
7 months ago
R
Seasoned
RobersoSNSeasoned
posted in Developer and User Community

Flexible time-series models

Hi @RobersoSN, Has Cognite done any exploration around flexible time-series modelling? Not sure I’m following what you’re asking for when you say “flexible time-series modelling”? Which aspect(s) of the model(s) should be flexible?Are we talking about flexible in terms of operations on two or more time series? Things like merge/combine, split, persist merged/combined? Update independent time series, but reflect the updated data in pre-existing merged “product” of two or more time series where the merged product includes the time series that were updated?Persisting computed time series from data in one or more existing time series?Something else altogether?

2
R
Seasoned
2 years ago
A
Seasoned
Andreas KimsåsSeasoned
asked in Developer and User Community

How to overcome metadata key length and max keys limitation

@Andreas Kimsås Sorry, this slipped my mind!We’re looking at how/whether we have the capacity to include expanding the metadata key length to 256 in one of the upcoming releases, but won’t know which until the team commits in one of the upcoming planning sessions. As for key charset, a quick scan of our sources indicate we use UTF-8.

11
T
Practitioner
1 year ago
H
Seasoned
henning.kvinneslandSeasoned
asked in Developer and User Community

Fallback for missing values when calculating synthetic timeseries

Hi and thank you for the insight @henning.kvinnesland ! I’ve added this problem as “Product Feedback”  here on the Hub.Please upvote and provide any additional commentary you may have there, so we can be sure to include the information in our discovery and assessment process for Time Series and Synthetic Time Series.

2
O
Committed
2 years ago
A
Seasoned
Andreas KimsåsSeasoned
asked in Developer and User Community

How to overcome metadata key length and max keys limitation

Hi @RobersoSN, really sorry about the (super) tardy response!The time series documentation is incorrect wrt to the number of metadata keys (i.e. the limit isn’t supposed to be 16). The actual limit is supposed to be 256 key/value pairs and I just got a PR to update the docs for time series and sequences to: Limits: Maximum length of key is 128 bytes, up to 256 key-value pairs, of total size of at most 10000 bytes across all keys and values.For events we believe we may be able to increase the key length to 256 bytes without adverse effects, if that might help a little? Obviously doesn’t address the value related workarounds you’re referring to! What pitfalls should we be aware of for this solution? We support up to 128 000 bytes for the value side, but anything above 8K (8192 bytes) will not be sortable or filterable. For those cases, you will get all of the data in the value field returned.  Or, are there any access management tools for segregating databases in RAW There are not, and w

11
T
Practitioner
1 year ago
R
Seasoned
RobersoSNSeasoned
posted in Developer and User Community

The cognite python SDK should batch requests that violate API constraints

Thank you for the input Robert!This seems like a reasonable thing for the SDK to be capable of doing, so I’ve added your insight to Productboard and will link it to a feature/idea for the Python SDK to more dynamically handle API limits (batching/chunking and back-off with appropriate warnings if necessary).  We will likely need more information as we investigate ideas on how to implement the functionality and hope it’s OK to reach out as needed?

3
R
Seasoned
2 years ago
A
Seasoned
Andreas KimsåsSeasoned
asked in Developer and User Community

How to overcome metadata key length and max keys limitation

We haven’t got immediate plans around expanding our metadata capabilities (field lengths, nesting, etc) for time series, but I have added this information as insights for our product development prioritization process so we can do some discovery across customers for needs/expectations/problem sets to solve for. Will also update this thread as we progress.

11
T
Practitioner
1 year ago
A
Active
Abusdal MortenActive
asked in Developer and User Community

Get latest TimeSerie entry for a node/collection of TimeSeries

Hi Morten,At this time, unfortunately, we do not have a simple way of getting the last recorded value of a Time Series, except by scanning through the entire series as you describe. I’m adding this insight to our product requirements board for analysis and prioritization. PS: I’m assuming you’ve seen and are referring to something more advanced than the getLatest ( …/timeseries/data/latest) endpoint. - https://api.cognitedata.com/api/v1/projects/{project}/timeseries/data/latest 

1
T
Practitioner
2 years ago

Badge winners

Show all badges
Terms & ConditionsCookie Settings