[
https://issues.apache.org/jira/browse/SOLR-10829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041200#comment-16041200
]
Hoss Man commented on SOLR-10829:
---------------------------------
bq. Do you think it's worth creating a specific IDField class for this?
i don't have strong opinions about that -- but if we do that it should be in
it's own "Improvement" jira because it can only be targeted for 7.x and above.
I want to keep this jira focused on being a "Bug" because right now if you try
to use an IntPointField as your uniqueKey in 6.x you'll silently get incorrect
behavior when doing deletes/updates so we need an error that we can backport to
6.x bug fix releases.
> IndexSchema should enforce that uniqueKey field must not be points based
> ------------------------------------------------------------------------
>
> Key: SOLR-10829
> URL: https://issues.apache.org/jira/browse/SOLR-10829
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
>
> if a uniqueKey field is defined, then the IndexSchema should fail fast & hard
> on startup if the field type of the specific uniqueKey uses "points" (ie:
> {{FieldType.isPointField()}})
> The reason for this is because deleting by id, and overwriting existing
> documents are predicated on being able to use
> {{IndexWriter.deleteDocuments(Term...)}} and
> {{IndexWriter.updateDocument(Term, Iterable<..docs..>)}} respectively -- but
> Points based fields have no "Term" that can be based to these methods.
> IndexSchema.readSchema should fail fast in this case with a clear error (just
> like it does if the uniqueKey field is multivalued)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
