Hi, On Sun, Nov 16, 2014 at 4:49 PM, [email protected] < [email protected]> 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)" < > [email protected]> 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 [email protected]. >> 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: [email protected], 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 [email protected]. >> 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 > [email protected]. > 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 [email protected]. 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.
