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
maybe you should ask your developers, why they recommended logstash for
this, I cant follow here (perhaps there is some export functionality in
your SQL server, which an input of logstash can use?). Would be interested
in reasons in this case.
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
Currently logstash provides an api to get data through sqlite. And have
been looking at how it is being used for sqlite and will try to replicate
that for Sql Server.
Will post code if I get it working.
Thanks
--J
On Thursday, 9 January 2014 00:23:36 UTC-8, Alexander Reelsen wrote:
Hey,
maybe you should ask your developers, why they recommended logstash for
this, I cant follow here (perhaps there is some export functionality in
your SQL server, which an input of logstash can use?). Would be interested
in reasons in this case.
--Alex
On Wed, Jan 8, 2014 at 5:26 PM, jsp <jayasu...@gmail.com <javascript:>>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
Consider the fact that rivers could be deprecated in future versions of
elasticsearch:
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
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
modify application which create those data and push to Elasticsearch from it
I prefer the latter as your search engine will be well synchronized with your database.
Also, it will be a gain, database performance wise, as you don't need to read again your DB to inject into ES.
My 2 cents
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
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: Sign Up | LinkedIn
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. Can someone point me to a guide on how to get started with logstash & sql server.
Thanks
J
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:
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
I just started a gathering framework plugin for fetching and indexing data
to Elasticsearch, with scalable components. It's not complete yet of
course. Next, I intend to create an alternative to the JDBC river, and if
that works out well, for other kinds of rivers too
I agree with the third option, if you can. But you should publish to a
queue and then that goes to ES. That way you can use a 2 phase commit to
the DB and to the queue.
Even with option 1 and 2 ... use a queue. Talend has built in stuff to do
this because it is more than just ETL (it is an ESB where ETL is just a
use case)
On Saturday, January 11, 2014 1:47:40 AM UTC-5, David Pilato wrote:
IMHO, some options:
ETL tool like Talend
a batch process you need to write
modify application which create those data and push to Elasticsearch
from it
I prefer the latter as your search engine will be well synchronized with
your database.
Also, it will be a gain, database performance wise, as you don't need to
read again your DB to inject into ES.
My 2 cents
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
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
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.