lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eks Dev (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3760) Cleanup DR.getCurrentVersion/DR.getUserData/DR.getIndexCommit().getUserData()
Date Thu, 09 Feb 2012 16:48:03 GMT


Eks Dev commented on LUCENE-3760:

I have a use case for CommitUserData and I think standard solr DIH could benefit from it as
I use it to persist current status of the max Document id (user id, not lucene docid) to know
what I have indexed so far (all update commands are stored in the database and have simple
incrementing counter). This makes incremental update process "restart- and rollback- safe"
as it gets written on lucene commit and read on startup. I do not index this field (not to
pollute term dictionary) and I need only to keep max value of it. 

I find it hugely useful, but if you have better ideas on how to safely persist max/min value
of the field I am all ears. 

Last time I checked, solr DIH used its own file in cfg directory to persist max(timestamp),
which is kind of risky as it is not in sync with lucene commit point under all scenarios.

I think I even opened an isue on solr jira to expose "user commit data"  feature to solr,
but I am missing good ideas on how to expose it to solr users (max/min/avg field tracking

Cheers, eks
> Cleanup DR.getCurrentVersion/DR.getUserData/DR.getIndexCommit().getUserData()
> -----------------------------------------------------------------------------
>                 Key: LUCENE-3760
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 3.6, 4.0
>         Attachments: LUCENE-3760.patch, LUCENE-3760.patch
> Spinoff from Ryan's dev thread "DR.getCommitUserData() vs DR.getIndexCommit().getUserData()"...
these methods are confusing/dups right now.

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