Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
When installing pygen in a CDF notebook you may be met with ValueError: Requested 'typing-extensions>=4.10.0; python_version < "3.13"', but typing-extensions==4.7.1 is already installedThis is currently a known bug, which we are working on solving. For now, the workaround is to manually uninstall `typing-extensions` using micropip. The code to do so is documented in the installation of pygen along with other known issues and solutions.
The recently released version `7.37.0` of the Python-SDK which pygen depends on broke pygen. This is fixed in `0.99.20`. For versions before 0.99.20 you will be met with `ImportError: cannot import name 'ListablePropertyType' ...` when you try to generate an SDK.
We are pleased to announce that cognite-pygen is available in beta. What does Pygen enable? It enables you to write python-code using the concepts in your data model. The code you can write enables you to query CDF and work with the data in your data model. How? Pygen generates a Python-SDK tailored for your data model. Want to know more? https://cognite-pygen.readthedocs-hosted.com/en/latest/what_is_pygen.htmlDisclaimer! In the beta period, we ask you to be careful when using the pygen generated SDK on a live production project.We would love to get feedback on how to improve the usability and robustness of the pygen. Toward General Availability, we will focus on robustifying the generation process.
Main ChangesThis is a rework of the terminal output of `cdf-tk deploy` and `cdf-tk clean` to provide better information about what happens. This change takes effect with and without also passing the flag `--dry-run`.In addition, both these commands now support `--drop-data` which is independent of `--drop`, so that you can for example, drop all datapoints from a timeseries without deleting the timeseries itself.Examples of running the deploy commandRunning the commandcdf-tk deploy --dry-run --env devWill now output two tables:And:Adding verbose will give more details about exactly which resources will be changedcdf-tk --verbose deploy --dry-run --env devPart of the new outputExample of running cleanRunning the commandcdf-tk clean --env devOutputs the same two tables with the summary of the opertion
I would like to have an option for an idempotent option for the Cognite Client. For example, I can add the same asset multiple times without rising an exception.Use Case: I have a script (running on a schedule in Cognite Functon) which dynamically create an asset hierarchy. Current behavior: If I try to add a list of assets in which one asset is existing in CDF, then no new assets are appended to the hierarchy and an exception is raised.Desired behavior: An option for suppressing the raised exception and add the new assets to the asset hierarchy.``client.assets.create(new_assets, skip_existing=True)``
Currently when fetching datapoints from multiple timeseries, the Python Cognite-SDK splits up the requests into one request per timeseries, while the underlying CDF API supports up to 100 timeseries per requests. This slows down fetching multiple timeseries, which is a problem when you display multiple timeseries (or aggregated of timeseries) in a frontend application.
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.