3 ms·
you can, but almost nobody will recommend to use it, neither will do with elasticsearch. In most cases it works, but it has priorized speed over resilience, so
by joking 6y ago
you can, but almost nobody will recommend to use it, neither will do with elasticsearch. In most cases it works, but it has priorized speed over resilience, so it's better to have a source from where you can rebuild the index.
- cmckn 6y ago> it's better to have a source from where you can rebuild the index. Having worked for several years at a company selling search, I can't emphasize this enough. Rebuilding indices should always be straightforward, and your data should be very accessible in some other (preliminary) form. We ran into so many issues, and had so many panics, because the index had become the only place some things existed. It's also way easier to tweak (read: optimize) your schema over time when you're in the habit of rebuilding the index.
- eivarv 6y agoAnother "but" here is what [0] may happen if you're storing personal data in big indexes... TLDR; In some cases, what data you actually have (as in "on disk") becomes complicated. For instance, in some cases, once a segment reaches max size (5GB by default) it will only be eligible for merging when it accumulates 50% deletions. This means you might not be able to guarantee deletion of data within 30 days (in accordance with the GDPR). [0]: https://www.eivindarvesen.com/blog/2018/09/23/lucene-indexes-and-gdpr https://www.eivindarvesen.com/blog/2018/09/23/lucene-indexes...