Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
When creating a Cognite Function you specify the dataset it belongs to, as an example lets say D2 LCI, then the files of the function is stored as files in that dataset. However, as D2 LCI is a dataset for file storage for engineering documents these function files cause noise, not much but still. If you were to list out all files for the dataset these “internal” CDF files would simply show as regular files and would have to be filtered out.
Now, as we (AkerBP) are moving away from the asset-centric and over to data modelling this might not be an issue given how data models and spaces are. But in the future when datasets are a thing of the past, how will function and the like work, where will those files be stored. Storing the file used for compute with the data they compute might be a simple implementation, but not ideal as it does cause some noise.
Note: this does not only apply to Cognite Functions, but to all CDF features where “internal” files are stored alongside the regular data.
