i agree with David suggestions,

here is link to topic that is also touching river deprecation (with 
suggested replacement(s)):
https://groups.google.com/d/msg/elasticsearch/-nZQheK0J-g/1xhVm9Y5_dgJ


BTW, if you really feel like river is the best solution for you, then you 
should go for it
even if elasticsearch team will deprecate rivers from the core 
implementation, there will be some community contributed solution to 
replace it 
i think the amount of elasticsearch applications using rivers is too big to 
get rid of them completely 


On Saturday, January 11, 2014 3:12:53 AM UTC, jsp wrote:
>
> Thanks Karl,
> Do you have any recommendation for alternatives to using rivers.  i want 
> to read data from sql db/tables.
> thanks
> jay
>
> On Friday, 10 January 2014 13:55:29 UTC-8, Karol Gwaj wrote:
>>
>> Consider the fact that rivers could be deprecated in future versions of 
>> elasticsearch:
>>
>> http://www.linkedin.com/groups/Official-guide-writing-ElasticSearch-rivers-3393294.S.268274223
>>
>>
>>
>> On Wednesday, January 8, 2014 4:26:58 PM UTC, jsp wrote:
>>>
>>> Hi,
>>> I am looking at implementing ES to index & query data that I get from my 
>>> SQL Server databases/tables.  I was initially using river to read data from 
>>> Sql server tables but one of the developers in my team recommended looking 
>>> at using logstash. Can anyone comment to any benefits of using one over 
>>> another?   I have not been able to find any documentation regarding reading 
>>> data from SQL server using logstash <http://logstash.net/docs/1.3.2/>. 
>>>  Can someone point me to a guide on how to get started with logstash & sql 
>>> server.  
>>> Thanks
>>> J
>>>
>>

-- 
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/f613f7f0-4c69-4e9f-bd2f-9b2c1a3c5f0e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to