Re:Ask HN: Are Lucene/Solr/ES Still Used for Search?
by ps101 on Friday July 19, 2019 @02:58PM
(#20481511)
Can you elaborate on the reasons for this?
[ Parent
| on HN ]
Re:Ask HN: Are Lucene/Solr/ES Still Used for Search?
by Izkata on Friday July 19, 2019 @05:50PM
(#20482738)
Coming from experience with Solr, the answer is far simpler than the link in the sibling comment indicates: Data is processed and manipulated on import, and it's difficult - sometimes impossible, depending on the field config - to get that data back out in the format it was imported.
Any changes to the schema, such as switching fields between indexed/not indexed/stored/not stored, requires reimporting the data to populate those fields, data which you're not likely to have if it was your primary store.
Re:Ask HN: Are Lucene/Solr/ES Still Used for Search?
by manigandham on Saturday July 20, 2019 @01:15AM
(#20484304)
Elasticsearch has a _source field [1] that stores the entire original document and is enabled by default. It's required to support features like highlighting in results. ES also has a reindex API that specifically makes use of this [2].
1. https://www.elastic.co/guide/en/elasticsearch/reference/curr...
2. https://www.elastic.co/guide/en/elasticsearch/reference/curr...
Re:Ask HN: Are Lucene/Solr/ES Still Used for Search?
by lemcoe9 on Friday July 19, 2019 @03:40PM
(#20481802)
Here is a very good Quora answer on why you should never use ES as a central repository for data: https://www.quora.com/Why-shouldnt-I-use-ElasticSearch-as-my...