lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrien Grand (JIRA)" <>
Subject [jira] [Reopened] (LUCENE-8342) Can we enforce more properties on fields like uniquness
Date Wed, 05 Sep 2018 17:09:00 GMT


Adrien Grand reopened LUCENE-8342:

Reopen: was closed by mistake.

> Can we enforce more properties on fields like uniquness 
> --------------------------------------------------------
>                 Key: LUCENE-8342
>                 URL:
>             Project: Lucene - Core
>          Issue Type: New Feature
>    Affects Versions: master (8.0)
>            Reporter: Simon Willnauer
>            Priority: Major
>             Fix For: 7.5, master (8.0)
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message