lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4258) Incremental Field Updates through Stacked Segments
Date Mon, 30 Jul 2012 14:03:35 GMT


Robert Muir commented on LUCENE-4258:

I don't see how UPDATE_FIELDS can do so unless we somehow save the raw
stats (FieldInvertState) in the index. It seems like UPDATE_FIELDS
should forever be limited to DOCS_ONLY, no norms updating?

Actually its DOCS_ONLY plus OMIT_NORMS.

Anyway why not start with updating the entire contents of a field as I suggested?
It seems to be the most general solution, and there is some discussion about how scoring can
work correctly on LUCENE-3837 (the stats, not just norms).

I do think this is a common use case (ACLs, filters, social
tags)... though I'm not sure how bad it'd really be in practice for
the app to simply REPLACE_FIELDS with the full set of tags. I guess
if we build REPLACE_FIELDS first we can test that.

This is why we should do 'replace contents of a field' first. Its the most well-defined and

Its also still controversial, myself I'm not convinced it will actually help most people that
they want it, I think it will just slow down searches.

> Incremental Field Updates through Stacked Segments
> --------------------------------------------------
>                 Key: LUCENE-4258
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/index
>            Reporter: Sivan Yogev
>   Original Estimate: 2,520h
>  Remaining Estimate: 2,520h
> Shai and I would like to start working on the proposal to Incremental Field Updates outlined
here (

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message