lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SOLR-2796) AddUpdateCommand.getIndexedId doesn't work with schema configured defaults/copyField - UUIDField/copyField can not be used as uniqueKey field
Date Fri, 01 Jun 2012 22:26:23 GMT

     [ https://issues.apache.org/jira/browse/SOLR-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hoss Man resolved SOLR-2796.
----------------------------

    Resolution: Fixed
      Assignee: Hoss Man

Committed revision 1345376. - trunk
Committed revision 1345378. - 4x

Committed checking for these situations in IndexSchema along with explicit error messages.
  Commit also includes a CHANGES.txt upgrading not about using UUIDUpdateProcessorFactory
to have uniqueKey values generated automatically, note will need to be updated once copy-field-esque
update processor is available (tracked in SOLR-2599)
                
> AddUpdateCommand.getIndexedId doesn't work with schema configured defaults/copyField
- UUIDField/copyField can not be used as uniqueKey field
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-2796
>                 URL: https://issues.apache.org/jira/browse/SOLR-2796
>             Project: Solr
>          Issue Type: Bug
>          Components: update
>    Affects Versions: 4.0
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>            Priority: Blocker
>             Fix For: 4.0
>
>         Attachments: SOLR-2796.patch
>
>
> in Solr 1.4, and the HEAD of the 3x branch, the UUIDField can be used as the uniqueKey
field even if documents do not specify a value by taking advantage of the {{default="NEW"}}
feature of UUIDField.
> Similarly, a copyField can be used to populate the uniqueKey field with data from some
field with another name -- multiple copyFields can even be used if there is no overlap (ie:
if you have two differnet types of documents with no overlap in their id space, you can copy
from companyId->id and from productId->id and use "id" as your uniqueKey field in solr)
> Neither of these approaches work in Solr trunk because of how {{AddUpdateCommand.getIndexedId}}
is currently used by the DirectUpdateHander2 (see [r1152500|http://svn.apache.org/viewvc?view=revision&revision=1152500]).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message