These Relationship objects are stored in a catalog, which enables FeatureByte to efficiently serve features or feature lists that involve multiple entities. Features and feature lists can be served by either their primary entity or any serving entities (descendants) thanks to the Relationship object collection in the catalog.
To list the Relationships in the catalog, use the
To retrieve a specific relationship using its Object ID from the catalog, use the
If you discover a relationship that should not be used for serving features or feature lists, you can disable it with the