[
https://issues.apache.org/jira/browse/LUCENE-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838804#comment-15838804
]
Michael McCandless commented on LUCENE-7659:
--------------------------------------------
OK I see, tricky. I think it's OK to add this (experimental) method to IW, and
I agree it would be cleaner if IW could just bring a new DV field into
existence on update.
Such a thing used to be terrifying, because you were in fact bringing an entire
column into existence, but in 7.0 we've fixed sparse doc values to be written
sparsely.
The patch wraps in {{Collections.unmodifiableSet}} twice now ... maybe remove
the one in IW and add a comment saying {{FieldInfos}} already did so?
> IndexWriter should expose field names
> -------------------------------------
>
> Key: LUCENE-7659
> URL: https://issues.apache.org/jira/browse/LUCENE-7659
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Attachments: LUCENE-7659.patch, LUCENE-7659.patch, LUCENE-7659.patch
>
>
> While working on SOLR-5944, I needed a way to know whether applying an update
> to a DV is possible (i.e. the DV exists or not), while deciding upon whether
> or not to apply the update as an in-place update or a regular full document
> update. This information is present at the IndexWriter in a FieldInfos
> instance, and can be exposed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
