There is no index section any more.

Try

curl -XPUT "http://localhost:9200/_river/table_river/_meta"; -d'{
    "type" : "jdbc",
    "jdbc" : {
        "url" : "jdbc:mysql://host/db",
        "user" : "x",
        "password" : "y",
        "sql" : "select * from table",
        "index" : "index_name",
        "type" : "type_name"
    }
}'

Jörg



On Sun, Feb 16, 2014 at 7:28 PM, Tomislav Poljak <tpol...@gmail.com> wrote:

> Hi,
> I've tried new/latest jdbc river plugin for elasticsearch 1.0.0 (with
> the latest es v1.0.0) and simple river definition:
>
> curl -XPUT "http://localhost:9200/_river/table_river/_meta"; -d'{
>     "type" : "jdbc",
>     "jdbc" : {
>         "driver" : "com.mysql.jdbc.Driver",
>         "url" : "jdbc:mysql://host/db",
>         "user" : "x",
>         "password" : "y",
>         "sql" : "select * from table"
>     },
>     "index" : {
>         "index" : "index_name",
>         "type" : "type_name"
>     }
> }'
>
> ended up importing data into index named 'jdbc' (instead 'index_name')
> and type set in indexed docs was also 'jdbc' (instead of type_name)
>
> Did something changed (completely) in how jdbc river is defined (I've
> checked the docs didn't find anything) or is this a bug?
>
> Tomislav
>
> 2014-02-13 1:37 GMT+01:00 joergpra...@gmail.com <joergpra...@gmail.com>:
> > Hi,
> >
> > JDBC river plugin 1.0.0.1 for Elasticsearch 1.0.0 has been released.
> >
> > https://github.com/jprante/elasticsearch-river-jdbc
> >
> > Changes:
> >
> > - compiled against Elasticsearch 1.0.0
> > - refactored some classes for preparing the move to a more robust data
> > gathering plugin
> > - improved JSON building when reading JSON out of a result column
> > - possible to access river state (timestamp) as SQL parameter
> > - reverted Collection to List in KeyValueStreamListener
> > - some cleanups
> >
> > Best,
> >
> > Jörg
> >
> > --
> > 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+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFrCUx6xB%3D40UTu6BgL8fKaQDrQ57ANexr569tfKVgGSg%40mail.gmail.com
> .
> > For more options, visit 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/CALuCJxgmZ%2BqWgNenAEuuo22R%2BhrXCHfXTzWyTL72Z4iwqZ962A%40mail.gmail.com
> .
> For more options, visit 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHw%2Be5GLBR2sho0VJZva7w_sTiY0Kvfe-w0UpqQ%2BMu6Qg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to