with an
update processor that removes the temporary field (and possibly other
unwanted fields) seemed to work great for us.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Version-conflict-during-data-import-from-another-Solr-instance-into-clean-Solr-tp4046937p4331876.html
Sent from
: It looks strange to me that if there is no document yet (foundVersion 0)
: then the only case when document will be imported is when input version is
: negative. Guess I need to test specific cases using SolrJ or smth. to be sure.
you're assuming that if foundVersion 0 that means no document
Hi,
I've configured data import handler:
requestHandler name=/dataimport
class=org.apache.solr.handler.dataimport.DataImportHandler
lst name=defaults
str name=configdata-config.xml/str
/lst
/requestHandler
data-config.xml:
dataConfig
document
entity name=sep
I believe you are running into the update semantics, new with Solr 4
(4.1?): https://wiki.apache.org/solr/Per%20Steffensen/Update%20semantics I
am not sure Wiki is 100% correct (especially on default mode), but it
should be good enough.
Basically, because you are specifying some real value in
Hello, thank you for response!
Configuration option semanticsMode does not help - it's probably not
yet implemented. I found however the line of code which checks versions:
Long lastVersion = vinfo.lookupVersion(cmd.getIndexedId());
long foundVersion = lastVersion == null ? -1 : lastVersion;
What about update request processors to drop the field?
Regards,
Alex
On Mar 13, 2013 9:45 AM, Artem OXSEED a.karpe...@oxseed.com wrote:
Hello, thank you for response!
Configuration option semanticsMode does not help - it's probably not yet
implemented. I found however the line of code
