Can you please let me know which is the best way to index the records in elastic search for my scenario.
My Scenario is :
Need to index around 40 million records from oracle table which has entries having one to many relationship records. And the uniqueness of the records is based on the composite key with 4 columns
After indexing , Search should support "full text search" on all the fields
Filters and sorting on selected fields needs to be supported.
After going through the official documentation i found couple of options , but want to know which approach would be most useful among below
For each record in table create a entry in the elastic index
Create a nested json object based on the composite key and then add this elastic index
Parent child Relationship mechanism and application side joins are not suitable for my scenario
Think about the use case, not the current implementation.
Basically ask yourself: "What type of data my user will be searching for?".
As an example, let's say that users want to search for employees. Then index employees.
2nd question is "What kind of attributes do my users will use to search?". Let's say "company name", "company website" and "employee name". Then just store those values within each document, like:
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.