Skip to main content

This might be a basic question, but I often find myself uncertain about when to use CogniteDescribable in data modeling within Cognite Data Fusion.

For example, let's say we have domain tables in our data model, such as MaterialType, which contains data from SAP and defines the types of materials we work with (e.g., code and description). In this case, would it be appropriate to implement CogniteDescribable to reuse common properties like name and description?

What are the advantages of doing so? Does using CogniteDescribable provide any specific benefits—such as improved performance through indexing or partitioning—when used it containers?

In summary, should I always use CogniteDescribable in these types of scenarios, or are there cases where it's better not to?

​@Andre Alves I’ll check on this with the engineering team and get back to you with an update.

Hi, using CogniteDescribable is specifically beneficial when you use CDF user interaction tools, as the “apps” are built to use the CogniteDescribable properties in an efficient way. The “name” property is also already set up for indexing, so you don’t need to think about that in your modeling.

I typically extend from the Core Data Model concepts by default, unless the data is meant for “bulk transmissions” only.

Thanks ​@popdahl , this is for a specific domain data model and will most likely not use the Cognite apps. Really appreciate your help with this!

Reply


Terms & ConditionsCookie Settings