I'm planning to use ElasticSearch as a horizontally scalable cache that I
can search data from (because querying data from our RDBMs even with
indexing and pagination is too slow). That is, I will query data from our
RDBMs, (optionally do some processing on those data,) then store it in
ElasticSearch. So that when I do a search, I just search against
ElasticSearch. And when I do an update, I update both RDBMs and
ElasticSearch.
Is my plan on how to use ElasticSearch correct, or I am totally wrong on
ElasticSearch's usage? ..or is there a better tool for that?
Sounds good to me, especially since you get some features out of
elasticsearch that you can't use in the database.
-shay.banon
On Mon, Jun 28, 2010 at 11:52 AM, Franz Allan Valencia See < franz.see@gmail.com> wrote:
Good day,
I'm planning to use Elasticsearch as a horizontally scalable cache that I
can search data from (because querying data from our RDBMs even with
indexing and pagination is too slow). That is, I will query data from our
RDBMs, (optionally do some processing on those data,) then store it in
Elasticsearch. So that when I do a search, I just search against
Elasticsearch. And when I do an update, I update both RDBMs and
Elasticsearch.
Is my plan on how to use Elasticsearch correct, or I am totally wrong on
Elasticsearch's usage? ..or is there a better tool for that?
Follow-up question:
From an RDBMs, to retrieve/search data from multiple table, we use a join.
How about for Elasticsearch? Are these data 'denormalized' to documents or
can Elasticsearch's index + type mimic joining a table?
Sounds good to me, especially since you get some features out of
elasticsearch that you can't use in the database.
-shay.banon
On Mon, Jun 28, 2010 at 11:52 AM, Franz Allan Valencia See < franz.see@gmail.com> wrote:
Good day,
I'm planning to use Elasticsearch as a horizontally scalable cache that I
can search data from (because querying data from our RDBMs even with
indexing and pagination is too slow). That is, I will query data from our
RDBMs, (optionally do some processing on those data,) then store it in
Elasticsearch. So that when I do a search, I just search against
Elasticsearch. And when I do an update, I update both RDBMs and
Elasticsearch.
Is my plan on how to use Elasticsearch correct, or I am totally wrong on
Elasticsearch's usage? ..or is there a better tool for that?
You will have to denormalize you data into self contained/searchable
documents. Though there is some interesting work being done at creating
parent / child doc relationship, but its at a very very early stage.
-shay.banon
On Tue, Jun 29, 2010 at 2:06 AM, Franz Allan Valencia See < franz.see@gmail.com> wrote:
Thanks
Follow-up question:
From an RDBMs, to retrieve/search data from multiple table, we use a join.
How about for Elasticsearch? Are these data 'denormalized' to documents or
can Elasticsearch's index + type mimic joining a table?
Sounds good to me, especially since you get some features out of
elasticsearch that you can't use in the database.
-shay.banon
On Mon, Jun 28, 2010 at 11:52 AM, Franz Allan Valencia See < franz.see@gmail.com> wrote:
Good day,
I'm planning to use Elasticsearch as a horizontally scalable cache that I
can search data from (because querying data from our RDBMs even with
indexing and pagination is too slow). That is, I will query data from our
RDBMs, (optionally do some processing on those data,) then store it in
Elasticsearch. So that when I do a search, I just search against
Elasticsearch. And when I do an update, I update both RDBMs and
Elasticsearch.
Is my plan on how to use Elasticsearch correct, or I am totally wrong on
Elasticsearch's usage? ..or is there a better tool for that?
You will have to denormalize you data into self contained/searchable
documents. Though there is some interesting work being done at creating
parent / child doc relationship, but its at a very very early stage.
-shay.banon
On Tue, Jun 29, 2010 at 2:06 AM, Franz Allan Valencia See < franz.see@gmail.com> wrote:
Thanks
Follow-up question:
From an RDBMs, to retrieve/search data from multiple table, we use a join.
How about for Elasticsearch? Are these data 'denormalized' to documents or
can Elasticsearch's index + type mimic joining a table?
Sounds good to me, especially since you get some features out of
elasticsearch that you can't use in the database.
-shay.banon
On Mon, Jun 28, 2010 at 11:52 AM, Franz Allan Valencia See < franz.see@gmail.com> wrote:
Good day,
I'm planning to use Elasticsearch as a horizontally scalable cache that
I can search data from (because querying data from our RDBMs even with
indexing and pagination is too slow). That is, I will query data from our
RDBMs, (optionally do some processing on those data,) then store it in
Elasticsearch. So that when I do a search, I just search against
Elasticsearch. And when I do an update, I update both RDBMs and
Elasticsearch.
Is my plan on how to use Elasticsearch correct, or I am totally wrong on
Elasticsearch's usage? ..or is there a better tool for that?
You will have to denormalize you data into self contained/searchable
documents. Though there is some interesting work being done at creating
parent / child doc relationship, but its at a very very early stage.
-shay.banon
On Tue, Jun 29, 2010 at 2:06 AM, Franz Allan Valencia See < franz.see@gmail.com> wrote:
Thanks
Follow-up question:
From an RDBMs, to retrieve/search data from multiple table, we use a join.
How about for Elasticsearch? Are these data 'denormalized' to documents or
can Elasticsearch's index + type mimic joining a table?
Sounds good to me, especially since you get some features out of
elasticsearch that you can't use in the database.
-shay.banon
On Mon, Jun 28, 2010 at 11:52 AM, Franz Allan Valencia See < franz.see@gmail.com> wrote:
Good day,
I'm planning to use Elasticsearch as a horizontally scalable cache that
I can search data from (because querying data from our RDBMs even with
indexing and pagination is too slow). That is, I will query data from our
RDBMs, (optionally do some processing on those data,) then store it in
Elasticsearch. So that when I do a search, I just search against
Elasticsearch. And when I do an update, I update both RDBMs and
Elasticsearch.
Is my plan on how to use Elasticsearch correct, or I am totally wrong on
Elasticsearch's usage? ..or is there a better tool for that?
Same answer I gave in the issue, there is some work in Lucene to support
this, but its far from something that can be used properly. I am not
tackling it on elasticsearch level (with or without native Lucene support)
anytime soon.
You will have to denormalize you data into self contained/searchable
documents. Though there is some interesting work being done at creating
parent / child doc relationship, but its at a very very early stage.
-shay.banon
On Tue, Jun 29, 2010 at 2:06 AM, Franz Allan Valencia See < franz.see@gmail.com> wrote:
Thanks
Follow-up question:
From an RDBMs, to retrieve/search data from multiple table, we use a
join. How about for Elasticsearch? Are these data 'denormalized' to
documents or can Elasticsearch's index + type mimic joining a table?
Sounds good to me, especially since you get some features out of
elasticsearch that you can't use in the database.
-shay.banon
On Mon, Jun 28, 2010 at 11:52 AM, Franz Allan Valencia See < franz.see@gmail.com> wrote:
Good day,
I'm planning to use Elasticsearch as a horizontally scalable cache that
I can search data from (because querying data from our RDBMs even with
indexing and pagination is too slow). That is, I will query data from our
RDBMs, (optionally do some processing on those data,) then store it in
Elasticsearch. So that when I do a search, I just search against
Elasticsearch. And when I do an update, I update both RDBMs and
Elasticsearch.
Is my plan on how to use Elasticsearch correct, or I am totally wrong
on Elasticsearch's usage? ..or is there a better tool for that?
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.
