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

David Smiley commented on LUCENE-4258:
--------------------------------------

Its exciting to see progress here!  I too live in the "world" that Shai speaks 
of -- DOCS_ONLY (w/ no norms).  I don't need to update a title field, I need to 
update ACLs and various categorical "tag" fields that will subsequently 
influence faceting or filtering.

Hey Rob, early on you made this excellent point:
{quote}A second problem (not solved by the above) is that many people are using 
scoring factors with a variety
of signals and these are changing often. I think unfortunately, people are 
often putting these in
a normal indexed field and uninverting these on the fieldcache, requiring the 
whole document to
be reindexed just because of how they implemented the scoring factor. People 
could instead solve this
by putting their apps primary key into a docvalues field, allowing them to keep 
these scoring factors
completely external to lucene (e.g. their own array or whatever), indexed by 
their own primary key. But
the problem is I think people want lucene to manage this, they don't want to 
implement themselves whats
necessary to make it consistent with commits etc.{quote}

So true.  What if Lucene had more hooks to make it easier to manage 
commit-consistency with side-car data?  I have no clue what's needed exactly, 
only that I don't dare do this without such hooks because I fear the 
complexity.  With hooks and documentation, it can become clear how to maintain 
data alongside Lucene's index, and this opens doors.  Like making it easier to 
store data in something custom (e.g. a DB) instead of stored-fields (won't have 
to pay needless merge cost), or putting metrics that influence scoring 
somewhere as you hinted at above. 
                
> Incremental Field Updates through Stacked Segments
> --------------------------------------------------
>
>                 Key: LUCENE-4258
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4258
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/index
>            Reporter: Sivan Yogev
>         Attachments: IncrementalFieldUpdates.odp, 
> LUCENE-4258-API-changes.patch, LUCENE-4258.r1410593.patch, 
> LUCENE-4258.r1412262.patch, LUCENE-4258.r1416438.patch, 
> LUCENE-4258.r1416617.patch, LUCENE-4258.r1422495.patch, 
> LUCENE-4258.r1423010.patch
>
>   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 (http://markmail.org/message/zhrdxxpfk6qvdaex).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Reply via email to