![]() |
VOOZH | about |
There are a vast number of PostgreSQL clients available on the Internet. PostgreSQL is a popular interface for data access. When you pair PostgreSQL with CData Connect AI, you gain database-like access to live Elasticsearch data from PostgreSQL. In this article, we walk through the process of connecting to Elasticsearch data in Connect AI and establishing a connection between Connect AI and PostgreSQL using a TDS foreign data wrapper (FDW).
CData Connect AI provides a pure SQL Server interface for Elasticsearch, allowing you to query data from Elasticsearch without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to Elasticsearch, leveraging server-side processing to return the requested Elasticsearch data quickly.
Accessing and integrating live data from Elasticsearch has never been easier with CData. Customers rely on CData connectivity to:
Users frequently integrate Elasticsearch data with analytics tools such as Crystal Reports, Power BI, and Excel, and leverage our tools to enable a single, federated access layer to all of their data sources, including Elasticsearch.
For more information on CData's Elasticsearch solutions, check out our Knowledge Base article: CData Elasticsearch Driver Features & Differentiators.
CData Connect AI uses a straightforward, point-and-click interface to connect to data sources.
Set the Server and Port connection properties to connect. To authenticate, set the User and Password properties, PKI (public key infrastructure) properties, or both. To use PKI, set the SSLClientCert, SSLClientCertType, SSLClientCertSubject, and SSLClientCertPassword properties.
The data provider uses X-Pack Security for TLS/SSL and authentication. To connect over TLS/SSL, prefix the Server value with 'https://'. Note: TLS/SSL and client authentication must be enabled on X-Pack to use PKI.
Once the data provider is connected, X-Pack will then perform user authentication and grant role permissions based on the realms you have configured.
๐ Configuring a connection (Salesforce is shown)When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
With the connection configured and a PAT generated, you are ready to connect to Elasticsearch data from PostgreSQL.
The Foreign Data Wrapper can be installed as an extension to PostgreSQL, without recompiling PostgreSQL. The tds_fdw extension is used as an example (https://github.com/tds-fdw/tds_fdw).
sudo apt-get install git git clone https://github.com/tds-fdw/tds_fdw.git cd tds_fdw make USE_PGXS=1 sudo make USE_PGXS=1 installNote: If you have several PostgreSQL versions and you do not want to build for the default one, first locate where the binary for pg_config is, take note of the full path, and then append PG_CONFIG=
sudo service postgresql start
psql -h localhost -U postgres -d postgresNote: Instead of localhost you can put the IP where your PostgreSQL is hosted.
After you have installed the extension, follow the steps below to start executing queries to Elasticsearch data:
CREATE EXTENSION tds_fdw;
CREATE SERVER "Elasticsearch1" FOREIGN DATA WRAPPER tds_fdw OPTIONS (servername'tds.cdata.com', port '14333', database 'Elasticsearch1');
CREATE USER MAPPING for postgres SERVER "Elasticsearch1" OPTIONS (username '[email protected]', password 'your_personal_access_token' );
CREATE SCHEMA "Elasticsearch1";
#Using a table_name definition: CREATE FOREIGN TABLE "Elasticsearch1".Orders ( id varchar, Freight varchar) SERVER "Elasticsearch1" OPTIONS(table_name 'Elasticsearch.Orders', row_estimate_method 'showplan_all'); #Or using a schema_name and table_name definition: CREATE FOREIGN TABLE "Elasticsearch1".Orders ( id varchar, Freight varchar) SERVER "Elasticsearch1" OPTIONS (schema_name 'Elasticsearch', table_name 'Orders', row_estimate_method 'showplan_all'); #Or using a query definition: CREATE FOREIGN TABLE "Elasticsearch1".Orders ( id varchar, Freight varchar) SERVER "Elasticsearch1" OPTIONS (query 'SELECT * FROM Elasticsearch.Orders', row_estimate_method 'showplan_all'); #Or setting a remote column name: CREATE FOREIGN TABLE "Elasticsearch1".Orders ( id varchar, col2 varchar OPTIONS (column_name 'Freight')) SERVER "Elasticsearch1" OPTIONS (schema_name 'Elasticsearch', table_name 'Orders', row_estimate_method 'showplan_all');
SELECT id, Freight FROM "Elasticsearch1".Orders;
Now, you have created a simple query from live Elasticsearch data. For more information on connecting to Elasticsearch (and more than 200 other data sources), visit the Connect AI page. Sign up for a free trial and start working with live Elasticsearch data in PostgreSQL.
Learn more about CData Connect AI or sign up for free trial access:
Free Trial