Hey everyone,
I'm trying to figure out the best way to implement Elasticsearch in our
company.
We currently have a SQL Server that houses all of our data and want to get
some better search and analytics functionality so ES seems like an awesome
option.
I've explored using the JDBC river to index data and I've successfully set
up elasticsearch with some test data.
There are some things I'm not clear on:
1. The status of rivers in Elasticsearch. Another thread suggested that
they were convenience feature added at the beginning to get data out of
CouchDB and into ES easily. Are they going to be deprecated soon? It was
suggested by on of the ES developers that companies should be coming up
with their own solutions for indexing data.
1. On that note, what does a custom indexing solution look like in a
scenario like mine? Does this mean leveraging the provided APIs to create
a
custom solution that polls the SQL server for changes?
2. Should I be modifying our middle tier to also queue up update
requests as a user modifies data?
3. I've read RabbitMQ can be used for queuing up bulk requests, but
isn't this just done via another river and therefore has the same
concerns
as above?
2. Does using the JDBC river scale well as the size of your data grows?
I might have this wrong, but rivers don't allow you to take advantage of
the distributed nature of ES?
3. The syntax on the JDBC river for creating nested documents in the ES
index. For example I have an PrimaryAddress table and an AddressAlias table
which contains alternate addresses/names for a single PrimaryAddress. Can
this be modeled in an ES index? The number of AddressAliases isn't the same
for each PrimaryAddress
Thanks!
--
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/cbadcb61-a0c0-4907-9182-5075566b8a7d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
