Can you elaborate what you mean by JDBC feeder plugin "only works in Linux"?
I have running it on Mac OS X and Solaris.
BTW you can configure ES to run rivers on specific (dedicated) nodes only.
They can be data-less so they do not interfere with search/indexing.
Jörg
Am 10.12.2014 20:53 schrieb
I know that feeders will replace them, for example the JDBC plugin ships
with a early version of a feeder but it only works in Linux at the moment.
Are there any project out there that provide a feeder functionality similar
to what rivers are now?
Also, the bad thing about rivers is that the ri
They are still planned to be deprecated, but there is no timeline for it as
yet.
On 10 December 2014 at 19:44, Phil Swenson
wrote:
> did you ever find an answer to this question?
>
>
>
> On Thursday, November 6, 2014 7:17:36 PM UTC-7, Alexandre Rafalovitch
> wrote:
>>
>> ElasticSearch 1.4 is out
did you ever find an answer to this question?
On Thursday, November 6, 2014 7:17:36 PM UTC-7, Alexandre Rafalovitch wrote:
>
> ElasticSearch 1.4 is out and I can't see any mentions that Rivers are
> deprecated.
>
> Has that (informal) decision been reversed? Or was the timeline
> further out?
Hi,
On Sun, Nov 16, 2014 at 4:49 PM, joergpra...@gmail.com <
joergpra...@gmail.com> wrote:
> Can you explain how you compare rivers with SolrCloud data import handlers?
>
They are similar in the sense that they both run inside their containers
(Solr/SolrCloud or ES) and *pull* data in. Data Imp
Can you explain how you compare rivers with SolrCloud data import handlers?
Rivers were once designed as a singleton to fetch data very quick for
prototyping and demo purpose, not more. With the official ES client
families, and with logstash / message queue "push" architecture, they can
often be r
Hello,
we generally don't use rivers as it does not seem to be a good idea to
put too much of connector functionality into a search nodes themselves.
The scaling of connectors and feeding is entirely different from that of
processing and indexing or querying. That's why it is in my opinion
clearl
We've seen issues with Rivers in the past and no longer use them in our
engagements.
Otis
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support * http://sematext.com/
On Thursday, November 6, 2014 9:17:36 PM UTC-5, Alexandre Rafalovitch wrote:
>
ElasticSearch 1.4 is out and I can't see any mentions that Rivers are
deprecated.
Has that (informal) decision been reversed? Or was the timeline
further out? What's the currently recommended approach?
Regards,
Alex.
--
You received this message because you are subscribed to the Google Group
