[jira] [Commented] (LUCENE-8342) Can we enforce more properties on fields like uniquness

["Robert Muir (JIRA)" <ji...@apache.org>]

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

Robert Muir commented on LUCENE-8342:
-------------------------------------

+1: it would be a big improvement to validate this in IW, merge, checkindex, etc.

> Can we enforce more properties on fields like uniquness 
> --------------------------------------------------------
>
>                 Key: LUCENE-8342
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8342
>             Project: Lucene - Core
>          Issue Type: New Feature
>    Affects Versions: master (8.0)
>            Reporter: Simon Willnauer
>            Priority: Major
>
> This is a spin-off from LUCENE-8335 where we discuss adding a boolean to FieldInfo to check if the field is used for soft deletes. This has been a a very delicate line we drew in the past but if we take a step back and think about how we'd design a feature like IW#updateDocument(Term, Document) today would we allow passing different fields to this API? It's just one example ie. storing floats and ints in the same DV field is a different one. I personally think it would be a good idea to be more strict on that end and I wonder what others think.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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