Hello,
I wrote a river for GitHub data (events, issues & open pull requests). You
There's a section for community-supported plugins [1] for elasticsearch,
[1] https://github.com/uberVU/elasticsearch-river-github http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-plugins.html
Thank you,
Mihnea Dobrescu-Balaur
--elasticsearch+unsubscribe@googlegroups.com .https://groups.google.com/d/msgid/elasticsearch/5b113d0e-1fe9-4575-a345-ae11110bdca5%40googlegroups.com .https://groups.google.com/groups/opt_out .
dadoonet
February 7, 2014, 10:13pm
2
Nice!
You should use BulkProcessor to process your data instead of running single index operations. It will be much faster.
To add your plugin, send a pull request in elasticsearch/elasticsearch repo. (Look inside /docs)
Best
--@dadoonet / @elasticsearchfr / @scrutmydocs
Le 7 févr. 2014 à 22:24, Mihnea Dobrescu-Balaur mihneadb@gmail.com a écrit :
Hello,
I wrote a river for GitHub data (events, issues & open pull requests). You can find it here[1], I hope it will be useful to some people :).
There's a section for community-supported plugins [1] for elasticsearch, and I was wondering: what's the process for having it added to that list?
[1] https://github.com/uberVU/elasticsearch-river-github http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-plugins.html
Thank you,
Mihnea Dobrescu-Balaur
You received this message because you are subscribed to the Google Groups "elasticsearch" group.elasticsearch+unsubscribe@googlegroups.com .https://groups.google.com/d/msgid/elasticsearch/5b113d0e-1fe9-4575-a345-ae11110bdca5%40googlegroups.com .https://groups.google.com/groups/opt_out .
--elasticsearch+unsubscribe@googlegroups.com .https://groups.google.com/d/msgid/elasticsearch/322C0493-3620-4372-8B27-186C07297C86%40pilato.fr .https://groups.google.com/groups/opt_out .
On Sat, Feb 8, 2014 at 12:13 AM, David Pilato david@pilato.fr wrote:
Nice!
You should use BulkProcessor to process your data instead of running single
Makes sense, thanks! Will do, next "release".
To add your plugin, send a pull request in elasticsearch/elasticsearch repo.
Cool, thanks!
--
--elasticsearch+unsubscribe@googlegroups.com .https://groups.google.com/d/msgid/elasticsearch/CAGmmvX%2Bvcwo%2Bhxx9%2BcAVBwo2tFoVsGeeoVpH8VH3vC%3DAe-ZA4Q%40mail.gmail.com .https://groups.google.com/groups/opt_out .
On Sat, Feb 8, 2014 at 3:16 PM, Mihnea Dobrescu-Balaur mihnea@linux.com wrote:
On Sat, Feb 8, 2014 at 12:13 AM, David Pilato david@pilato.fr wrote:
Nice!
You should use BulkProcessor to process your data instead of running single
Makes sense, thanks! Will do, next "release".
To add your plugin, send a pull request in elasticsearch/elasticsearch repo.
Cool, thanks!
Opened the pull req: [DOCS] Add GitHub community river plugin by mihneadb · Pull Request #5056 · elastic/elasticsearch · GitHub
--
--elasticsearch+unsubscribe@googlegroups.com .https://groups.google.com/d/msgid/elasticsearch/CAGmmvX%2B21zADtJo8BVu4j0GZ065od5C%2BAcGJ2xj7Add5hT5FNg%40mail.gmail.com .https://groups.google.com/groups/opt_out .
On Sat, Feb 8, 2014 at 2:16 PM, Mihnea Dobrescu-Balaur mihnea@linux.com wrote:
On Sat, Feb 8, 2014 at 12:13 AM, David Pilato david@pilato.fr wrote:
Nice!
You should use BulkProcessor to process your data instead of running single
Makes sense, thanks! Will do, next "release".
As promised, the river now uses BulkProcessor. It also fetches
Mihnea Dobrescu-Balaur
--elasticsearch+unsubscribe@googlegroups.com .https://groups.google.com/d/msgid/elasticsearch/CAGmmvXK-tbvdMqAqwLncqPiiUjpjb5LSDBpuSQoQ8w6HFt%2BpLg%40mail.gmail.com .https://groups.google.com/groups/opt_out .
