[ https://issues.apache.org/jira/browse/SOLR-10829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044835#comment-16044835 ]
ASF subversion and git services commented on SOLR-10829: -------------------------------------------------------- Commit 477eeea1ede3eac12328a57642f88cb6ea8994b8 in lucene-solr's branch refs/heads/branch_6x from Chris Hostetter [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=477eeea ] SOLR-10829: Fixed IndexSchema to enforce that uniqueKey can not be Points based for correctness (cherry picked from commit 8cd826f2936853d345c863e51c50eeaa9754a061) > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org