When i try to connect the elastic search jdbc river plugin with postgres or h2 db to get the data into the elastic search engine, it behaves properly.
But in case of informix it always give this kind of error :-
java.sql.SQLException: No suitable driver found for jdbc:informix-sqli:
even after i put the jar file into the plugin/jdbc folder.
can anybody has any idea on that.
The issue was with the Jar, I had all the 6 jars but the thing wat elastic search engine accepts a jar in specific way which means jar should contail Meta-Inf->services->jdbc.sql.Driver, which was not there so explicitly I had mension the driver name in the elastic search configuration. which is
set JAVA_OPTS=%JAVA_OPTS% -Djdbc.drivers=com.informix.jdbc.IfxDriver
Related
I am trying to query couchbase from within JMeter in mac.
I downloaded connector-couchbase-10.0.2.jar. I put the jar file in the jmeter lib folder. I have the couchbase URL of my org and I can connect to it and query it directly.
I put the couchbase uRL in the jmeter JDBC Connector Configuration element. However, it is not clear what to put in the JDBC Driver class.
I keep getting the error message "“Cannot load JDBC driver class”. Any idea what should I do? Is there a way to add the couchbase connector through the JMeter Plugins Manager?
I appreciate any clues to this.
Add also connector's dependencies to JMeter's lib folder
Dependencies teiid-api, teiid-common-core, jboss-connector-api_1.7_spec, couchbase-api, java-client,
Use JDBC Driver as cdata.jdbc.couchbase.CouchbaseDriver, see couchbase JDBC docs
Provide the JDBC URL. For example:
jdbc:couchbase:User='myusername';Password='mypassword';Server='http://couchbase40'
or
jdbc:cdata:couchbase:User='myusername';Password='mypassword';Server='http://couchbase40'
I want to know if there's a way to configure the datasource for Ignite as Elastic Search. I was browsing the web. But I did not find a solution.
I want to implement this integration for a Java application.
If I understand your idea correctly there's a way to do it. As far as I can see Elasticsearch supports SQL table-like data access and it's available through jdbc connection. From the Ignite's side we have 3rd party persistance, it uses jdbc to connect to an underlying store system. To be honest I haven't tested it but I suppose it should work.
Also I need mention that you can use GridGain WebConsole to generate simple Ignite project from existing jdbc connection. This functionality could be found on Configuration tab -> Create Cluster Configuration.
I am trying to connect to Elastic Search 5.4.2 .
I am using spring-data-elasticsearch 3.0.0.M4.
I get the below exception when i connect to the elastic search instance
Exception in thread "main" NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{ZJchkKLgRUGzjUP_cG7z9g}{102.21.31.52}{102.21.31.52}]]
at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:348)
at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:246)
at org.elasticsearch.client.transport.TransportProxyClient.execute(TransportProxyClient.java:59)
at org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:366)
at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:408)
at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:397)
at org.elasticsearch.client.support.AbstractClient$IndicesAdmin.execute(AbstractClient.java:1250)
at org.elasticsearch.client.support.AbstractClient$IndicesAdmin.exists(AbstractClient.java:1272)
I used to get similair error when i was working with lower versions of Elastic Search ( 2.3.3 ) . Mostly it would be related to incompatible version of elastic search and spring data elastic search
I would like to view the logs in order to know the root cause of the error.
I am not able to enable logs for org.elasticsearch package.
If I configure the log4j.xml , I am able to view the spring data logs but elastic search logs are not showing up ? Has anybody faced similar issue ?
I was browsing through the elastic search source code and could not find much logger statements ( esp . in org.elasticsearch.client.transport ) . Do they have minimal log statements ?
I am developing a Question answering application and for that I need to use neo4j and elasticsearch in the same maven project. I am using elasticsearch to make my application more robust.
As we know that neo4j and elasticsearch works on different version of lucene, so whichever version I include in dependency, it gives an error.
Here is what I am doing:
First elasticsearch will index the data and the data and relationships will be stored as graphdatabase using neo4j. Then the user will input as a query, through which the data will be retrieved with the help of indexes. This data will be trigerred in graphdatabasev using trigger score which will be then propagated along the graphdatabase to find relevant results according to the user query.
Is there any way that I can integrate neo4j and elasticsearch in same maven project, or is there any other way through which these two modules can interact seperately.
Thanks
Please check out our integration page:
http://neo4j.com/developer/elastic-search/
Which has some discussion and also an example project to get you started.
http://github.com/neo4j-contrib/neo4j-elasticsearch
I am trying to integrate Apache Nutch 2.2.1 with Elasticsearch 0.90.11.
I have followed all tutorials available (although there are not so many) and even changed bin/crawl.sh to use elasticsearch to index instead of solr.
It seems that all works when I run the script until elasticsearch is trying to index the crawled data.
I checked hadoop.log inside logs folder under nutch and found the following errors:
Error injecting constructor, java.lang.NoSuchFieldError: STOP_WORDS_SET
Error injecting constructor, java.lang.NoClassDefFoundError: Could not initialize class org.apache.lucene.analysis.en.EnglishAnalyzer$DefaultSetHolder
If you managed to get it working I would very much appreciate the help.
Thanks,
Andrei.
Having never used Apache Nutch, but briefly reading about it, I would suspect that your inclusion of Elasticsearch is causing a classpath collision with a different version of Lucene that is also on the classpath. Based on its Maven POM, which does not specify Lucene directly, then I would suggest only including the Lucene bundled with Elasticsearch, which should be Apache Lucene 4.6.1 for your version.
Duplicated code (differing versions of the same jar) tend to be the cause of NoClassDefFoundError when you are certain that you have the necessary code. Based on the fact that you switched from Solr to Elasticsearch, then it would make sense that you left whatever jars from Solr on your classpath, which would cause the collision at hand. The current release of Solr is 4.7.0, which is the same as Lucene and that would collide with 4.6.1.