elasticsearch-client | Simple Elasticsearch client | Search Engine library

by Top-Q Java Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(9)Vulnerabilities Install Support

kandi X-RAY | elasticsearch-client Summary

elasticsearch-client is a Java library typically used in Database, Search Engine, Docker applications. elasticsearch-client has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

A simple Elasticseach client based on the 5.x HTTP API. This is by no means a full blown client and it support only a small sub set of the Elasticseach operations. Furethemore, when the Elasticteam will release a full Java client, this client will probably become redundent. Nevertheless, the client is very simple for use, supports the basic operations and is designed to easily be extended.

Support

Quality

Security

License

Reuse

Support

elasticsearch-client has a low active ecosystem.

It has 4 star(s) with 7 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

There are 2 open issues and 0 have been closed. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of elasticsearch-client is current.

Quality

elasticsearch-client has 0 bugs and 0 code smells.

Security

elasticsearch-client has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

elasticsearch-client code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

elasticsearch-client is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

elasticsearch-client releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

It has 1578 lines of code, 179 functions and 29 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed elasticsearch-client and discovered the below as its top functions. This is intended to give you an instant insight into elasticsearch-client implemented functionality, and help decide if they suit your requirements.

Get the cardinality of a field
Get average value for a field
Return the cardinality of a field
Get the maximum value for a field
Get the max value
Get the minimum value for a field
Get the minimum value
Query for average results
Search by query
Performs a HTTP request
Bulk request
Bulk insert operations
Check if index exists
Deletes a single document
Updates a single object
Bulk update list of objects
Close resources
Delete this index
Returns statistics for the index
Search by term
Main entry point
Search by wildcard
Search by term
Creates a new index
Gets the stats
Returns all nodes

Get all kandi verified functions for this library.

elasticsearch-client Key Features

No Key Features are available at this moment for elasticsearch-client.

elasticsearch-client Examples and Code Snippets

No Code Snippets are available at this moment for elasticsearch-client.

Community Discussions

Trending Discussions on elasticsearch-client

can I use old spring-data-elasticsearch to connect to new elasticsearch?

Elasticsearch exception [type=parsing_exception, reason=[wildcard] query does not support [case_insensitive]]

springboot elasticsearch date convert ConversionException

Set Kubernetes Readiness for elasticsearch client

Automate calling bash commands on a Kubernetes container

deploy elk stack in kubernetes with helm VolumeBinding error

Unresolved reference: grgit in build.gradle.kts

Angular Universal SSR + Serverless Framework ReferenceError: Event is not defined when Trigger the URL

Helm Chart - Can't evaluate .Release.Name in a field

QUESTION

can I use old spring-data-elasticsearch to connect to new elasticsearch?

Asked 2022-Mar-28 at 17:51

Currently we are on spring-data-elasticsearch 3.2.6 + elasticsearch 6.8. We are moving to new elasticsearch 7.x. Do I have to update spring-data-elasticsearch to 4.x? We only use ElasticsearchRepository in spring-data-elasticsearch. And we don't need to use any new feature in elasticsearch 7.x.

If we are moving to elasticsearch 8.x in the future, do I need update spring-data-elasticsearch ?

Update:

What Elasticsearch client does Spring-Data-Elasticsearch use under the hood?

All methods in the `ElasticsearchRepository` are deprecated. What should do I use?

I found some discussions in above threads. Here is my summary.

Operations with Templates:

ElasticsearchTemplate implements ElasticSearchOperation. It uses TransportClient(which is deprecated in ES 7 and has been removed in ES8)

ElasticsearchRestTemplate implements ElasticSearchOperation. It uses high level client(which is deprecated in ES 7.16.0. It will be removed in future. @Deprecated(since = "7.16.0", forRemoval = true) )

ReactiveElasticsearchTemplate implements ReactiveElasticsearchOperations. It uses Reactive Client.

Repository

ElasticsearchRepository uses TransportClient as default. All methods in the ElasticsearchRepository are deprecated now.

Reactive Elasticsearch repository builds on ReactiveElasticsearchOperations.

Due to underlying TransportClient or HigLevelRestClient has been deprecated, can I conclude that the correct way is to use Reactive Client(ReactiveElasticsearchTemplate or Reactive Elasticsearch repository) ?

...

ANSWER

Answered 2022-Mar-24 at 16:54

The new Elasticsearch would be 8.

Val already put the link to the compatibility matrix in his comment.

Version 3.2.6 is pretty outdated (March 25 2020) and out of support since October 2020.

The first thing you can try is to see if your application works with a 7 cluster - although I doubt that, I can't tell you exactly what had changed in the API, but there was quite some stuff.

What you should not do is putting newer Elasticsearch libraries on the classpath than the ones that Spring Data Elasticsearch was built with, this will in most cases make problems.

But I'd recommend to upgrade your application anyway and keep it regularly up to date.

As for future upgrade to version 8: It is possible to send a compatibility header in your requests (this can be done in Spring Data Elasticsearch 4) and the Elasticsearch cluster should respond in a format that is compatible with a client expecting version 7. I wrote should, because it does not conform to this in every case - I reported one case that is fixed now. But I wouldn't rely on that.

Again, please update your application and keep it up to date, not only because of Spring Data Elasticsearch, but also because these updates always include bug and/or security fixes.

Source https://stackoverflow.com/questions/71605823

QUESTION

Elasticsearch exception [type=parsing_exception, reason=[wildcard] query does not support [case_insensitive]]

Asked 2022-Jan-08 at 18:53

I'm using 7.10.2 version of Maven-org-elasticsearch-client_elasticsearch-rest-high-level-client version and WildcardQueryBuilder should work with caseInsensitive property. Following is my code snippet and I'm getting "Elasticsearch exception [type=parsing_exception, reason=[wildcard] query does not support [case_insensitive]]" on executing my ES search request

...

ANSWER

Answered 2022-Jan-08 at 18:53

I strongly believe that the Java client version and your Cluster's version differ. The caseInsensitive query parameter was first introduced with Elasticsearch version 7.10.

So I guess you're running an Elasticsearch cluster with a version below 7.10. The cluster does not know about this parameter "yet".

I hope I could help you.

Source https://stackoverflow.com/questions/70628749

QUESTION

springboot elasticsearch date convert ConversionException

Asked 2021-Jul-05 at 05:49

springboot version:2.5.2
elasticsearch version:7.3.0
elasticsearch-client: rest-hight-level
the entity

...

ANSWER

Answered 2021-Jul-05 at 05:49

The date time string you have represent with offset you can use OffsetDateTime to parse the string with custom pattern

Source https://stackoverflow.com/questions/68251141

QUESTION

Set Kubernetes Readiness for elasticsearch client

Asked 2021-Jan-27 at 10:04

I upgraded the elasticsearch chart in kubernetes from 6.6 to 7.10.2 version. Data and master pods are running and ready but, the clients aren't ready (2 clients, 2 data , 3 master).

This is their status:

...

ANSWER

Answered 2021-Jan-24 at 14:30

You must have odd number of master nodes, e.g. 1, 3, 5 and so on, usually 3 masters is optimal. Otherwise your cluster won't work due to lack of quorum.

Source https://stackoverflow.com/questions/65871294

QUESTION

Automate calling bash commands on a Kubernetes container

Asked 2020-Dec-01 at 09:23

I am running an Elasticsearch stack with Kibana and Fluent Bit on Kubernetes. To set up security I set a passwords using this command:

...

ANSWER

Answered 2020-Dec-01 at 09:23

As @David Maze pointed out I should put the (bootstrap) password into a secret.

My initial problem was that I thought that the elasticsearch-setup-passwords tool was the only way to set up the (user) password.

In other words, I did not know the password before the program was started. But I just found a way to change the bootstrap password beforehand here, so the problem is solved.

Source https://stackoverflow.com/questions/65075374

QUESTION

deploy elk stack in kubernetes with helm VolumeBinding error

Asked 2020-Aug-24 at 16:55

I'm trying to deploy elk stack in kubernetes cluster with helm, using this chart. When I launch

helm install elk-stack stable/elastic-stack

I receive the following message:

...

ANSWER

Answered 2020-Aug-24 at 16:55

The reason why pod is pending is below PVCs are pending because corresponding PVs are not created.

Source https://stackoverflow.com/questions/63556649

QUESTION

Unresolved reference: grgit in build.gradle.kts

Asked 2020-Aug-06 at 13:04

Getting error like below, When I am compiling the code using using this command "bash ./gradlew build"

Unresolved reference: grgit

build.gradle.kts :

...

ANSWER

Answered 2020-Aug-06 at 13:04

You have not declared your grgit variable.

You can get a Grgit instance by:

Source https://stackoverflow.com/questions/63281263

QUESTION

Angular Universal SSR + Serverless Framework ReferenceError: Event is not defined when Trigger the URL

Asked 2020-May-22 at 06:00

I'm Trying to add SSR for my angular application and after days i was able to finally Build it right.

Build Command : npm run build:ssr

Out Put :

...

ANSWER

Answered 2020-May-22 at 06:00

This is because one of your dependencies is trying to access the Event object, which is not available by default server side.

Since you are already using domino, you can try adding these lines to your server.ts to make Event object available

Source https://stackoverflow.com/questions/61624741

QUESTION

Helm Chart - Can't evaluate .Release.Name in a field

Asked 2020-Apr-29 at 10:39

I am new to Helm and I can not understand why this is happening. I am using the official EFK chart and I am trying to add release name to fluentd-elasticsearch's host fields but it does not get evaluated. It is passed just as a string. The release name in ELASTICSEARCH_HOSTS is evaluated properly but the same in host field is not evaluated at all. Can anyone tell why is this happening and how to fix it?

...

ANSWER

Answered 2020-Apr-29 at 10:39

The values.yaml file is not evaluated. So you cannot use {{ .Release.Name }} inside values.yaml.

The reason why it works for ELASTICSEARCH_HOSTS is that inside Kibana Helm Chart, the values are first kind-of copied and later evaluated.

Source https://stackoverflow.com/questions/61485221

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install elasticsearch-client

Java 8

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: