elasticsearch-jdbc | JDBC importer for Elasticsearch | DB Client library

by jprante Java Version: 2.0.0.0 License: Non-SPDX

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

kandi X-RAY | elasticsearch-jdbc Summary

elasticsearch-jdbc is a Java library typically used in Utilities, DB Client applications. elasticsearch-jdbc has no bugs, it has no vulnerabilities, it has build file available and it has medium support. However elasticsearch-jdbc has a Non-SPDX License. You can download it from GitHub.

The Java Database Connection (JDBC) importer allows to fetch data from JDBC sources for indexing into Elasticsearch. The JDBC importer was designed for tabular data. If you have tables with many joins, the JDBC importer is limited in the way to reconstruct deeply nested objects to JSON and process object semantics like object identity. Though it would be possible to extend the JDBC importer with a mapping feature where all the object properties could be specified, the current solution is focused on rather simple tabular data streams. Assuming you have a table of name orders with a primary key in column id, you can issue this from the command line. And that's it. Now you can check your Elasticsearch cluster for the index jdbc or your Elasticsearch logs about what happened.

Support

Quality

Security

License

Reuse

Support

elasticsearch-jdbc has a medium active ecosystem.

It has 2834 star(s) with 719 fork(s). There are 233 watchers for this library.

It had no major release in the last 12 months.

There are 401 open issues and 478 have been closed. On average issues are closed in 284 days. There are 18 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of elasticsearch-jdbc is 2.0.0.0

Quality

elasticsearch-jdbc has 0 bugs and 0 code smells.

Security

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

elasticsearch-jdbc code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

elasticsearch-jdbc has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

elasticsearch-jdbc releases are available to install and integrate.

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

Installation instructions, examples and code snippets are available.

elasticsearch-jdbc saves you 6189 person hours of effort in developing the same functionality from scratch.

It has 12895 lines of code, 953 functions and 117 files.

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

Top functions reviewed by kandi - BETA

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

Receive a list of values
Merge control keys with values
Serialize the given shape into a GeoJSON format
Maps a control key to an indexable object
Fetch SQL commands
Prepares database
Parses the value of the JDBC type
Returns a summary of the expression summary
Generate the expression set summary
Ends an indexable object
Returns true if the given date satisfies the cron expression
Overrides the settings to set the values in this context
Performs the actual fetch
Appends a value to the list
Returns a string representation of the options
Main entry point
Parses an expression
Shuts down resources
Initializes the index
Index an indexable object
Updates an indexable object
Gets the next valid date after the given date
Flush index
Deletes an indexable object
Sets the rounding to use
Invoked by the pipeline

Get all kandi verified functions for this library.

elasticsearch-jdbc Key Features

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

elasticsearch-jdbc Examples and Code Snippets

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

Community Discussions

Trending Discussions on elasticsearch-jdbc

load dynamic data from MySQL table in ElasticSearch using JDBC driver

Elasticsearch query with NEST don't work

Elastic Search 5 and SQL Server synchronisation

QUESTION

load dynamic data from MySQL table in ElasticSearch using JDBC driver

Asked 2018-May-24 at 07:16

I have get dyanamically data from MySQL tables in my elasticSearch index. For that i have used following link for but not get propper result:

I have used following code:

...

ANSWER

Answered 2018-May-24 at 07:16

I have got a answer for that question: make one file in root directory called event.sh and following code in that file

event.sh

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

QUESTION

Elasticsearch query with NEST don't work

Asked 2017-Mar-02 at 23:39

I'm using Microsoft SQL Server Management Studio and ElasticSearch 2.3.4 with ElasticSearch-jdbc-2.3.4.1, and i linked ES with my mssql server. Everything works fine, but when i make a query using NEST on my MVC program the result is empty. When i put an empty string inside my search attribute i get the elements, but when i try to fill it with some filter i get an empty result. Can someone help me out please? Thanks in advance.

C#:

...

ANSWER

Answered 2017-Mar-02 at 23:39

There's a couple of things that I can see that may help here:

By default, NEST camel cases POCO property names when serializing them as part of the query JSON in the request, so x => x.Question will serialize to "question". Looking at your mapping however, field names in Elasticsearch are Pascal cased, so what the client is doing will not match what's in Elasticsearch.

You can change how NEST serializes POCO property names by using .DefaultFieldNameInferrer(Func) on ConnectionSettings

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

QUESTION

Elastic Search 5 and SQL Server synchronisation

Asked 2017-Jan-03 at 13:07

I am starting a Elastic search 5 project from data that are actually in a SQL Server, so I am starting from the start:

I am thinking about how import data from my SQL Server, and especially how to synchronise my data when data are updated or added.

I saw here it is adviced to make no too frequent batch.

But how make synchronisation batchs, may I have to write it myself or is there very used tools and practices ? River and JDBC plugin feeder appears to have been really used but don't work with Elastic Search 5.*

Any help would be very welcomed.

...

ANSWER

Answered 2017-Jan-03 at 13:07

I'd recommend using Logstash:

It's easy to use and setup
You can do your own ETL in logstash configuration files
You can have multiple JDBC sources in one file
You'll have figure out how to make incremental (batched) updates to sync your data. It really depends on your data model.

This is a nice blog piece to begin with:

https://www.elastic.co/blog/logstash-jdbc-input-plugin

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

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

Vulnerabilities

No vulnerabilities reported

Install elasticsearch-jdbc

in the following steps replace <version> by one of the versions above, e.g. 1.7.0.0. download the JDBC importer distribution. go to the unpacked directory (we call it $JDBC_IMPORTER_HOME) cd elasticsearch-jdbc-<version>. if you do not find the JDBC driver jar in the lib directory, download it from your vendor's site and put the driver jar into the lib folder. modify script in the bin directory to your needs (Elasticsearch cluster address). run script with a command that starts org.xbib.tools.JDBCImporter with the lib directory on the classpath.
in the following steps replace <version> by one of the versions above, e.g. 1.7.0.0
download the JDBC importer distribution wget http://xbib.org/repository/org/xbib/elasticsearch/importer/elasticsearch-jdbc/<version>/elasticsearch-jdbc-<version>-dist.zip
unpack unzip elasticsearch-jdbc-<version>-dist.zip
go to the unpacked directory (we call it $JDBC_IMPORTER_HOME) cd elasticsearch-jdbc-<version>
if you do not find the JDBC driver jar in the lib directory, download it from your vendor's site and put the driver jar into the lib folder
modify script in the bin directory to your needs (Elasticsearch cluster address)
run script with a command that starts org.xbib.tools.JDBCImporter with the lib directory on the classpath

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: