There is nothing magical about rivers. With some Java code changes, most
rivers can be made to run as standalone Java processes. The only thing the
rivers do is (weakly) guarantee that only one river instance is run per
cluster.
Cheers,
Ivan
On Mon, Oct 27, 2014 at 4:11 AM, joergpra...@gmail.com
Yes, there is already a substitution, the JDBC feeder in the JDBC river
repo.
Future versions of JDBC river will no longer rely on the river API.
Jörg
On Mon, Oct 27, 2014 at 12:49 AM, Mungeol Heo wrote:
> Hi,
>
> My question is that will es remove all river related plugin in the future?
> If
I see. Thanks for your quick reply.
Have a nice day.
Thanks,
- Mungeol
On Monday, October 27, 2014 12:40:12 PM UTC+9, vineeth mohan wrote:
>
> Hello Mungeol ,
>
> As far as i know , the plan is to depreciate rivers and move them to
> logstash.
>
> Thanks
>Vineeth
>
> On Mon, Oct 27,
Hello Mungeol ,
As far as i know , the plan is to depreciate rivers and move them to
logstash.
Thanks
Vineeth
On Mon, Oct 27, 2014 at 5:19 AM, Mungeol Heo wrote:
> Hi,
>
> My question is that will es remove all river related plugin in the future?
> If it will, I'd like to know that
Hi,
My question is that will es remove all river related plugin in the future?
If it will, I'd like to know that is there any kind of substitution for
JDBC?
Thanks.
Best regards,
- Mungeo
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To u
Hi,
My question is that will es remove all river related plugin in the future?
If it will, I'd like to know that is there substitution for JDBC?
Thanks.
Best regards,
- Mungeol
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe f
