[ANN] Elasticsearch Twitter River plugin 2.2.0 released


(David Pilato) #1

Heya,

We are pleased to announce the release of the Elasticsearch Twitter River plugin, version 2.2.0.

The Twitter River plugin allows index twitter stream using elasticsearch rivers feature.

Release Notes - elasticsearch-river-twitter - Version 2.2.0

Fix:

Update:

New:

Doc:

Issues, Pull requests, Feature requests are warmly welcome on elasticsearch-river-twitter project repository: https://github.com/elasticsearch/elasticsearch-river-twitter/
For questions or comments around this plugin, feel free to use elasticsearch mailing list: https://groups.google.com/forum/#!forum/elasticsearch

Enjoy,

-The Elasticsearch team

--
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/53cfa3ef.8124b40a.2b81.3571SMTPIN_ADDED_MISSING%40gmr-mx.google.com.
For more options, visit https://groups.google.com/d/optout.


(James Green) #2

I was told a week or two ago on IRC that rivers were deprecated in favour
of external data sources like Logstash.

Is this not correct?

On 23 July 2014 13:00, Elasticsearch Team david@pilato.fr wrote:

Heya,

We are pleased to announce the release of the Elasticsearch Twitter
River plugin
, version 2.2.0

The Twitter River plugin allows index twitter stream using elasticsearch
rivers feature.

Release Notes - Version 2.2.0 Fix

Update

New

Doc

Issues, Pull requests, Feature requests are warmly welcome on
elasticsearch-river-twitter
https://github.com/elasticsearch/elasticsearch-river-twitter/ project
repository!

For questions or comments around this plugin, feel free to use
elasticsearch mailing list
https://groups.google.com/forum/#!forum/elasticsearch!

Enjoy,

--
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/53cfa3ef.8124b40a.2b81.3571SMTPIN_ADDED_MISSING%40gmr-mx.google.com
https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN_ADDED_MISSING%40gmr-mx.google.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%2Bawb9LYHPnm_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #3

Rivers will be deprecated in favor of logstash inputs.
Deprecated does not mean removed yet.
So in the meantime we still try to keep up to date official plugins.

But yes, you should prefer using if possible logstash twitter input (http://logstash.net/docs/1.4.2/inputs/twitter)

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr

Le 23 juillet 2014 à 14:08:49, James Green (james.mk.green@gmail.com) a écrit:

I was told a week or two ago on IRC that rivers were deprecated in favour of external data sources like Logstash.

Is this not correct?

On 23 July 2014 13:00, Elasticsearch Team david@pilato.fr wrote:
Heya,

We are pleased to announce the release of the Elasticsearch Twitter River plugin, version 2.2.0

The Twitter River plugin allows index twitter stream using elasticsearch rivers feature.
Release Notes - Version 2.2.0

Fix

[62] - Generate default mapping even if index already exists
[60] - ignore_retweets does not ignore RT
Update

[61] - Update to Twitter4J 4.0.2
[58] - Remove old deprecated user and password properties
[57] - Deprecate usage of camelCase settings
[54] - Added not_analyzed to retweet user_screen_name
[52] - Update to elasticsearch 1.2.0
New

[56] - Add oauth credentials in elasticsearch.yml file
[51] - Support geo location array format
[50] - Add user stream support
[37] - Move tests to elasticsearch test framework
Doc

[49] - [DOC] Link to rivers documentation is incorrect
Issues, Pull requests, Feature requests are warmly welcome on elasticsearch-river-twitter project repository!

For questions or comments around this plugin, feel free to use elasticsearch mailing list!

Enjoy,

  • The Elasticsearch team

--
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/53cfa3ef.8124b40a.2b81.3571SMTPIN_ADDED_MISSING%40gmr-mx.google.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%2Bawb9LYHPnm_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%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/etPan.53cfa6ef.507ed7ab.13e40%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.


(Andrej) #4

Hi David,

does that mean in conclusion that there will be a rss input for logstash
soon as replacement of the river? Same goes for wikipedia?

Greets,
Andrej

Am Mittwoch, 23. Juli 2014 14:13:51 UTC+2 schrieb David Pilato:

Rivers will be deprecated in favor of logstash inputs.
Deprecated does not mean removed yet.
So in the meantime we still try to keep up to date official plugins.

But yes, you should prefer using if possible logstash twitter input (
http://logstash.net/docs/1.4.2/inputs/twitter)

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr

Le 23 juillet 2014 à 14:08:49, James Green (james.m...@gmail.com
<javascript:>) a écrit:

I was told a week or two ago on IRC that rivers were deprecated in favour
of external data sources like Logstash.

Is this not correct?

On 23 July 2014 13:00, Elasticsearch Team <da...@pilato.fr <javascript:>>
wrote:

Heya,

We are pleased to announce the release of the Elasticsearch Twitter
River plugin
, version 2.2.0

The Twitter River plugin allows index twitter stream using elasticsearch
rivers feature.

Release Notes - Version 2.2.0 Fix

Update

New

Doc

Issues, Pull requests, Feature requests are warmly welcome on
elasticsearch-river-twitter
https://github.com/elasticsearch/elasticsearch-river-twitter/ project
repository!

For questions or comments around this plugin, feel free to use
elasticsearch mailing list
https://groups.google.com/forum/#!forum/elasticsearch!

Enjoy,

--
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%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/c521027a-16e1-4b3b-85bc-14c370323de7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #5

Hi Andrej

That's the plan indeed.
About "soon", I don't know :slight_smile:

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr

Le 24 juillet 2014 à 13:42:25, Andrej Rosenheinrich (andrej.rosenheinrich@unister.de) a écrit:

Hi David,

does that mean in conclusion that there will be a rss input for logstash soon as replacement of the river? Same goes for wikipedia?

Greets,
Andrej

Am Mittwoch, 23. Juli 2014 14:13:51 UTC+2 schrieb David Pilato:
Rivers will be deprecated in favor of logstash inputs.
Deprecated does not mean removed yet.
So in the meantime we still try to keep up to date official plugins.

But yes, you should prefer using if possible logstash twitter input (http://logstash.net/docs/1.4.2/inputs/twitter)

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr

Le 23 juillet 2014 à 14:08:49, James Green (james.m...@gmail.com) a écrit:

I was told a week or two ago on IRC that rivers were deprecated in favour of external data sources like Logstash.

Is this not correct?

On 23 July 2014 13:00, Elasticsearch Team da...@pilato.fr wrote:
Heya,

We are pleased to announce the release of the Elasticsearch Twitter River plugin, version 2.2.0

The Twitter River plugin allows index twitter stream using elasticsearch rivers feature.
Release Notes - Version 2.2.0

Fix

[62] - Generate default mapping even if index already exists
[60] - ignore_retweets does not ignore RT
Update

[61] - Update to Twitter4J 4.0.2
[58] - Remove old deprecated user and password properties
[57] - Deprecate usage of camelCase settings
[54] - Added not_analyzed to retweet user_screen_name
[52] - Update to elasticsearch 1.2.0
New

[56] - Add oauth credentials in elasticsearch.yml file
[51] - Support geo location array format
[50] - Add user stream support
[37] - Move tests to elasticsearch test framework
Doc

[49] - [DOC] Link to rivers documentation is incorrect
Issues, Pull requests, Feature requests are warmly welcome on elasticsearch-river-twitter project repository!

For questions or comments around this plugin, feel free to use elasticsearch mailing list!

Enjoy,

  • The Elasticsearch team

--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN_ADDED_MISSING%40gmr-mx.google.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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%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/c521027a-16e1-4b3b-85bc-14c370323de7%40googlegroups.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/etPan.53d0f211.737b8ddc.13e40%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.


(system) #6