Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 29 Nov 2012 03:37:16 +0000 (UTC)
From: "Yonik Seeley (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <1606561595.37548.1354160236493.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <1707168022.14119.1312664607135.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (SOLR-2701) Expose
 IndexWriter.commit(Map<String,String> commitUserData) to solr
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yonik Seeley commented on SOLR-2701:
------------------------------------

bq. Should previous index commits carry forward in solr for ease of use ?

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.
                
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org