Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
@Juan Alvarado The scenario where you have a view B that implements A, the current behavior is that property x will be included in the output for both views now if it is selected for just one of the views in the query - and we are changing this so that it will only be included for the view where it is selected. Meaning if you select property a from the A view and property x from the B view, the query output will include only property a from the A view and property x from the B view, while currently you will get property a and x from the A view and property x from the B view.Thanks,-AndersM
Hi!CDF Data Modeling does not support specifying the sorting the output of aggregation queries at this time.Thanks,-AndersM
Hi again,We have ongoing development work on improving the representation of time series data in data modeling, While I cannot yet commit to a release date for this I believe we will have an improvement that may fill in some of the described requirements in an upcoming CDF release. Don’t hold your breath just yet, though, if you need this urgently then using the existing time series API is the recommended workaround.Thanks,-AndersM
Based on the available information this is just as likely to be an issue with the calling service and/or its network connectivity. Actionable data for us would be requestids in failure responses from the CDF API services, or if that is not available or a response is not received at all, timestamps and other details (URL, request method and headers) of requests to CDF that fail.
Hi Sangavi,Edit: Last response was probably wrong.Currently, if you need to work with time series extensively, consider the time series REST API, either directly (https://developer.cognite.com/api/#tag/Time-series/operation/listTimeSeries) or via an SDK such as the Python SDK - https://cognite-sdk-python.readthedocs-hosted.com/en/latest/core_data_model.html#list-time-seriesThanks,-AndersM
Hi!While there is no explicit support for joblib in the Cognite Python SDK, there’s also no need to have that to benefit from joblib and the Python SDK together. Simply use both in your code as you normally would. As the Joblib documentation states. Joblib’s philosophy is to keep the underlying algorithm code unchanged, avoiding framework-style modifications.The details would depend on your use case, naturally, but in general applying joblib to your code should not interfere with the SDK.Thanks,-Anders M
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.