When I am putting PDF documents and rows from a table into the same index, I
create "dataSource" field to identify the source and I don't copy database
fields - only index them - apart from the unique key which is stored as
"document". On search, you process the output before passing to user. If
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
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.n
Solr indexes data for search and if search is the main criterion Solr should be
used.
On Mon, 8/7/17, sg1973 wrote:
Subject: Storing data in Solr
To: solr-user@lucene.apache.org
Received: Monday, August 7, 2017, 6:55 PM
Hello All,
I am new to
Which database is to be integrated? Solr provides Data Import Handlers for
several databases including Oracle and MySQL.
On Mon, 8/7/17, sg1973 wrote:
Subject: Storing data in Solr
To: solr-user@lucene.apache.org
Received: Monday, August 7, 2017,
