Package io.debezium.metadata
Class CollectionId
java.lang.Object
io.debezium.metadata.CollectionId
An abstract data model that represents a table or collection of a datastore in its hierarchy.
(e.g. server/catalog/database, schema, table).
It can either have two levels (namespace and name) or three levels (realm, namespace and name), depending on the requirements of underlying datastore:
realm: The optional highest layer, used for datastores that have a concept of three layers. For example MySQL and Oracle have database, schema and table, where database would be the highest layer and will be represented by realm.
namespace: The second-highest layer, used for datastores that have a concept of three or two layers. For example MySQL and Oracle have database, schema and table, where schema would be the second layer and will be represented by namespace. PostgreSQL only has schema and table, then schema will be represented by namespace.
name: The lowest layer, used for datastores that have a concept of three, two or one single layer hierarchy. This is usually the table layer of a relational database or the collection in MongoDB or similar datastores (e.g. document stores, key-value stores), this layer will then be represented by name.
Also acts as model class representing the structure of the response for the REST Extension call that returns the matching tables/collections on the `validate filters` endpoint.
It can either have two levels (namespace and name) or three levels (realm, namespace and name), depending on the requirements of underlying datastore:
realm: The optional highest layer, used for datastores that have a concept of three layers. For example MySQL and Oracle have database, schema and table, where database would be the highest layer and will be represented by realm.
namespace: The second-highest layer, used for datastores that have a concept of three or two layers. For example MySQL and Oracle have database, schema and table, where schema would be the second layer and will be represented by namespace. PostgreSQL only has schema and table, then schema will be represented by namespace.
name: The lowest layer, used for datastores that have a concept of three, two or one single layer hierarchy. This is usually the table layer of a relational database or the collection in MongoDB or similar datastores (e.g. document stores, key-value stores), this layer will then be represented by name.
Also acts as model class representing the structure of the response for the REST Extension call that returns the matching tables/collections on the `validate filters` endpoint.
-
Field Summary
Fields -
Constructor Summary
ConstructorsConstructorDescriptionCollectionId(String name) CollectionId(String namespace, String name) CollectionId(String realm, String namespace, String name) -
Method Summary
-
Field Details
-
namespace
catalog, schema or replica set name -
name
table or collection -
realm
optional database or schema name
-
-
Constructor Details
-
CollectionId
-
CollectionId
-
CollectionId
-
-
Method Details