lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4575) Allow IndexWriter to commit, even just commitData
Date Thu, 29 Nov 2012 15:36:58 GMT


Shai Erera commented on LUCENE-4575:

bq. Then the only thing that would need to change is DataInput.readStringStringMap: s/HashMap/LinkedHashMap.

So you propose that the code will always initialize LHM in DataInput, that way preserving
order whether required or not? Yes, I guess that we can do that. But I wonder if we should?
We didn't so far, and nobody complained. And since it's an internal change, we can always
make that change in the future if somebody asks?
> Allow IndexWriter to commit, even just commitData
> -------------------------------------------------
>                 Key: LUCENE-4575
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/index
>            Reporter: Shai Erera
>            Priority: Minor
>         Attachments: LUCENE-4575.patch
> Spinoff from here
> In some cases, it is valuable to be able to commit changes to the index, even if the
changes are just commitData. Such data is sometimes used by applications to register in the
index some global application information/state.
> The proposal is:
> * Add a setCommitData() API and separate it from commit() and prepareCommit() (simplify
their API)
> * When that API is called, flip on the dirty/changes bit, so that this gets committed
even if no other changes were made to the index.
> I will work on a patch a post.

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message