[
https://issues.apache.org/jira/browse/SOLR-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bowyer updated SOLR-2701:
------------------------------
Attachment: SOLR-2701-Expose-userCommitData-throughout-solr.patch
I gave this another attempt today, and went full bore on trying to find all the
locations of where userCommitData would need to be exposed to clients of the
SOLR API.
There are a few questions in my mind about this:
* The backwards compat for javabin is not obvious, do we want to change up the
version on javabin
* What should be the exacting behavior around soft and autocommits
* Should previous index commits carry forward in solr for ease of use ?
> Expose IndexWriter.commit(Map<String,String> commitUserData) to solr
> ---------------------------------------------------------------------
>
> Key: SOLR-2701
> URL: https://issues.apache.org/jira/browse/SOLR-2701
> Project: Solr
> Issue Type: New Feature
> Components: update
> Affects Versions: 4.0-ALPHA
> Reporter: Eks Dev
> Priority: Minor
> Labels: commit, update
> Attachments: SOLR-2701-Expose-userCommitData-throughout-solr.patch,
> SOLR-2701.patch
>
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> At the moment, there is no feature that enables associating user information
> to the commit point.
>
> 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 updates.
--
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: [email protected]
For additional commands, e-mail: [email protected]
