# JDBC importer 2.1.1.0 for Elasticsearch 2.1.1

**URL:** https://discuss.elastic.co/t/jdbc-importer-2-1-1-0-for-elasticsearch-2-1-1/37802
**Category:** Community Ecosystem
**Created:** [December 22, 2015, 10:40pm UTC](https://discuss.elastic.co/t/jdbc-importer-2-1-1-0-for-elasticsearch-2-1-1/37802 "2015-12-22T22:40:15Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)
#### Post date: [December 22, 2015, 10:40pm UTC](https://discuss.elastic.co/t/jdbc-importer-2-1-1-0-for-elasticsearch-2-1-1/37802/1 "2015-12-22T22:40:15Z")

</div>

Hi,

I have released JDBC importer 2.1.1.0 which is compatible to Elasticsearch 2.1.1

> **[jprante/elasticsearch-jdbc](https://github.com/jprante/elasticsearch-jdbc)**
>
> elasticsearch-jdbc - JDBC importer for Elasticsearch

There is not much functionality that has changed or added. Detected JSON can now be parsed as lists/maps, thanks to a contribution by Simon J Hewitt.

Please try this new release, all feedback and contributions are welcome. The Elasticsearch community is really great. I will still continue to work on JDBC importer in 2016 on a voluntary basis and I have many plans for improvements.

I wish you a merry christmas and a happy new year 2016!

Best,

Jörg

P.S. if you want to honor me for my work, you can now send me a donation. See the button at [https://github.com/jprante/elasticsearch-jdbc](https://github.com/jprante/elasticsearch-jdbc) Thanks for your support!

---

<div class="post-metadata">

### Author: ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)
#### Post date: [December 23, 2015, 9:33am UTC](https://discuss.elastic.co/t/jdbc-importer-2-1-1-0-for-elasticsearch-2-1-1/37802/2 "2015-12-23T09:33:20Z")

</div>

I released JDBC importer 2.1.1.1 with a fix for the cluster name parameter.

If you have trouble connecting to the cluster, you can try

```auto
 "elasticsearch": {
  "cluster": {
    "name": {
      "my-cluster-name"
   },
   ...
  }
}

```

in the JDBC importer specification.

---

<div class="post-metadata">

### Author: ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)
#### Post date: [December 23, 2015, 9:57pm UTC](https://discuss.elastic.co/t/jdbc-importer-2-1-1-0-for-elasticsearch-2-1-1/37802/3 "2015-12-23T21:57:11Z")

</div>

Next try, JDBC importer 2.1.1.2 contains a fix and is actually connecting to a cluster (again). Wow. Now merry christmas everybody and sorry for the noise.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 9:47pm UTC](https://discuss.elastic.co/t/jdbc-importer-2-1-1-0-for-elasticsearch-2-1-1/37802/4 "2017-07-05T21:47:53Z")

</div>


