# JDBC River && \_parent

**URL:** <https://discuss.elastic.co/t/jdbc-river--parent/10783>\
**Category:** Elasticsearch\
**Created:** [February 18, 2013, 5:55pm UTC](https://discuss.elastic.co/t/jdbc-river--parent/10783 "2013-02-18T17:55:18Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yann\_Barraud](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yann_barraud/32/1108_2.png) [@Yann\_Barraud](https://discuss.elastic.co/u/Yann_Barraud)\
**Post date:** [February 18, 2013, 5:55pm UTC](https://discuss.elastic.co/t/jdbc-river--parent/10783/1 "2013-02-18T17:55:18Z")

</div>

Hi,

I'm currently trying to understand how to use JDBC River. I just got some  
good results this afternoon. 🙂

Now I have a few questions regarding the river :

- if I have 2 tables with 1 for parent items & two which are more child  
items, should I have 3 different rivers ?
- how to set the \_parent filed ? Is it the id of the parent object ? In ES  
? And then, how to make this coherent with preceding question ?

Thanks.

Kind regards,  
Yann

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [February 18, 2013, 6:25pm UTC](https://discuss.elastic.co/t/jdbc-river--parent/10783/2 "2013-02-18T18:25:03Z")

</div>

The JDBC river uses a "pseudo column" method fpr prante/child aware  
indexing. Just like you can state a \_parent attribute in the bulk API,  
you can name a column '\_parent' in the JDBC source to use this attribute.

It does not matter in what order you index parent/children docs as long  
the parent exists (I admit I'm not even sure about this), so, you should  
create the parent docs first. You can create a parent run with the  
default "oneshot" river, and then, add another river for the children,  
or even more. It's as simple as that.

Yes, the \_parent is the \_id attribute of the parent document.

Best regards,

Jörg

Am 18.02.13 18:55, schrieb Yann Barraud:

> Hi,
> 
> I'm currently trying to understand how to use JDBC River. I just got  
> some good results this afternoon. 🙂
> 
> Now I have a few questions regarding the river :
> 
> - if I have 2 tables with 1 for parent items & two which are more  
> child items, should I have 3 different rivers ?
> - how to set the \_parent filed ? Is it the id of the parent object ?  
> In ES ? And then, how to make this coherent with preceding question ?
> 
> Thanks.
> 
> Kind regards,  
> Yann

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Yann\_Barraud](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yann_barraud/32/1108_2.png) [@Yann\_Barraud](https://discuss.elastic.co/u/Yann_Barraud)\
**Post date:** [February 19, 2013, 8:11am UTC](https://discuss.elastic.co/t/jdbc-river--parent/10783/3 "2013-02-19T08:11:57Z")

</div>

Hi Jörg,

Thanks for the answer. It seems in fact really simple. Nevertheless, if I  
index a living DB using the "simple" strategy, I might face problems,  
indexing child before parent, no ?

Cordialement,  
Yann Barraud

2013/2/18 Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com)

> The JDBC river uses a "pseudo column" method fpr prante/child aware  
> indexing. Just like you can state a \_parent attribute in the bulk API, you  
> can name a column '\_parent' in the JDBC source to use this attribute.
> 
> It does not matter in what order you index parent/children docs as long  
> the parent exists (I admit I'm not even sure about this), so, you should  
> create the parent docs first. You can create a parent run with the default  
> "oneshot" river, and then, add another river for the children, or even  
> more. It's as simple as that.
> 
> Yes, the \_parent is the \_id attribute of the parent document.
> 
> Best regards,
> 
> Jörg
> 
> Am 18.02.13 18:55, schrieb Yann Barraud:
> 
> Hi,
> 
> > I'm currently trying to understand how to use JDBC River. I just got some  
> > good results this afternoon. 🙂
> > 
> > Now I have a few questions regarding the river :
> > 
> > - if I have 2 tables with 1 for parent items & two which are more child  
> > items, should I have 3 different rivers ?
> > - how to set the \_parent filed ? Is it the id of the parent object ? In  
> > ES ? And then, how to make this coherent with preceding question ?
> > 
> > Thanks.
> > 
> > Kind regards,  
> > Yann
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to elasticsearch+unsubscribe@\*\*[googlegroups.com](http://googlegroups.com)[elasticsearch%2Bunsubscribe@googlegroups.com](mailto:elasticsearch%2Bunsubscribe@googlegroups.com)  
> .  
> For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out)  
> .

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [February 19, 2013, 9:01am UTC](https://discuss.elastic.co/t/jdbc-river--parent/10783/4 "2013-02-19T09:01:01Z")

</div>

You can create children docs before parent docs. It's not the river.  
It's an ES feature.

See [Creating children docs before parent docs · GitHub](https://gist.github.com/jprante/4984178) for a simple demonstration.

Cordialement,

Jörg

Am 19.02.13 09:11, schrieb Yann Barraud:

> Hi Jörg,
> 
> Thanks for the answer. It seems in fact really simple. Nevertheless,  
> if I index a living DB using the "simple" strategy, I might face  
> problems, indexing child before parent, no ?
> 
> Cordialement,  
> Yann Barraud

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Yann\_Barraud](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yann_barraud/32/1108_2.png) [@Yann\_Barraud](https://discuss.elastic.co/u/Yann_Barraud)\
**Post date:** [February 19, 2013, 9:30am UTC](https://discuss.elastic.co/t/jdbc-river--parent/10783/5 "2013-02-19T09:30:56Z")

</div>

Great ! I definitely love ES !!

Le mardi 19 février 2013 10:01:01 UTC+1, Jörg Prante a écrit :

> You can create children docs before parent docs. It's not the river.  
> It's an ES feature.
> 
> See [Creating children docs before parent docs · GitHub](https://gist.github.com/jprante/4984178) for a simple demonstration.
> 
> Cordialement,
> 
> Jörg
> 
> Am 19.02.13 09:11, schrieb Yann Barraud:
> 
> > Hi Jörg,
> > 
> > Thanks for the answer. It seems in fact really simple. Nevertheless,  
> > if I index a living DB using the "simple" strategy, I might face  
> > problems, indexing child before parent, no ?
> > 
> > Cordialement,  
> > Yann Barraud

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![A\_Daniel](https://avatars.discourse-cdn.com/v4/letter/a/fbc32d/32.png) [@A\_Daniel](https://discuss.elastic.co/u/A_Daniel)\
**Post date:** [May 16, 2013, 6:13pm UTC](https://discuss.elastic.co/t/jdbc-river--parent/10783/6 "2013-05-16T18:13:44Z")

</div>

Hi Jörg,

I am having trouble creating a parent-child relation between two tables  
using JDBC river. I have two tables "person" and "work".

Create table person (  
person\_id numeric,  
person\_name varchar2(100)  
)

create table work (  
work\_id numeric,  
person\_id numeric,  
work\_name varchar2(500),  
genre varchar2(100),  
publisher varchar2(500)  
)

I create a person index using this:

curl -XPUT 'localhost:9200/\_river/person/\_meta' -d '{  
"type" : "jdbc",  
"jdbc" : {  
"strategy" : "simple",  
"driver" : "oracle.jdbc.OracleDriver",  
"url" :  
"jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS\_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=myserver)(PORT=10000)))(CONNECT\_DATA=(SERVER=DEDICATED)(SERVICE\_NAME=TPAI.WORLD)))",  
"user" : "myuser",  
"password" : "test123",  
"sql" : "select person\_id as "\_id", person\_name from person",  
"poll" : "100m"  
},  
"index" : {  
"index" : "jdbcriver\_person",  
"type" : "jdbc"  
}  
}'

I specify the mapping using this:

curl -XPOST 'localhost:9200/\_river/work/\_mapping' -d '{  
"work":{  
"\_parent": {"type": "person"}  
}  
}'

But when I run the below command, I get a RoutingMissingException[routing  
is required for [\_river]/[work]/[\_meta].

curl -XPUT 'localhost:9200/\_river/work/\_meta' -d '{  
"type" : "jdbc",  
"jdbc" : {  
"strategy" : "simple",  
"driver" : "oracle.jdbc.OracleDriver",  
"url" :  
"jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS\_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=myserver)(PORT=10000)))(CONNECT\_DATA=(SERVER=DEDICATED)(SERVICE\_NAME=TPAI.WORLD)))",  
"user" : "myuser",  
"password" : "test123",  
"sql" : "select work\_id as "\_id", person\_id as "\_parent",  
work\_name, genre, publisher from work",  
"poll" : "100m"  
},  
"index" : {  
"index" : "jdbcriver\_work",  
"type" : "jdbc"  
}  
}'

Can you tell me if I am missing something.

On Monday, 18 February 2013 13:25:03 UTC-5, Jörg Prante wrote:

> The JDBC river uses a "pseudo column" method fpr prante/child aware  
> indexing. Just like you can state a \_parent attribute in the bulk API,  
> you can name a column '\_parent' in the JDBC source to use this attribute.
> 
> It does not matter in what order you index parent/children docs as long  
> the parent exists (I admit I'm not even sure about this), so, you should  
> create the parent docs first. You can create a parent run with the  
> default "oneshot" river, and then, add another river for the children,  
> or even more. It's as simple as that.
> 
> Yes, the \_parent is the \_id attribute of the parent document.
> 
> Best regards,
> 
> Jörg
> 
> Am 18.02.13 18:55, schrieb Yann Barraud:
> 
> > Hi,
> > 
> > I'm currently trying to understand how to use JDBC River. I just got  
> > some good results this afternoon. 🙂
> > 
> > Now I have a few questions regarding the river :
> > 
> > - if I have 2 tables with 1 for parent items & two which are more  
> > child items, should I have 3 different rivers ?
> > - how to set the \_parent filed ? Is it the id of the parent object ?  
> > In ES ? And then, how to make this coherent with preceding question ?
> > 
> > Thanks.
> > 
> > Kind regards,  
> > Yann

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![A\_Daniel](https://avatars.discourse-cdn.com/v4/letter/a/fbc32d/32.png) [@A\_Daniel](https://discuss.elastic.co/u/A_Daniel)\
**Post date:** [May 16, 2013, 6:15pm UTC](https://discuss.elastic.co/t/jdbc-river--parent/10783/7 "2013-05-16T18:15:53Z")

</div>

Hi Jörg,

I am having trouble creating a parent-child relation between two tables  
using JDBC river. I have two tables "person" and "work".

Create table person (  
person\_id numeric,  
person\_name varchar2(100)  
)

create table work (  
work\_id numeric,  
person\_id numeric,  
work\_name varchar2(500),  
genre varchar2(100),  
publisher varchar2(500)  
)

I create a person index using this:

curl -XPUT 'localhost:9200/\_river/person/\_meta' -d '{  
"type" : "jdbc",  
"jdbc" : {  
"strategy" : "simple",  
"driver" : "oracle.jdbc.OracleDriver",  
"url" :  
"jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS\_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=myserver)(PORT=10000)))(CONNECT\_DATA=(SERVER=DEDICATED)(SERVICE\_NAME=MYDB)))",  
"user" : "myuser",  
"password" : "test123",  
"sql" : "select person\_id as "\_id", person\_name from person",  
"poll" : "100m"  
},  
"index" : {  
"index" : "jdbcriver\_person",  
"type" : "jdbc"  
}  
}'

I specify the mapping using this:

curl -XPOST 'localhost:9200/\_river/work/\_mapping' -d '{  
"work":{  
"\_parent": {"type": "person"}  
}  
}'

But when I run this command, I get a RoutingMissingException[routing is  
required for [\_river]/[work]/[\_meta].  
curl -XPUT 'localhost:9200/\_river/work/\_meta' -d '{  
"type" : "jdbc",  
"jdbc" : {  
"strategy" : "simple",  
"driver" : "oracle.jdbc.OracleDriver",  
"url" :  
"jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS\_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=myserver)(PORT=10000)))(CONNECT\_DATA=(SERVER=DEDICATED)(SERVICE\_NAME=MYDB)))",  
"user" : "myuser",  
"password" : "test123",  
"sql" : "select work\_id as "\_id", person\_id as "\_parent",  
work\_name, genre, publisher from work",  
"poll" : "100m"  
},  
"index" : {  
"index" : "jdbcriver\_work",  
"type" : "jdbc"  
}  
}'

Can you tell me if I am missing something.

On Monday, 18 February 2013 13:25:03 UTC-5, Jörg Prante wrote:

> The JDBC river uses a "pseudo column" method fpr prante/child aware  
> indexing. Just like you can state a \_parent attribute in the bulk API,  
> you can name a column '\_parent' in the JDBC source to use this attribute.
> 
> It does not matter in what order you index parent/children docs as long  
> the parent exists (I admit I'm not even sure about this), so, you should  
> create the parent docs first. You can create a parent run with the  
> default "oneshot" river, and then, add another river for the children,  
> or even more. It's as simple as that.
> 
> Yes, the \_parent is the \_id attribute of the parent document.
> 
> Best regards,
> 
> Jörg
> 
> Am 18.02.13 18:55, schrieb Yann Barraud:
> 
> > Hi,
> > 
> > I'm currently trying to understand how to use JDBC River. I just got  
> > some good results this afternoon. 🙂
> > 
> > Now I have a few questions regarding the river :
> > 
> > - if I have 2 tables with 1 for parent items & two which are more  
> > child items, should I have 3 different rivers ?
> > - how to set the \_parent filed ? Is it the id of the parent object ?  
> > In ES ? And then, how to make this coherent with preceding question ?
> > 
> > Thanks.
> > 
> > Kind regards,  
> > Yann

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [May 17, 2013, 12:26am UTC](https://discuss.elastic.co/t/jdbc-river--parent/10783/8 "2013-05-17T00:26:39Z")

</div>

Your data for a child document is not enough to fulfil the routing (the  
parent id in that case).

Can you please gist the stacktrace of the exception? And some example  
data so I can better reproduce?

Thanks,

Jörg

Am 16.05.13 20:13, schrieb A Daniel:

> But when I run the below command, I get a  
> RoutingMissingException[routing is required for [\_river]/[work]/[\_meta].

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![A\_Daniel](https://avatars.discourse-cdn.com/v4/letter/a/fbc32d/32.png) [@A\_Daniel](https://discuss.elastic.co/u/A_Daniel)\
**Post date:** [May 17, 2013, 2:27pm UTC](https://discuss.elastic.co/t/jdbc-river--parent/10783/9 "2013-05-17T14:27:22Z")

</div>

Hi Jörg,

Here is the data that I put into my tables.

Insert into PERSON (PERSON\_ID, PERSON\_NAME) Values (1, 'Person1');  
Insert into PERSON (PERSON\_ID, PERSON\_NAME) Values (2, 'Person2');  
COMMIT;

Insert into WORK (WORK\_ID, PERSON\_ID, WORK\_NAME, GENRE, PUBLISHER)  
Values (1, 1, 'P1Book1', 'Fiction', 'MyHouse');  
Insert into WORK (WORK\_ID, PERSON\_ID, WORK\_NAME, GENRE, PUBLISHER)  
Values (2, 1, 'P1Book2', 'Non-Fiction', 'MyHouse');  
Insert into WORK (WORK\_ID, PERSON\_ID, WORK\_NAME, GENRE, PUBLISHER)  
Values (3, 2, 'P2Book1', 'Fiction', 'MyHouse');  
Insert into WORK (WORK\_ID, PERSON\_ID, WORK\_NAME, GENRE, PUBLISHER)  
Values (4, 2, 'P2Book2', 'Non-Fiction', 'MyHouse');  
COMMIT;

The only entries that I see in the elasticsearch logs are shown below. I do  
not get any exception stack trace.

[2013-05-17 10:19:59,123][INFO][cluster.metadata] [ESNode1]  
[\_river] creating index, cause [auto(index api)], shards [1]/[1], mappings  
  
[2013-05-17 10:19:59,295][INFO][cluster.metadata] [ESNode1]  
[\_river] update\_mapping [person] (dynamic)  
[2013-05-17 10:19:59,308][DEBUG][river.jdbc] [ESNode1]  
[jdbc][person] found river source  
org.elasticsearch.river.jdbc.strategy.simple.SimpleRiverSource for strategy  
simple  
[2013-05-17 10:19:59,310][DEBUG][river.jdbc] [ESNode1]  
[jdbc][person] found river target  
org.elasticsearch.river.jdbc.strategy.simple.SimpleRiverMouth for strategy  
simple  
[2013-05-17 10:19:59,311][INFO  
][org.elasticsearch.river.jdbc.strategy.simple.SimpleRiverMouth] waiting  
for cluster...  
[2013-05-17 10:19:59,313][DEBUG][river.jdbc] [ESNode1]  
[jdbc][person] found river task  
org.elasticsearch.river.jdbc.strategy.simple.SimpleRiverFlow for strategy  
simple  
[2013-05-17 10:19:59,314][INFO][river.jdbc] [ESNode1]  
[jdbc][person] starting JDBC river: URL  
[jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS\_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=myserver)(PORT=10000)))(CONNECT\_DATA=(SERVER=DEDICATED)(SERVICE\_NAME=MYDB)))],  
driver [oracle.jdbc.OracleDriver], strategy [simple], index  
[jdbcriver\_person]/[jdbc]  
[2013-05-17 10:19:59,377][INFO][cluster.metadata] [ESNode1]  
[jdbcriver\_person] creating index, cause [api], shards [5]/[1], mappings   
[2013-05-17 10:19:59,597][INFO][cluster.metadata] [ESNode1]  
[\_river] update\_mapping [person] (dynamic)  
[2013-05-17 10:19:59,633][INFO  
][org.elasticsearch.river.jdbc.strategy.simple.SimpleRiverSource] merged 2  
rows  
[2013-05-17  
10:19:59,633][DEBUG][org.elasticsearch.river.jdbc.strategy.simple.SimpleRiverFlow]  
{"jdbc":{"created":"2013-05-17T14:19:59.315Z","version":1,"digest":"2Mq+WYAP7eWwiikKMAlUPvrn8V3g65I855gkUWl0ZNE="}}  
[2013-05-17 10:19:59,644][INFO  
][org.elasticsearch.river.jdbc.strategy.simple.SimpleRiverFlow] next run,  
waiting 1.6h  
[2013-05-17 10:19:59,647][INFO][cluster.metadata] [ESNode1]  
[\_river] update\_mapping [person] (dynamic)  
[2013-05-17 10:20:00,313][INFO  
][org.elasticsearch.river.jdbc.strategy.simple.SimpleRiverMouth] new bulk  
[1] of [2 items], 1 outstanding bulk requests  
[2013-05-17 10:20:00,321][INFO  
][org.elasticsearch.river.jdbc.strategy.simple.SimpleRiverMouth] bulk [1]  
success [2 items] [8ms]  
[2013-05-17 10:20:00,324][INFO][cluster.metadata] [ESNode1]  
[jdbcriver\_person] update\_mapping [jdbc] (dynamic)  
[2013-05-17 10:20:12,268][INFO][cluster.metadata] [ESNode1]  
[\_river] create\_mapping [work]

On Thursday, 16 May 2013 20:26:39 UTC-4, Jörg Prante wrote:

> Your data for a child document is not enough to fulfil the routing (the  
> parent id in that case).
> 
> Can you please gist the stacktrace of the exception? And some example  
> data so I can better reproduce?
> 
> Thanks,
> 
> Jörg
> 
> Am 16.05.13 20:13, schrieb A Daniel:
> 
> > But when I run the below command, I get a  
> > RoutingMissingException[routing is required for [\_river]/[work]/[\_meta].

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [May 17, 2013, 2:38pm UTC](https://discuss.elastic.co/t/jdbc-river--parent/10783/10 "2013-05-17T14:38:35Z")

</div>

Thanks, just give me some time to let me reproduce.

Jörg

Am 17.05.13 16:27, schrieb A Daniel:

> Here is the data that I put into my tables.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:36am UTC](https://discuss.elastic.co/t/jdbc-river--parent/10783/11 "2017-07-06T02:36:02Z")

</div>


