Well, a very common pattern is to use Solr to search, storing just enough in each field (stored="true") to return to the user search results that give enough information to determine whether they want to look at the original document. When the click on a choice (or a link like "download PDF") then fetch the actual file from the system of record.
You'll have to re-index sometime anyway as your requirements change and you have to re-ingest all your data and that's easiest from the system of record. Best, Erick Erickson On Mon, Aug 7, 2017 at 8:05 PM, sg1973 <srigollam...@gmail.com> wrote: > I have written the code to publish to Solr but i am wondering what is the > right way to do it. Is directly putting data in Solr OK or putting it in a > separate cache and then building solr on top of it? what are the pros and > cons of each? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Storing-data-in-Solr-tp4349537p4349541.html > Sent from the Solr - User mailing list archive at Nabble.com.
