lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregg Donovan (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2701) Expose IndexWriter.commit(Map<String,String> commitUserData) to solr
Date Wed, 28 Dec 2011 03:05:32 GMT


Gregg Donovan commented on SOLR-2701:

We (Etsy) are interested in this issue for the same use-case that Eks Dev mentions -- passing
around timestamps and other meta-data for use by incremental indexers. We currently write
out and replicate custom property files for this -- using commitUserData would be preferable.

It seems like another use-case the commitUserData could be useful for is doing an empty commit
that actually triggered replication, as the updated commitUserData will cause the segments
file to be updated.

For our purposes, we'd just be using CommitUpdateCommand and DUH2 as our interfaces for writing
the commitUserData, but exposing commitUserData to the SolrJ/HTTP interfaces does seem like
a nice feature. I wonder where it would be useful to expose reading the commitUserData via
SolrJ/HTTP as right now you still need low-level code to extract the commitUserData from an
IndexReader. Perhaps stats.jsp could expose each key in the commitUserData as a stat?
> Expose IndexWriter.commit(Map<String,String> commitUserData) to solr 
> ---------------------------------------------------------------------
>                 Key: SOLR-2701
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: update
>    Affects Versions: 4.0
>            Reporter: Eks Dev
>            Assignee: Erick Erickson
>            Priority: Minor
>              Labels: commit, update
>         Attachments: SOLR-2701.patch
>   Original Estimate: 8h
>  Remaining Estimate: 8h
> At the moment, there is no feature that enables associating user information to the commit
> Lucene supports this possibility and it should be exposed to solr as well, probably via
beforeCommit Listener (analogous to prepareCommit in Lucene).
> Most likely home for this Map to live is UpdateHandler.
> Example use case would be an atomic tracking of sequence numbers or timestamps for incremental

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