# Elasticsearch 0.20.2 / jdbc river / Gram

**URL:** <https://discuss.elastic.co/t/elasticsearch-0-20-2-jdbc-river-gram/10392>\
**Category:** Elasticsearch\
**Created:** [January 17, 2013, 3:30pm UTC](https://discuss.elastic.co/t/elasticsearch-0-20-2-jdbc-river-gram/10392 "2013-01-17T15:30:07Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul\_Bertonio](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Paul\_Bertonio](https://discuss.elastic.co/u/Paul_Bertonio)\
**Post date:** [January 17, 2013, 3:30pm UTC](https://discuss.elastic.co/t/elasticsearch-0-20-2-jdbc-river-gram/10392/1 "2013-01-17T15:30:07Z")

</div>

Hello,

I have some problem to create an index with gram parameters by using  
elastic's search jdbc river (  
[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)).

I'm using the following request :

curl -XPUT 'localhost:9200/\_river/my\_jdbc\_test/\_meta' -d '{  
"type":"jdbc",  
"jdbc": {  
XXXX  
},  
"index": {  
"index":"jdbc",  
"type":"jdbc",  
"analysis" : {  
"analyzer" : {  
"my\_analyzer" : {  
"type" : "custom",  
"tokenizer" :  
"my\_ngram\_tokenizer",  
"filter" :  
["my\_ngram\_filter"]  
}  
},  
"filter" : {  
"my\_ngram\_filter" : {  
"type" : "nGram",  
"min\_gram" : 3,  
"max\_gram" : 10  
}  
},  
"tokenizer" : {  
"my\_ngram\_tokenizer" : {  
"type" : "nGram",  
"min\_gram" : 3,  
"max\_gram" : 10  
}  
}  
}  
},  
"mappings": {  
"jdbc": {  
"properties": {  
"field1": {  
"type": "string",  
"analyzer": "my\_analyzer"  
}  
}  
}  
}  
}'

But with these settings, index jdbc is able to grab database field1 but my  
Gram doesn't work..

Maybe someone already got this problem and could give some help ?

Thanks for your help,

Regards,

--

---

<div class="post-metadata">

**Author:** ![Justin\_Treher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/justin_treher/32/45243_2.png) [@Justin\_Treher](https://discuss.elastic.co/u/Justin_Treher)\
**Post date:** [January 17, 2013, 3:34pm UTC](https://discuss.elastic.co/t/elasticsearch-0-20-2-jdbc-river-gram/10392/2 "2013-01-17T15:34:21Z")

</div>

I will just latch onto this question. I've been setting up my index first  
and then running the jdbc river. It doesn't always seem to populate. I've  
found that if I delete everything, setup the index and then setup the  
river, population is immediate and it works.

So, it's possible to setup the river and the index at the same time, cool?  
Is this is a best practice?

On Thursday, January 17, 2013 10:30:07 AM UTC-5, Paul Bertonio wrote:

> Hello,
> 
> I have some problem to create an index with gram parameters by using  
> elastic's search jdbc river (  
> [GitHub - jprante/elasticsearch-jdbc: JDBC importer for Elasticsearch](https://github.com/jprante/elasticsearch-river-jdbc)).
> 
> I'm using the following request :
> 
> curl -XPUT 'localhost:9200/\_river/my\_jdbc\_test/\_meta' -d '{  
> "type":"jdbc",  
> "jdbc": {  
> XXXX  
> },  
> "index": {  
> "index":"jdbc",  
> "type":"jdbc",  
> "analysis" : {  
> "analyzer" : {  
> "my\_analyzer" : {  
> "type" : "custom",  
> "tokenizer" :  
> "my\_ngram\_tokenizer",  
> "filter" :  
> ["my\_ngram\_filter"]  
> }  
> },  
> "filter" : {  
> "my\_ngram\_filter" : {  
> "type" : "nGram",  
> "min\_gram" : 3,  
> "max\_gram" : 10  
> }  
> },  
> "tokenizer" : {  
> "my\_ngram\_tokenizer" : {  
> "type" : "nGram",  
> "min\_gram" : 3,  
> "max\_gram" : 10  
> }  
> }  
> }  
> },  
> "mappings": {  
> "jdbc": {  
> "properties": {  
> "field1": {  
> "type": "string",  
> "analyzer": "my\_analyzer"  
> }  
> }  
> }  
> }  
> }'
> 
> But with these settings, index jdbc is able to grab database field1 but my  
> Gram doesn't work..
> 
> Maybe someone already got this problem and could give some help ?
> 
> Thanks for your help,
> 
> Regards,

--

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 17, 2013, 3:44pm UTC](https://discuss.elastic.co/t/elasticsearch-0-20-2-jdbc-river-gram/10392/3 "2013-01-17T15:44:08Z")

</div>

IMHO, from a maintainability point of view, I will spilt the two operations:

1. create the index, mappings, aliases,...
2. when everything is ready start the river (aka create the river)

My 2 cents

Le 17 janvier 2013 à 16:34, [jtreher@gmail.com](mailto:jtreher@gmail.com) a écrit :

> I will just latch onto this question. I've been setting up my index first and  
> then running the jdbc river. It doesn't always seem to populate. I've found  
> that if I delete everything, setup the index and then setup the river,  
> population is immediate and it works.
> 
> So, it's possible to setup the river and the index at the same time, cool? Is  
> this is a best practice?
> 
> On Thursday, January 17, 2013 10:30:07 AM UTC-5, Paul Bertonio wrote:
> 
> > > Hello,
> > 
> > I have some problem to create an index with gram parameters by using  
> > elastic's search jdbc river (  
> > [GitHub - jprante/elasticsearch-jdbc: JDBC importer for Elasticsearch](https://github.com/jprante/elasticsearch-river-jdbc)).  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > I'm using the following request :  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > curl -XPUT 'localhost:9200/\_river/my\_jdbc\_test/\_meta' -d '{  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > "type":"jdbc",  
> > "jdbc": {  
> > XXXX  
> > },  
> > "index": {  
> > "index":"jdbc",  
> > "type":"jdbc",  
> > "analysis" : {  
> > "analyzer" : {  
> > "my\_analyzer" : {  
> > "type" : "custom",  
> > "tokenizer" :  
> > "my\_ngram\_tokenizer",  
> > "filter" :  
> > ["my\_ngram\_filter"]  
> > }  
> > },  
> > "filter" : {  
> > "my\_ngram\_filter" : {  
> > "type" : "nGram",  
> > "min\_gram" : 3,  
> > "max\_gram" : 10  
> > }  
> > },  
> > "tokenizer" : {  
> > "my\_ngram\_tokenizer" : {  
> > "type" : "nGram",  
> > "min\_gram" : 3,  
> > "max\_gram" : 10  
> > }  
> > }  
> > }  
> > },  
> > "mappings": {  
> > "jdbc": {  
> > "properties": {  
> > "field1": {  
> > "type": "string",  
> > "analyzer": "my\_analyzer"  
> > }  
> > }  
> > }  
> > }  
> > }'  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > But with these settings, index jdbc is able to grab database field1 but  
> > my Gram doesn't work.. [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > Maybe someone already got this problem and could give some help ?  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > Thanks for your help,  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > Regards, [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)
> > 
> > >
> 
> --
> 
> [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)

[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)

--  
David Pilato  
[http://www.scrutmydocs.org/](http://www.scrutmydocs.org/)  
[http://dev.david.pilato.fr/](http://dev.david.pilato.fr/)  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

--

---

<div class="post-metadata">

**Author:** ![Paul\_Bertonio](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Paul\_Bertonio](https://discuss.elastic.co/u/Paul_Bertonio)\
**Post date:** [January 17, 2013, 4:27pm UTC](https://discuss.elastic.co/t/elasticsearch-0-20-2-jdbc-river-gram/10392/4 "2013-01-17T16:27:27Z")

</div>

Hello,

I have split both part, thanks for your advice.

But i don't understand why analyzer still doesn't work 😕

On Thursday, January 17, 2013 4:44:08 PM UTC+1, David Pilato wrote:

> IMHO, from a maintainability point of view, I will spilt the two  
> operations:
> 
> 1. create the index, mappings, aliases,...
> 2. when everything is ready start the river (aka create the river)
> 
> My 2 cents
> 
> Le 17 janvier 2013 à 16:34, [jtr...@gmail.com](mailto:jtr...@gmail.com) \<javascript:\> a écrit :
> 
> I will just latch onto this question. I've been setting up my index first  
> and then running the jdbc river. It doesn't always seem to populate. I've  
> found that if I delete everything, setup the index and then setup the  
> river, population is immediate and it works.
> 
> So, it's possible to setup the river and the index at the same time, cool?  
> Is this is a best practice?
> 
> On Thursday, January 17, 2013 10:30:07 AM UTC-5, Paul Bertonio wrote:
> 
> Hello,
> 
> I have some problem to create an index with gram parameters by using  
> elastic's search jdbc river (  
> [GitHub - jprante/elasticsearch-jdbc: JDBC importer for Elasticsearch](https://github.com/jprante/elasticsearch-river-jdbc)).[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> I'm using the following request :[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> curl -XPUT 'localhost:9200/\_river/my\_jdbc\_test/\_meta' -d '{[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> "type":"jdbc",  
> "jdbc": {  
> XXXX  
> },  
> "index": {  
> "index":"jdbc",  
> "type":"jdbc",  
> "analysis" : {  
> "analyzer" : {  
> "my\_analyzer" : {  
> "type" : "custom",  
> "tokenizer" :  
> "my\_ngram\_tokenizer",  
> "filter" :  
> ["my\_ngram\_filter"]  
> }  
> },  
> "filter" : {  
> "my\_ngram\_filter" : {  
> "type" : "nGram",  
> "min\_gram" : 3,  
> "max\_gram" : 10  
> }  
> },  
> "tokenizer" : {  
> "my\_ngram\_tokenizer" : {  
> "type" : "nGram",  
> "min\_gram" : 3,  
> "max\_gram" : 10  
> }  
> }  
> }  
> },  
> "mappings": {  
> "jdbc": {  
> "properties": {  
> "field1": {  
> "type": "string",  
> "analyzer": "my\_analyzer"  
> }  
> }  
> }  
> }  
> }'  
> [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> But with these settings, index jdbc is able to grab database field1 but  
> my Gram doesn't work..[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> Maybe someone already got this problem and could give some help ?[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> Thanks for your help,[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> Regards, [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)
> 
> --
> 
> [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)
> 
> [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)
> 
> --  
> David Pilato  
> [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/)  
> [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/)  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

--

---

<div class="post-metadata">

**Author:** ![Paul\_Bertonio](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Paul\_Bertonio](https://discuss.elastic.co/u/Paul_Bertonio)\
**Post date:** [January 17, 2013, 4:52pm UTC](https://discuss.elastic.co/t/elasticsearch-0-20-2-jdbc-river-gram/10392/5 "2013-01-17T16:52:23Z")

</div>

I also tried to create index and mapping first and then create the river  
but i have still the same situation

On Thursday, January 17, 2013 5:27:27 PM UTC+1, Paul Bertonio wrote:

> Hello,
> 
> I have split both part, thanks for your advice.
> 
> But i don't understand why analyzer still doesn't work 😕
> 
> On Thursday, January 17, 2013 4:44:08 PM UTC+1, David Pilato wrote:
> 
> > IMHO, from a maintainability point of view, I will spilt the two  
> > operations:
> > 
> > 1. create the index, mappings, aliases,...
> > 2. when everything is ready start the river (aka create the river)
> > 
> > My 2 cents
> > 
> > Le 17 janvier 2013 à 16:34, [jtr...@gmail.com](mailto:jtr...@gmail.com) a écrit :
> > 
> > I will just latch onto this question. I've been setting up my index first  
> > and then running the jdbc river. It doesn't always seem to populate. I've  
> > found that if I delete everything, setup the index and then setup the  
> > river, population is immediate and it works.
> > 
> > So, it's possible to setup the river and the index at the same time,  
> > cool? Is this is a best practice?
> > 
> > On Thursday, January 17, 2013 10:30:07 AM UTC-5, Paul Bertonio wrote:
> > 
> > Hello,
> > 
> > I have some problem to create an index with gram parameters by using  
> > elastic's search jdbc river (  
> > [GitHub - jprante/elasticsearch-jdbc: JDBC importer for Elasticsearch](https://github.com/jprante/elasticsearch-river-jdbc)).[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > I'm using the following request :[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > curl -XPUT 'localhost:9200/\_river/my\_jdbc\_test/\_meta' -d '{[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > "type":"jdbc",  
> > "jdbc": {  
> > XXXX  
> > },  
> > "index": {  
> > "index":"jdbc",  
> > "type":"jdbc",  
> > "analysis" : {  
> > "analyzer" : {  
> > "my\_analyzer" : {  
> > "type" : "custom",  
> > "tokenizer" :  
> > "my\_ngram\_tokenizer",  
> > "filter" :  
> > ["my\_ngram\_filter"]  
> > }  
> > },  
> > "filter" : {  
> > "my\_ngram\_filter" : {  
> > "type" : "nGram",  
> > "min\_gram" : 3,  
> > "max\_gram" : 10  
> > }  
> > },  
> > "tokenizer" : {  
> > "my\_ngram\_tokenizer" : {  
> > "type" : "nGram",  
> > "min\_gram" : 3,  
> > "max\_gram" : 10  
> > }  
> > }  
> > }  
> > },  
> > "mappings": {  
> > "jdbc": {  
> > "properties": {  
> > "field1": {  
> > "type": "string",  
> > "analyzer": "my\_analyzer"  
> > }  
> > }  
> > }  
> > }  
> > }'  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > But with these settings, index jdbc is able to grab database field1 but  
> > my Gram doesn't work..[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > Maybe someone already got this problem and could give some help ?[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > Thanks for your help,[https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
> > Regards, [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)
> > 
> > --
> > 
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)
> > 
> > [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)
> > 
> > --  
> > David Pilato  
> > [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/)  
> > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/)  
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

--

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 17, 2013, 8:45pm UTC](https://discuss.elastic.co/t/elasticsearch-0-20-2-jdbc-river-gram/10392/6 "2013-01-17T20:45:17Z")

</div>

Could you gist a full curl recreation as we can see what's going on here?

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 17 janv. 2013 à 17:52, Paul Bertonio [pbertonio@gmail.com](mailto:pbertonio@gmail.com) a écrit :

I also tried to create index and mapping first and then create the river but i have still the same situation

On Thursday, January 17, 2013 5:27:27 PM UTC+1, Paul Bertonio wrote:

> Hello,
> 
> I have split both part, thanks for your advice.
> 
> But i don't understand why analyzer still doesn't work 😕
> 
> On Thursday, January 17, 2013 4:44:08 PM UTC+1, David Pilato wrote:
> 
> > IMHO, from a maintainability point of view, I will spilt the two operations:
> > 
> > 1. create the index, mappings, aliases,...
> > 2. when everything is ready start the river (aka create the river)
> > 
> > My 2 cents
> > 
> > Le 17 janvier 2013 à 16:34, [jtr...@gmail.com](mailto:jtr...@gmail.com) a écrit :
> > 
> > > I will just latch onto this question. I've been setting up my index first and then running the jdbc river. It doesn't always seem to populate. I've found that if I delete everything, setup the index and then setup the river, population is immediate and it works.
> > > 
> > > So, it's possible to setup the river and the index at the same time, cool? Is this is a best practice?
> > > 
> > > On Thursday, January 17, 2013 10:30:07 AM UTC-5, Paul Bertonio wrote:  
> > > Hello,
> > > 
> > > I have some problem to create an index with gram parameters by using elastic's search jdbc river ( [GitHub - jprante/elasticsearch-jdbc: JDBC importer for Elasticsearch](https://github.com/jprante/elasticsearch-river-jdbc)).
> > > 
> > > I'm using the following request :
> > > 
> > > curl -XPUT 'localhost:9200/\_river/my\_jdbc\_test/\_meta' -d '{  
> > > "type":"jdbc",  
> > > "jdbc": {  
> > > XXXX  
> > > },  
> > > "index": {  
> > > "index":"jdbc",  
> > > "type":"jdbc",  
> > > "analysis" : {  
> > > "analyzer" : {  
> > > "my\_analyzer" : {  
> > > "type" : "custom",  
> > > "tokenizer" : "my\_ngram\_tokenizer",  
> > > "filter" : ["my\_ngram\_filter"]  
> > > }  
> > > },  
> > > "filter" : {  
> > > "my\_ngram\_filter" : {  
> > > "type" : "nGram",  
> > > "min\_gram" : 3,  
> > > "max\_gram" : 10  
> > > }  
> > > },  
> > > "tokenizer" : {  
> > > "my\_ngram\_tokenizer" : {  
> > > "type" : "nGram",  
> > > "min\_gram" : 3,  
> > > "max\_gram" : 10  
> > > }  
> > > }  
> > > }  
> > > },  
> > > "mappings": {  
> > > "jdbc": {  
> > > "properties": {  
> > > "field1": {  
> > > "type": "string",  
> > > "analyzer": "my\_analyzer"  
> > > }  
> > > }  
> > > }  
> > > }  
> > > }'
> > > 
> > > But with these settings, index jdbc is able to grab database field1 but my Gram doesn't work..
> > > 
> > > Maybe someone already got this problem and could give some help ?
> > > 
> > > Thanks for your help,
> > > 
> > > Regards,
> > > 
> > > --
> > 
> > --  
> > David Pilato  
> > [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/)  
> > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/)  
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs  
> > --

--

---

<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 6, 2017, 2:55am UTC](https://discuss.elastic.co/t/elasticsearch-0-20-2-jdbc-river-gram/10392/7 "2017-07-06T02:55:50Z")

</div>