Hi,
I am a newbie to elasticsearch. I am planning to use elasticsearch for just
search and leave oracle DB to hold the canonical data.
Requirement : To provide search functionality on the 'application forms'
submitted to our system. Our 'application forms' can have many 'items'
associated with it (one to many).
We have to provide 2 searches, one that fetches 'application form' level
data and the other fetches 'item' level data. Both will have similar search
criteria.
Options 1:
I can create 2 indices with different json document structure. First index
will have the 'application form' as the parent and all 'items' as its child
(similar to its canonical structure), Second index will reverse the
hierarchy and have 'item' as the parent and all the 'application form'
attributes associated to it.
*Cons: *
Data is duplicated in 2 indices.
Option 2:
Create one index similar to canonical structure and support both the search
requirement.
*Cons : *
I have to write code to process and massage the data for returning the
results at 'item' level.
Question:
Which option is preferable and why.
Is there a better solution to handle this scenario.
If I opt for option 1 - do I need to create 2 JDBC river component to
update data in both the elasticsearch indices.
or
should I write one JDBC river component and update both the indices.
Regarding the JDBC river, it depends how many data sources you have. If you
have one for form fields and one for form values, you should use two
instances. If you can use a single SQL select for both form fields and
values, one river instance should be sufficient.
Beside, you do not need parent/child or two indices if one index with two
mappings should work where you can follow reference IDs to get additional
attributes.
Hi,
I am a newbie to elasticsearch. I am planning to use elasticsearch for
just search and leave oracle DB to hold the canonical data.
Requirement : To provide search functionality on the 'application
forms' submitted to our system. Our 'application forms' can have many
'items' associated with it (one to many).
We have to provide 2 searches, one that fetches 'application form' level
data and the other fetches 'item' level data. Both will have similar search
criteria.
Options 1:
I can create 2 indices with different json document structure. First index
will have the 'application form' as the parent and all 'items' as its child
(similar to its canonical structure), Second index will reverse the
hierarchy and have 'item' as the parent and all the 'application form'
attributes associated to it.
*Cons: *
Data is duplicated in 2 indices.
Option 2:
Create one index similar to canonical structure and support both the
search requirement.
*Cons : *
I have to write code to process and massage the data for returning the
results at 'item' level.
Question:
Which option is preferable and why.
Is there a better solution to handle this scenario.
If I opt for option 1 - do I need to create 2 JDBC river component to
update data in both the elasticsearch indices.
or
should I write one JDBC river component and update both the indices.
Thanks Jorg,
I will try this out and get back.
meanwhile if you have a sample to create the mapping at the 'item' level,
please share it.
Thanks,
Ranjith
On Monday, July 14, 2014 3:05:32 AM UTC-4, Jörg Prante wrote:
Regarding the JDBC river, it depends how many data sources you have. If
you have one for form fields and one for form values, you should use two
instances. If you can use a single SQL select for both form fields and
values, one river instance should be sufficient.
Beside, you do not need parent/child or two indices if one index with two
mappings should work where you can follow reference IDs to get additional
attributes.
Jörg
On Mon, Jul 14, 2014 at 2:03 AM, Ranjith Sundaraj Chandra < scranji...@gmail.com <javascript:>> wrote:
Hi,
I am a newbie to elasticsearch. I am planning to use elasticsearch for
just search and leave oracle DB to hold the canonical data.
Requirement : To provide search functionality on the 'application
forms' submitted to our system. Our 'application forms' can have many
'items' associated with it (one to many).
We have to provide 2 searches, one that fetches 'application form' level
data and the other fetches 'item' level data. Both will have similar search
criteria.
Options 1:
I can create 2 indices with different json document structure. First
index will have the 'application form' as the parent and all 'items' as its
child (similar to its canonical structure), Second index will reverse the
hierarchy and have 'item' as the parent and all the 'application form'
attributes associated to it.
*Cons: *
Data is duplicated in 2 indices.
Option 2:
Create one index similar to canonical structure and support both the
search requirement.
*Cons : *
I have to write code to process and massage the data for returning the
results at 'item' level.
Question:
Which option is preferable and why.
Is there a better solution to handle this scenario.
If I opt for option 1 - do I need to create 2 JDBC river component to
update data in both the elasticsearch indices.
or
should I write one JDBC river component and update both the indices.
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.