elasticsearch-js | Official Elasticsearch client library for Node.js | Runtime Evironment library

by elastic TypeScript Version: v8.8.1 License: Apache-2.0

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

kandi X-RAY | elasticsearch-js Summary

elasticsearch-js is a TypeScript library typically used in Server, Runtime Evironment, Nodejs, Docker applications. elasticsearch-js has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

The official Node.js client for Elasticsearch.

Support

Quality

Security

License

Reuse

Support

elasticsearch-js has a medium active ecosystem.

It has 5140 star(s) with 733 fork(s). There are 409 watchers for this library.

It had no major release in the last 12 months.

There are 48 open issues and 869 have been closed. On average issues are closed in 51 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of elasticsearch-js is v8.8.1

Quality

elasticsearch-js has 0 bugs and 0 code smells.

Security

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

elasticsearch-js code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

elasticsearch-js 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-js releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

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

Pulls an index with the given tag name

Get all kandi verified functions for this library.

elasticsearch-js Key Features

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

elasticsearch-js Examples and Code Snippets

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

Community Discussions

Trending Discussions on elasticsearch-js

Getting error while creating index for elastic search

Why am I getting the error "Cannot read property 'MAX_LENGTH' of undefined" when I try to connect to Elasticsearch using the JavaScript client?

Elastic Search Node.js client - Routing Error

Can't connect Elasticsearch from my Nodejs app: connect ECONNREFUSED 127.0.0.1:9200

ElasticSearch: Insert a new record into an existing index

Not able to connect to Elasticsearch from docker container (node.js client)

QUESTION

Getting error while creating index for elastic search

Asked 2022-Jan-16 at 08:44

I am trying to create an elastic search index if it doesn't exist using OnModuleInit (NestJs). It works fine with my local machine but when I am trying to deploy to AWS ES Cluster, this part is giving such an error.

...

ANSWER

Answered 2022-Jan-16 at 08:44

This looks like your AWS Opensearch (same tech under the hood of Elasticsearch) instance is returning a 403. This might mean you need to set up IAM Roles and the correct access for your instance. Please See the AWS Docs

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

QUESTION

Why am I getting the error "Cannot read property 'MAX_LENGTH' of undefined" when I try to connect to Elasticsearch using the JavaScript client?

Asked 2021-Jun-30 at 09:03

I am trying to connect a React app to an instance of Elasticsearch in AWS using the JavaScript client. I started the React app using "npm start-react-app app" and then I installed the client using "npm install @elastic/elasticsearch". In the official documentation, it says I can initialize the client by using:

...

ANSWER

Answered 2021-Jun-30 at 09:03

This library is intended to be used in a nodejs environment on the server. You can't use it in the browser as is.

From the repo readme:

Browser
WARNING: There is no official support for the browser environment. It exposes your Elasticsearch instance to everyone, which could lead to security issues. We recommend that you write a lightweight proxy that uses this client instead, you can see a proxy example here.

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

QUESTION

Elastic Search Node.js client - Routing Error

Asked 2020-Nov-11 at 14:51

We have elastic hosted on GCP. I'm getting an error when I try to simply post a document. I'm using their node.js package, and I'm stuck with the following error:

...

ANSWER

Answered 2020-Nov-10 at 08:02

I think you have one too many create in the command you return from onDocument. The command you can return is described here:

So, by removing one create layer, it should work:

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

QUESTION

Can't connect Elasticsearch from my Nodejs app: connect ECONNREFUSED 127.0.0.1:9200

Asked 2020-Nov-01 at 09:14

I cannot connect to Elasticsearch docker server from my NodeJS application.

My code

This is my docker-compose file:

...

ANSWER

Answered 2020-Nov-01 at 09:14

when you run the docker-compose file, the elasticsearch service instance will not be available to your backend service at localhost. change http://localhost:9200 to http://elasticsearch:9200 in your node.js code.

docker compose automatically creates dns entries with same name as the service name for each service.

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

QUESTION

ElasticSearch: Insert a new record into an existing index

Asked 2020-Sep-16 at 03:35

I recently inherited the job of maintaining our ElasticSearch indexes. So I'm still pretty new at this. I've got code in Node.js to create an index and I assume it overwrites an existing index with the same name if it already exists.

What I would like to do is insert one new record into the index leaving the existing data untouched. I've been researching how to do this here, but I'm still not clear on how to do it.

Here is code for creating an index that I'm using now, it appears that the original writer of my file got it from here:

...

ANSWER

Answered 2020-Sep-16 at 03:35

That code doesn't create an index, but it "indexes" a document.

If a document with the same id (i.e. group.id) already exists in the index, then it's going to be reindexed (i.e. overridden), otherwise a new document is going to be created.

So I don't think anything wrong can happen here.

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

QUESTION

Not able to connect to Elasticsearch from docker container (node.js client)

Asked 2020-Feb-11 at 00:16

I have set up an elasticsearch/kibana docker configuration and I want to connect to elasticsearch from inside of a docker container using the @elastic/elasticsearch client for node. However, the connection is "timing out".

The project is taken with inspiration from Patrick Triest : https://blog.patricktriest.com/text-search-docker-elasticsearch/

However, I have made some modification in order to connect kibana, use a newer ES image and the new elasticsearch node client.

I am using the following docker-compose file:

...

ANSWER

Answered 2020-Feb-11 at 00:16

In Docker, localhost (or the corresponding IPv4 address 127.0.0.1, or the corresponding IPv6 address ::1) generally means "this container"; you can't use that host name to access services running in another container.

In a Compose-based setup, the names of the services: blocks (api, elasticsearch, kibana) are usable as host names. The caveat is that all of the services have to be on the same Docker-internal network. Compose creates one for you and attaches containers to it by default. (In your example api is on the default network but the other two containers are on a separate elastic network.) Networking in Compose in the Docker documentation has some more details.

So to make this work, you need to tell your client code to honor the environment variable you're setting that points at Elasticsearch

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

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

Vulnerabilities

No vulnerabilities reported

Install elasticsearch-js

If you are using multiple versions of Elasticsearch, you need to use multiple versions of the client. In the past, install multiple versions of the same package was not possible, but with npm v6.9, you can do that via aliasing.

Support

NOTE: The minimum supported version of Node.js is v12. The client versioning follows the Elastic Stack versioning, this means that major, minor, and patch releases are done following a precise schedule that often does not coincide with the Node.js release times. To avoid support insecure and unsupported versions of Node.js, the client will drop the support of EOL versions of Node.js between minor releases. Typically, as soon as a Node.js version goes into EOL, the client will continue to support that version for at least another minor release. If you are using the client with a version of Node.js that will be unsupported soon, you will see a warning in your logs (the client will start logging the warning with two minors in advance). Unless you are always using a supported version of Node.js, we recommend defining the client dependency in your package.json with the ~ instead of ^. In this way, you will lock the dependency on the minor release and not the major. (for example, ~7.10.0 instead of ^7.10.0).

Find more information at: