lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrien Grand (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7659) IndexWriter should expose field names
Date Wed, 25 Jan 2017 15:00:35 GMT


Adrien Grand commented on LUCENE-7659:

It should not be necessary to know the list of the current field names. If I understand the
Solr issue correctly, your use-case is to check whether an update can be applied using dv-updates
only, or whether it requires an regular update. Do I get it right? If I do then maybe a better
way to address this use-case would be to either try the dv-only update and fallback to a regular
update if it failed (which should be fine since dv updates are atomic), or change the semantics
of dv updates to create fields if they did not exist already (then the only thing the Solr
code should check is whether any of the fields is already used for index sorting)? Note that
I am not very familiar with {{IndexWriter}}, hopefully others can comment about whether that
makes any sense.

> IndexWriter should expose field names
> -------------------------------------
>                 Key: LUCENE-7659
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Ishan Chattopadhyaya
>         Attachments: 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

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

View raw message