Agreed. We get messages on this list pretty regularly about data locked in old versions of solr with no good way out.
Even if reindexing takes a week on a big cluster and is hard to do, and means un-glaciering stuff from s3, etc make sure you can do it! > On Apr 4, 2022, at 7:57 AM, Dave <hastings.recurs...@gmail.com> wrote: > > NO. I know it’s tempting but solr is a search engine not a database. You > should at any point be able to destroy the search index and rebuild it from > the database. Most any rdbms can do what you want, or go the nosql mongo > route which is becoming popular, but never use a search engine in this way, > you could use it as an intermediate data store for queries and speed but it’s > not the purpose. > >> On Apr 4, 2022, at 7:53 AM, Srijan <shree...@gmail.com> wrote: >> >> Hi All, >> >> I am working on designing a Solr based enterprise search solution. One >> requirement I have is to track crawled data from various different data >> sources with metadata like crawled date, indexing status and so on. I am >> looking into using Solr itself as my data store and not adding a separate >> database to my stack. Has anyone used Solr as a dedicated data store? How >> did it compare to an RDBMS? I see Lucidworks Fusion has a notion of Crawl >> DB - can someone here share some insight into how Fusion is using this >> 'DB'? My store will need to track millions of objects and be able to handle >> parallel adds/updates. Do you think Solr is a good tool for this or am I >> better off depending on a database service? >> >> Thanks a bunch.
