lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Khludnev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-10829) IndexSchema should enforce that uniqueKey field must not be points based
Date Fri, 09 Jun 2017 07:35:18 GMT

    [ https://issues.apache.org/jira/browse/SOLR-10829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044088#comment-16044088
] 

Mikhail Khludnev commented on SOLR-10829:
-----------------------------------------

LGTM

> 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
>         Attachments: SOLR-10829.patch
>
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message