resourceType and resourceDiscriminator
Starting with Collibra version 2024.10 we deprecated the resourceType field that is part of Resource and ResourceReference objects and their accessor methods, in favor of resourceDiscriminator.
Both fields have the same logical value but different data types:
resourceType:- Returns an
enumvalue. - Returns
BaseDataTypefor traits and any newly added resource types.
- Returns an
resourceDiscriminator:- Returns a
stringvalue. - Returns
Traitfor traits.
- Returns a
Backward compatibility
The introduction of the resourceDiscriminator field is necessary to ensure backward compatibility while we add new resource types as part of the evolution of the platform. Adding new values to an enum list is not considered backward compatible as it poses challenges to existing integrations that must regenerate their client libraries or fail to recognize the newly added values.
The deprecation of the resourceType field means your current applications continue to work without the need to replace the deprecated field with the new field until you are ready to do so.
Some APIs may still expect resourceType as an input field without having an alternative available as we are in the process of updating them. Once the updates are complete, you should also update your integrations to use resourceDiscriminator.