Hi David and Jörg,
Many thanks for your help. Finally I can found the problem. It was in the
version of the postgres driver.
Kind regards!!!
Jorge von Rudno
2014-06-25 18:01 GMT+02:00 joergpra...@gmail.com joergpra...@gmail.com:
You did not specify an index for the JDBC river to index to,
Dear colleagues,
I just start to work with ES and after read the documentation, I am trying
to load the data from my postgres db. To do this I found that the plugin
river jdbc should be work for this purpose.
After following the instruction to install the plugin, I run the following
command
How did you run your search?
By any chance did you search in _river index?
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 25 juin 2014 à 11:00:08, Jorge von Rudno (jorge.vonrudno...@googlemail.com)
a écrit:
Dear colleagues,
I just start to work
You should not query the _river index but the `customers` index I think.
Just check what gives GET /_search
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 25 juin 2014 à 13:05:37, Jorge von Rudno (jorge.vonrudno...@googlemail.com)
a écrit:
Hi
Hi David,
When I run I GET /_search, I get some documents but not what I expect
(some index about .marvel . The river should be generate around 1 million
documents.
I just delete all and change the index name by cm_customer
PUT /cm_customer/customers/
{
type : jdbc,
jdbc : {
url :
You need to create the river in _river special index. Otherwise it won't be
considered as a river.
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 25 juin 2014 à 15:21:10, Jorge von Rudno (jorge.vonrudno...@googlemail.com)
a écrit:
Hi David,
When I
You did not specify an index for the JDBC river to index to, so it assumes
the index name is jdbc.
It means, if you search
curl '0:9200/jdbc/_search'
you should see some of the indexed documents.
Jörg
On Wed, Jun 25, 2014 at 11:00 AM, Jorge von Rudno
jorge.vonrudno...@googlemail.com wrote:
