ogether 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
: 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 documen
What about update request processors to drop the field?
Regards,
Alex
On Mar 13, 2013 9:45 AM, "Artem OXSEED" wrote:
> Hello, thank you for response!
>
> Configuration option does not help - it's probably not yet
> implemented. I found however the line of code which checks versions:
>
> Lo
Hello, thank you for response!
Configuration option 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;
if ( versionOn
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 _ver
Hi,
I've configured data import handler:
class="org.apache.solr.handler.dataimport.DataImportHandler">
data-config.xml
data-config.xml:
http://host:8080/index"; query="*:*" wt="javabin"/>
Both Solr instances are of the same version - 4.1. Target Solr instance
