![]() |
VOOZH | about |
The CData ODBC drivers expand your ability to work with data from hundreds of data sources. QlikView is a business discovery platform that provides self-service BI for all business users in an organization. This article outlines simple steps to connect to Elasticsearch data using the CData ODBC driver and create data visualizations in QlikView.
The CData ODBC drivers offer unmatched performance for interacting with live Elasticsearch data in QlikView due to optimized data processing built into the driver. When you issue complex SQL queries from QlikView to Elasticsearch, the driver pushes supported SQL operations, like filters and aggregations, directly to Elasticsearch and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze Elasticsearch data using native QlikView data types.
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.
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
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.
When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
The steps below supply the results of an SQL query to a visualization in QlikView. In this article, you will create a bar chart with the query below:
SELECT Orders.Freight, Customers.ContactName FROM Customers INNER JOIN Orders ON Customers.CustomerId=Orders.CustomerId
ODBC CONNECT TO [CData Elasticsearch Sys];
SQL SELECT Orders.Freight, Customers.ContactName FROM Customers INNER JOIN Orders ON Customers.CustomerId=Orders.CustomerId;
Where possible, the SQL operations in the query, like filters and aggregations, will be pushed down to Elasticsearch, while any unsupported operations (which can include SQL functions and JOIN operations) will be managed client-side by the CData SQL engine embedded in the driver.
๐ A script that connects and executes an SQL query. (Salesforce is shown.)Finish the wizard to generate the chart. The CData ODBC Driver for Elasticsearch connects to live Elasticsearch data, so the chart can be refreshed to see real-time changes. Live connections are possible and effective, thanks to the high-performance data processing native to CData ODBC Drivers.
๐ A chart populated with the results of a query. (Salesforce is shown.)Download a free trial of the Elasticsearch ODBC Driver to get started:
Download NowLearn more:
๐ Elasticsearch IconThe Elasticsearch ODBC Driver is a powerful tool that allows you to connect with live Elasticsearch document databases, directly from any applications that support ODBC connectivity.
Access Elasticsearch like you would a database - read, write, and update through a standard ODBC Driver interface.