Defining the E-Commerce Datastore
Since all tables of the ecommerce schema are present in an Dore_Ecommerce
database, we
need a way to define details of the MySQL database in the Manifest.
Datastores
In Dore, Datastores represent data sources. It usually represents a particular database, whether that's a database running within a locally installed MySQL server, a remote Elasticsearch cluster, or a hosted MongoDB database.
Let's add the datastores
object in the manifest:
This will contain definition for the Dore_Ecommerce
MySQL database.
Defining the ecommerce
Datastore
Datastores are configured at $.datastores
in the Manifest, i.e, inside the datastores
object we added above. Each
datastore is defined with a key which will be the ID for the Datastore and value as the
Datastore Definition.
Let's add the ecommerce
datastore to our Manifest:
dore-ecommerce-manifest.json | |
---|---|
In the snippet above, we have defined a datastore with ID ecommerce
. We will add the definition for
Dore_Ecommerce
database within this object.
Protocol
Each datastore must specify a protocol
which
indicates the type of system the datastore represents. In our case, the datastore represents a mysql
database.
Let's specify that ecommerce
datastore uses mysql
protocol:
dore-ecommerce-manifest.json | |
---|---|
Properties
We also need to define certain protocol specific properties for a datastore which allows Dore to interact with the underlying system:
dore-ecommerce-manifest.json | |
---|---|
These properties specify details which Dore uses to identify, connect, and interact with the Dore_Ecommerce
MySQL
database represented by the Datastore.
Please provide details for your MySQL instance for the host
, port
, user
, and password
fields above.