[ANN] Deprecating Rivers

Hi All,
We've recently announced that Rivers in Elasticsearch are actively
deprecated as of the 1.5 release, the 2.0 release will still maintain that
functionality to ease migration, but we recommend you start to leverage the
official clients to replace any Rivers you may have in use.

If you have feedback around this process then feel free to add a comment to
this Github issue - https://github.com/elastic/elasticsearch/issues/10345

And for more information please see this blog post on our site -

--
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/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Good luck with this when "Elasticsearch Team" is continuing to email the
list with river plugin updates and asking for feature requests to their
github projects.

On 1 April 2015 at 23:30, Mark Walkom mark@walkom.id.au wrote:

Hi All,
We've recently announced that Rivers in Elasticsearch are actively
deprecated as of the 1.5 release, the 2.0 release will still maintain that
functionality to ease migration, but we recommend you start to leverage the
official clients to replace any Rivers you may have in use.

If you have feedback around this process then feel free to add a comment
to this Github issue -
https://github.com/elastic/elasticsearch/issues/10345

And for more information please see this blog post on our site -
https://www.elastic.co/blog/deprecating_rivers

--
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/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%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/CAMH6%2BaxMe0yPQyRCWB0e8RytsvPt67OFxoH71RBE%3Dh_GcEfA-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Fair enough. I will remove this part of the « signature » in next emails.

--
David Pilato - Developer | Evangelist
elastic.co
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr https://twitter.com/elasticsearchfr | @scrutmydocs https://twitter.com/scrutmydocs

Le 2 avr. 2015 à 10:00, James Green james.mk.green@gmail.com a écrit :

Good luck with this when "Elasticsearch Team" is continuing to email the list with river plugin updates and asking for feature requests to their github projects.

On 1 April 2015 at 23:30, Mark Walkom <mark@walkom.id.au mailto:mark@walkom.id.au> wrote:
Hi All,
We've recently announced that Rivers in Elasticsearch are actively deprecated as of the 1.5 release, the 2.0 release will still maintain that functionality to ease migration, but we recommend you start to leverage the official clients to replace any Rivers you may have in use.

If you have feedback around this process then feel free to add a comment to this Github issue - https://github.com/elastic/elasticsearch/issues/10345 https://github.com/elastic/elasticsearch/issues/10345

And for more information please see this blog post on our site - https://www.elastic.co/blog/deprecating_rivers https://www.elastic.co/blog/deprecating_rivers

--
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/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%40mail.gmail.com https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%40mail.gmail.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout 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 mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAMH6%2BaxMe0yPQyRCWB0e8RytsvPt67OFxoH71RBE%3Dh_GcEfA-Q%40mail.gmail.com https://groups.google.com/d/msgid/elasticsearch/CAMH6%2BaxMe0yPQyRCWB0e8RytsvPt67OFxoH71RBE%3Dh_GcEfA-Q%40mail.gmail.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout 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/782C3D2A-727C-4B2C-BB3B-78352548CCCD%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Also note that the current documentation lists a load of river plugins
without stating that they are officially deprecated as an idea:

http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-plugins.html

Rather concerned that people are still adopting rivers due to the apparent
continued promotion of them. If you have not already, I suggest each time a
node fires up and detects a river plugin it issues at least a warning in a
log to remove it in favour of alternatives such as logstash. At least the
official rivers are marked deprecated in their readme but not everyone will
spot this.

On 1 April 2015 at 23:30, Mark Walkom mark@walkom.id.au wrote:

Hi All,
We've recently announced that Rivers in Elasticsearch are actively
deprecated as of the 1.5 release, the 2.0 release will still maintain that
functionality to ease migration, but we recommend you start to leverage the
official clients to replace any Rivers you may have in use.

If you have feedback around this process then feel free to add a comment
to this Github issue -
https://github.com/elastic/elasticsearch/issues/10345

And for more information please see this blog post on our site -
https://www.elastic.co/blog/deprecating_rivers

--
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/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%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/CAMH6%2Bazr1yamseHfSD9HriTqyos6uLJ7zX3qa%2B7oqom24qCeCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

I agree James. That's a nice suggestion (warn when running deprecated code).
BTW we have a lot of work in the code such as mark some Java classes as deprecated, modify docs...

Things will come.

IMO it's better to announce the deprecation sooner than later. That's the purpose of this blog post.
So community can react as you just did or anticipate on their architecture design decisions.

My cents on it.

David

Le 8 avr. 2015 à 10:01, James Green james.mk.green@gmail.com a écrit :

Also note that the current documentation lists a load of river plugins without stating that they are officially deprecated as an idea:

http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-plugins.html

Rather concerned that people are still adopting rivers due to the apparent continued promotion of them. If you have not already, I suggest each time a node fires up and detects a river plugin it issues at least a warning in a log to remove it in favour of alternatives such as logstash. At least the official rivers are marked deprecated in their readme but not everyone will spot this.

On 1 April 2015 at 23:30, Mark Walkom mark@walkom.id.au wrote:
Hi All,
We've recently announced that Rivers in Elasticsearch are actively deprecated as of the 1.5 release, the 2.0 release will still maintain that functionality to ease migration, but we recommend you start to leverage the official clients to replace any Rivers you may have in use.

If you have feedback around this process then feel free to add a comment to this Github issue - https://github.com/elastic/elasticsearch/issues/10345

And for more information please see this blog post on our site - https://www.elastic.co/blog/deprecating_rivers

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/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%40mail.gmail.com.
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/CAMH6%2Bazr1yamseHfSD9HriTqyos6uLJ7zX3qa%2B7oqom24qCeCA%40mail.gmail.com.
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/C0038380-367E-457F-B207-775E48E1F0A5%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.