The .jar usage (not installation) doesn't depend on an operating system. It is meant to be used either in a Java application or in a database visualizer tool (for example, DBVisualizer) where your own Java code can make use of the Java classes from the JDBC driver we provide, or a third party tool can use the driver in a standardized way (the JDBC spec) to access Elasticsearch.
The JDBC drivers (not only ours) are specific to a certain database type. So Elasticsearch-SQL JDBC driver will "talk" to an Elasticsearch cluster only. It's like an interface that translates SQL queries to Elasticsearch queries.
If you'd like to test Elasticsearch-SQL, you could just send REST request (using curl for example) to Elasticsearch using the SQL API. Alternatively, if you'd like just to play with some data without setting up Elasticsearch yourself, you could start with https://demo.elastic.co. There is some preloaded data in there and from the main page you could click on Query it button from the Elasticsearch SQL box in the welcome page.
Oh my god is complicated elasticstack. Splunk is much easier. OK then I'll try it over the restAPI.
Your instructions are only for professionals. Where do I enter the remote address of the SQL Server? What needs to be changed on a Windows SQL Server for the request?
I'm sorry if I implied something else, but our JDBC driver works only with Elasticsearch. The same goes for other JDBC drivers created by other providers for their own data bases (MySQL has its own jdbc driver, SQL server the same etc).
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.