Elasticsearch JDBC River problem

Hello,

I have a problem with JPrante JDBC river.

The first time the river runs it imports all the data in ES (296
Documents or so), but on the second time "I think" for an unknown reason
that the house keeper deletes all the documents even if the log said 0
document deleted. The fact is that I have only 3 documents left after the
second import.... Im wondering what i'm doing wrong...

I'm runnnig ES server 0.90, on a single node with jprante 2.2.1 river.

Any help will be appreciated!

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

Louis,

Could you run your select query on SQL and gist the results?
I suspect that your query is returning the same id many times and so the river update the same document many time.

HTH

David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 12 juin 2013 à 15:40, Louis Bedard foutchy@gmail.com a écrit :

Hello,

I have a problem with JPrante JDBC river.

The first time the river runs it imports all the data in ES (296 Documents or so), but on the second time "I think" for an unknown reason that the house keeper deletes all the documents even if the log said 0 document deleted. The fact is that I have only 3 documents left after the second import.... Im wondering what i'm doing wrong...

I'm runnnig ES server 0.90, on a single node with jprante 2.2.1 river.

Any help will be appreciated!

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

<data.json><mapping.json><elasticsearch.log>

Hi,

I got some duplicated IDs but nothing near 3 distinct one. And your are
right that _version > 1, In fact it's > 1000

So now the question is, how could I avoid those duplicated ids and tell
ES what to do with it ?

I joigned a subset of the resultset

Le mercredi 12 juin 2013 09:43:36 UTC-4, David Pilato a écrit :

Louis,

Could you run your select query on SQL and gist the results?
I suspect that your query is returning the same id many times and so the
river update the same document many time.

HTH

David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 12 juin 2013 à 15:40, Louis Bedard <fou...@gmail.com <javascript:>> a
écrit :

Hello,

I have a problem with JPrante JDBC river.

The first time the river runs it imports all the data in ES (296
Documents or so), but on the second time "I think" for an unknown reason
that the house keeper deletes all the documents even if the log said 0
document deleted. The fact is that I have only 3 documents left after the
second import.... Im wondering what i'm doing wrong...

I'm runnnig ES server 0.90, on a single node with jprante 2.2.1 river.

Any help will be appreciated!

--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.

<data.json><mapping.json><elasticsearch.log>

--
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.
For more options, visit https://groups.google.com/groups/opt_out.