[
https://issues.apache.org/jira/browse/SOLR-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506688#comment-13506688
]
Greg Bowyer commented on SOLR-2701:
-----------------------------------
bq. I haven't had a chance to check out the rest of the patch/issue, but for
this specifically, what about a convention? Anything under the "persistent" key
in the commit data is carried over indefinitely. Or if persistent is the norm,
then we could reverse it and have a "transient" map that is not carried over.
The persistent/transient map sounds like a good idea; I will take a look at how
that can be implemented
> 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]
