[
https://issues.apache.org/jira/browse/LUCENE-6849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991572#comment-14991572
]
Robert Muir commented on LUCENE-6849:
-------------------------------------
I disagree. I don't think we should add anything but a no-arg flush() here.
If its going to be more engineered than that, then this is the wrong direction:
lets just not expose it at all.
> Add IndexWriter API to write segment(s) without refreshing them
> ---------------------------------------------------------------
>
> Key: LUCENE-6849
> URL: https://issues.apache.org/jira/browse/LUCENE-6849
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: Trunk, 5.4
>
> Attachments: LUCENE-6849.patch
>
>
> Today, the only way to have {{IndexWriter}} free up some heap is to invoke
> refresh or flush or close it, but these are all quite costly, and do much
> more than simply "move bytes to disk".
> I think we should add a simple API, e.g. "move the biggest in-memory segment
> to disk" to 1) give more granularity (there could be multiple in-memory
> segments), and 2) only move bytes to disk (not refresh, not fsync, etc.).
> This way apps that want to be more careful on how heap is used can have more
> control.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
