You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We know that storing metadata within solr makes the search slower. We could add a second embedded database to do the metadata look-up using solr's search results. Would it make sense to have a second index for the metadata using solr rather than introducing a second database technology?
For the server-based solution, maybe a second server would be appropriate.
The text was updated successfully, but these errors were encountered:
Yes, that's a viable solution if metadata make the index very big. The experience I had for very big indexes, i.e 500G indexes that won't fit a single host, one can use a secondary document storage database for document retrieval to speed things up. Alternatively (especially since solr 4.10), we could further tune the SOLR_HOME, sharding, caching etc to store the metadata in the same Solr instance. Chances are less dependencies if that scales well.
We know that storing metadata within solr makes the search slower. We could add a second embedded database to do the metadata look-up using solr's search results. Would it make sense to have a second index for the metadata using solr rather than introducing a second database technology?
For the server-based solution, maybe a second server would be appropriate.
The text was updated successfully, but these errors were encountered: