My earlier version of NEST used to support the following code for DeleteByQuery
ESClient.DeleteByQuery<object>(q => q.Query(q1 => q1.QueryString(qs => qs.Query("*"))));
Now, that the nugetPackage of NEST elastic version has changed to 2.0.4, I am unable to work using the existing code. Could anyone please let me know what could be replacement for it. My Elastic Search is version 1.5.1
Thanks
cmrhema
NEST 2.x is not compatible with Elasticsearch 1.x; there are breaking changes on the Elasticsearch side that are reflected as changes in NEST. The NEST github repository shows the compatibility matrix, which is essentially
NEST 1.x is compatible with Elasticsearch 1.x
NEST 2.x is compatible with Elasticsearch 2.x
and in prerelease, NEST 5.0.0-alpha1 is compatible with Elasticsearch 5.0.0-alpha1.
If you're using Elasticsearch 2.x, it is recommended to use NEST 2.3.1, as it contains a fix for a memory leak that exists in prior NEST 2.x versions.
DeleteByQuery is no longer part of Elasticsearch core in 2.x and is available as a plugin.
Related
I am trying to connect elasticsearch as output connector from apache ManifoldCF.Using elasticsearch 7.1.X version which is not working.
Can you suggest will maniFoldCF work with latest elasticsearch version ?
Tried configuring the repository and output plugin with elasticsearch. Executed a job but nothing turned up in elasticsearch.
Data should be crawled from repo to elasticsearch index. But its not happening with latest elasticsearch version.
The latest release of ManifoldCF was tested successfully for version 7.x. See this ticket:
https://issues.apache.org/jira/browse/CONNECTORS-1639
Looking at the output connector interoperability notes for version 2.15 (the latest as of this writing) the Elasticsearch connector was tested against 1.x instances Tested with ElasticSearch 1.0, 1.1, 1.2, 1.3 Included Connectors. Knowing of breaking changes in both ES 6.x and 7.x releases I would guess the connector will need some modifications to work with the latest 6, 7, and maybe even 5.x versions of Elasticsearch. Should be a relatively simple task to clone the default connector and make the changes to add support though.
I have more properties in 2.3.2 elastic search version. Now i am using 5.4.1. I have to use same index and properties in that version. Is it possible to restore the index and properties in simple way .
If you are migrating from version 2.3.2 to 5.4.1 you can definitely use the indices created in version 2.x, provided that no index was created in version 1.x.
Similarly while upgrading from 5.x. to 6.x. you have to make sure no index was created in version 2.x. or before, else you have to reindex
Have a look at this link:
link
I have copy of old data i.e. Elasticsearch 1.x, I want to migrate or reindex in Elasticsearch 5.x.
what are the methods and better way to do this ?
Elasticsearch is able to use indices created in the previous major
version only. For instance, Elasticsearch 5.x can use indices created
in Elasticsearch 2.x, but not those created in Elasticsearch 1.x or
before.
If you are running an Elasticsearch 2.x cluster which contains indices
that were created before 2.x, you will either need to delete those old
indices or to reindex them before upgrading to 5.x. See Reindex in
place.
If you are running an Elasticsearch 1.x cluster, you have two options:
First upgrade to Elasticsearch 2.4.x, reindex the old indices, then
upgrade to 5.x.
I would recommend to follow official guide from Elasticsearch by looking here - https://www.elastic.co/guide/en/elasticsearch/reference/current/reindex-upgrade.html#reindex-upgrade-remote, which should help you.
I am using Spring Data ElasticSearch 1.3.2 release, which comes with ElasticSearch 1.5.2 by default. Is it possible to upgrade to the latest version of ES (2.0) without breaking the Spring Data ES repository API ?
No. Due to several changes in the ES API this is not possible. Please see DATAES-211 for details.
The current unstable working branch can be found here: tree/DATAES-211-ES2.0
A feature in my project is already using 1.3 of elasticsearch and for new feature the plan is to use ES 2.2 also it is for some reasons that I cannot upgrade existing ES 1.3 to ES 2.2
Can one single version of elasticsearch client library (preferably 2.2) work with both versions of ES 1.3 and ES 2.2?
I know ES has changed a lot of their APIs from 2.0 but curious to know if someone has tried this path.
The Java client must be from the same major version of Elasticsearch
as the nodes; otherwise, they may not be able to understand each
other. https://www.elastic.co/guide/en/elasticsearch/guide/current/_talking_to_elasticsearch.html