You don't give an indication of size. How large are the documents being indexed and how many of them are there. However, my opinion would be a single index with an 'active' flag. In your queries you can use FilterQueries (fq=) to optimize on just active if you wish, or just inactive if that is necessary.
For the RDBMS, do you have any other reason to use a RDBMS besides storing this data inbetween indexes? Do you need to make relational queries that Solr can't handle? If not, then I think a file based approach may be better. Or, as in my case, a small DB for generating/tracking unique_ids and last_update_datetimes, but the bulk of the data is archived in files and can easily be updated or read and indexed. -- View this message in context: http://lucene.472066.n3.nabble.com/Index-partitioned-Full-indexing-by-MSSQL-or-MySQL-tp1515572p1516763.html Sent from the Solr - User mailing list archive at Nabble.com.
