On 4/7/2022 8:41 PM, James Greene wrote:
This is actually why people abandon solr for elastic/opensearch. Solrs core contributors hold little value in supporting migration paths and stability with-in so it's always a heavy cost to users for upgrades.
At a fundamental level, because ES and Solr both use Lucene for the vast majority of their functionality, there are not a lot of differences between what each of them is capable of doing. The main differences are in what each of them does out of the box. Solr is geared towards maximum capability and flexibility, and the sheer number of things that can be configured is overwhelming for a novice. ES focuses more on a "typical user" sort of audience. If you want to really dive into things, they offer some of the same things that Solr does, but those advanced features are not staring you in the face when you take a look at a default config.
As I understand it, ES offers reindex capability by storing the entire input document into a field in the index. Which means that the index will be lot bigger than it needs to be, which is going to affect performance. If the field is not indexed, then the performance impact may not be huge, but it will not be zero. And it wouldn't really improve the speed of a full reindex, it just makes it possible to do a reindex without an external data source.
The same thing can be done with Solr, and it is something I would definitely say needs to be part of any index design where Solr will be a primary data store. That capability should be available in Solr, but I do not think it should be enabled by default.
I would love to explore the possibilities in making it possible to have a much more streamlined config system for Solr. Something that would make it a lot easier for a novice to get started, without making things really difficult for an advanced user to create more complex configurations.
Thanks, Shawn
