Are rivers still being deprecated?

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 Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEFAe-FJqdk6yzV8i9E4DFrveDhabNDrk5wLeETYrJf1mB2L4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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 Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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
clearly advisable to keep such components in an architecture separate
and not to interweave them more than necessary. The notorious data
import handlers of SolrCloud demonstrate where this leads to.

I don't know what stance the Elasticsearch folks take towards rivers,
but from an architectural point of view, the clear separation from
Elasticsearch seems like a good mid- to long-term goal to go for.

My 5 EUR-cents worth of feedback...

--Jürgen

On 16.11.2014 21:24, Otis Gospodnetic wrote:

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
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearch+unsubscribe@googlegroups.com
mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout.

--

Mit freundlichen Grüßen/Kind regards/Cordialement vôtre/Atentamente/С
уважением
i.A. Jürgen Wagner
Head of Competence Center "Intelligence"
& Senior Cloud Consultant

Devoteam GmbH, Industriestr. 3, 70565 Stuttgart, Germany
Phone: +49 6151 868-8725, Fax: +49 711 13353-53, Mobile: +49 171 864 1543
E-Mail: juergen.wagner@devoteam.com
mailto:juergen.wagner@devoteam.com, URL: www.devoteam.de
http://www.devoteam.de/


Managing Board: Jürgen Hatzipantelis (CEO)
Address of Record: 64331 Weiterstadt, Germany; Commercial Register:
Amtsgericht Darmstadt HRB 6450; Tax Number: DE 172 993 071

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/546913B8.7080409%40devoteam.com.
For more options, visit https://groups.google.com/d/optout.

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

Thanks,

Jörg

On Sun, Nov 16, 2014 at 10:14 PM, "Jürgen Wagner (DVT)" <
juergen.wagner@devoteam.com> wrote:

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 clearly
advisable to keep such components in an architecture separate and not to
interweave them more than necessary. The notorious data import handlers of
SolrCloud demonstrate where this leads to.

I don't know what stance the Elasticsearch folks take towards rivers, but
from an architectural point of view, the clear separation from
Elasticsearch seems like a good mid- to long-term goal to go for.

My 5 EUR-cents worth of feedback...

--Jürgen

On 16.11.2014 21:24, Otis Gospodnetic wrote:

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 Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--

Mit freundlichen Grüßen/Kind regards/Cordialement vôtre/Atentamente/С
уважением
i.A. Jürgen Wagner
Head of Competence Center "Intelligence"
& Senior Cloud Consultant

Devoteam GmbH, Industriestr. 3, 70565 Stuttgart, Germany
Phone: +49 6151 868-8725, Fax: +49 711 13353-53, Mobile: +49 171 864 1543
E-Mail: juergen.wagner@devoteam.com, URL: www.devoteam.de

Managing Board: Jürgen Hatzipantelis (CEO)
Address of Record: 64331 Weiterstadt, Germany; Commercial Register:
Amtsgericht Darmstadt HRB 6450; Tax Number: DE 172 993 071

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/546913B8.7080409%40devoteam.com
https://groups.google.com/d/msgid/elasticsearch/546913B8.7080409%40devoteam.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEMTZ4HLXccrcQM-S0MP3o2VD0y8pq9Zm3WV9a%3DN2L%3DQw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Hi,

On Sun, Nov 16, 2014 at 4:49 PM, joergprante@gmail.com <
joergprante@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 Import Handler (DIH) in
Solr is similarly not the greatest way to index data in Solr even though it
was (and still is) super popular.

Otis

Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support * http://sematext.com/

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

Thanks,

Jörg

On Sun, Nov 16, 2014 at 10:14 PM, "Jürgen Wagner (DVT)" <
juergen.wagner@devoteam.com> wrote:

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 clearly
advisable to keep such components in an architecture separate and not to
interweave them more than necessary. The notorious data import handlers of
SolrCloud demonstrate where this leads to.

I don't know what stance the Elasticsearch folks take towards rivers, but
from an architectural point of view, the clear separation from
Elasticsearch seems like a good mid- to long-term goal to go for.

My 5 EUR-cents worth of feedback...

--Jürgen

On 16.11.2014 21:24, Otis Gospodnetic wrote:

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 Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--

Mit freundlichen Grüßen/Kind regards/Cordialement vôtre/Atentamente/С
уважением
i.A. Jürgen Wagner
Head of Competence Center "Intelligence"
& Senior Cloud Consultant

Devoteam GmbH, Industriestr. 3, 70565 Stuttgart, Germany
Phone: +49 6151 868-8725, Fax: +49 711 13353-53, Mobile: +49 171 864 1543
E-Mail: juergen.wagner@devoteam.com, URL: www.devoteam.de

Managing Board: Jürgen Hatzipantelis (CEO)
Address of Record: 64331 Weiterstadt, Germany; Commercial Register:
Amtsgericht Darmstadt HRB 6450; Tax Number: DE 172 993 071

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/546913B8.7080409%40devoteam.com
https://groups.google.com/d/msgid/elasticsearch/546913B8.7080409%40devoteam.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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/XW05vCHp_pY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEMTZ4HLXccrcQM-S0MP3o2VD0y8pq9Zm3WV9a%3DN2L%3DQw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEMTZ4HLXccrcQM-S0MP3o2VD0y8pq9Zm3WV9a%3DN2L%3DQw%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CANNBgPJioLbePbu_TxOzyz2sxmneY_07TSvkJwdjp091fNV%2B7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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? What's the currently recommended approach?

Regards,
Alex.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d7638967-0cbc-4ab7-b2ce-2646116423c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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 pswenson@itriagehealth.com
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 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 Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/d7638967-0cbc-4ab7-b2ce-2646116423c8%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/d7638967-0cbc-4ab7-b2ce-2646116423c8%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9vjYZbb9oDm%2B6Z9neS1hKvL_mjjAM-Rh4bzMKUTqmWQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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 river is running inside a
Elasticsearch JVM. Would that not be mitigated by having a seperate
instance of Elasticsearch running the river process that would be a client
to the cluster?

On Friday, November 7, 2014 2:17:36 AM UTC, 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 Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e853e0cb-7cfb-4f72-a256-08fa74b5e735%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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 "Elvar Böðvarsson" elvarb@gmail.com:

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 river is running inside a
Elasticsearch JVM. Would that not be mitigated by having a seperate
instance of Elasticsearch running the river process that would be a client
to the cluster?

On Friday, November 7, 2014 2:17:36 AM UTC, 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 Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/e853e0cb-7cfb-4f72-a256-08fa74b5e735%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/e853e0cb-7cfb-4f72-a256-08fa74b5e735%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE-%2B2uZpSCFPUXe5efa5fOfG_5YLhqwi20mLdf0EM313A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.