Jdbc river


(Fabricio Archanjo) #1

Hi All,

I'm learning elasticsearch to change my search engine on my website.
I have one doubt abou that. Can I add new documents to the index after
oneshot? I'd like to add new documents incrementally, is it possible?

Thanks for all,

Fabricio Archanjo

--
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.


(Jörg Prante) #2

The JDBC river "oneshot" is thought for quick success, and then forget
about it (demo mode).

Currently there are some deficiencies (bugs?) to detect new rows. To make
it simple, the JDBC river needs some overhaul of the "strategies" design
that fetch the data, for becoming more feasible in everyday situations.

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


(Fabricio Archanjo) #3

Currently there are some deficiencies (bugs?) to detect new rows.

Detect new rows via sql, right?

I'd like to add new documents via PUT on elasticsearch. The oneshot is
going to make an index once for me, after my app is going to feed this
index created by plugin.

Thanks Jörg,

On Wed, Sep 11, 2013 at 9:57 AM, joergprante@gmail.com <
joergprante@gmail.com> wrote:

The JDBC river "oneshot" is thought for quick success, and then forget
about it (demo mode).

Currently there are some deficiencies (bugs?) to detect new rows. To make
it simple, the JDBC river needs some overhaul of the "strategies" design
that fetch the data, for becoming more feasible in everyday situations.

Jörg

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/Td6QJrGMC1k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(lebowitz) #4

You can use Jörg's table strategy, which implements a fixed sliding window of time query. One for an int64 primary key would be nice.

--
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.


(system) #5