Interesting.
In your scenario would you use commit=true, or commit=false, and do you use
auto soft/hard commits?
Secondly, if you did use auto-soft/hard commits, how would they affect this
scenario? I'm guessing even with commit=false, the autoCommits would be
triggered either by time or max docs, which opens a searcher anyways. A total
guess though.
I'm interested in doing full-imports without committing/opening new searchers
until it is complete.
Cheers!
Tim
On 20/05/13 03:59 PM, shreejay wrote:
geeky2 wrote
you mean i would add this switch to my script that kicks of the
dataimport?
exmaple:
OUTPUT=$(curl -v
http://${SERVER}.intra.searshc.com:${PORT}/solrpartscat/${CORE}/dataimport
-F command=full-import -F clean=${CLEAN} -F commit=${COMMIT} -F
optimize=${OPTIMIZE} -F openSearcher=false)
Yes. Thats correct
geeky2 wrote
what needs to be done _AFTER_ the DIH finishes (if anything)?
eg, does this need to be turned back on after the DIH has finished?
Yes. You need to open the searcher to be able to search. Just run another
commit with openSearcher = true , once your indexing process finishes.
--
View this message in context:
http://lucene.472066.n3.nabble.com/seeing-lots-of-autowarming-messages-in-log-during-DIH-indexing-tp4064649p4064768.html
Sent from the Solr - User mailing list archive at Nabble.com.
