[
https://issues.apache.org/jira/browse/SOLR-10829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039784#comment-16039784
]
Hoss Man commented on SOLR-10829:
---------------------------------
Discovered this while working on SOLR-10807.
Note that the same sort of error checking should be applied to the {{\_root_}}
field if defined, but SOLR-10830 is probably a broader fix for that specific
issue: if we assert that {{\_root_}} uses the same type as the uniqueKeyField,
then we don't need to worry about checking that {{\_root_}} doesn't use points
as long as we've already checked that the uniqueKey field doesn't use points
> 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]
