The SingleStore connector allows querying and creating tables in an external SingleStore database. This can be used to join data between different systems like SingleStore and Hive, or between two different SingleStore instances.
To configure the SingleStore connector, create a catalog properties file
etc/catalog named, for example,
mount the SingleStore connector as the
Create the file with the following contents, replacing the
connection properties as appropriate for your setup:
connector.name=singlestore connection-url=jdbc:singlestore://localhost:3306 connection-user=root connection-password=LbRootPass1
connection-url defines the connection information and parameters to pass
to the SingleStore JDBC driver. The supported parameters for the URL are
available in the SingleStore Connection String Parameters.
connection-password are typically required and
determine the user credentials for the connection, often a service user.
Multiple SingleStore Servers#
You can have as many catalogs as you need, so if you have additional
SingleStore servers, simply add another properties file to
with a different name (making sure it ends in
example, if you name the property file
will create a catalog named
sales using the configured connector.
The SingleStore connector provides a schema for every SingleStore database.
You can see the available SingleStore databases by running
SHOW SCHEMAS FROM singlestore;
If you have a SingleStore database named
web, you can view the tables
in this database by running
SHOW TABLES FROM singlestore.web;
You can see a list of the columns in the
clicks table in the
using either of the following:
DESCRIBE singlestore.web.clicks; SHOW COLUMNS FROM singlestore.web.clicks;
Finally, you can access the
clicks table in the
SELECT * FROM singlestore.web.clicks;
If you used a different name for your catalog properties file, use
that catalog name instead of
singlestore in the above examples.
SingleStore Connector Limitations#
The following SQL statements are not yet supported: