[jira] [Updated] (LUCENE-3659) Allow per-RAMFile buffer sizes based on IOContext and source of data (e.g. copy from another directory)
[ https://issues.apache.org/jira/browse/LUCENE-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley updated LUCENE-3659: - Fix Version/s: (was: 4.7) 4.8 Allow per-RAMFile buffer sizes based on IOContext and source of data (e.g. copy from another directory) --- Key: LUCENE-3659 URL: https://issues.apache.org/jira/browse/LUCENE-3659 Project: Lucene - Core Issue Type: Sub-task Affects Versions: 4.0-ALPHA Reporter: Uwe Schindler Assignee: Uwe Schindler Fix For: 4.8 Attachments: LUCENE-3659.patch, LUCENE-3659.patch, LUCENE-3659.patch, LUCENE-3659.patch Spinoff from several dev@lao issues: - [http://mail-archives.apache.org/mod_mbox/lucene-dev/201112.mbox/%3C001001ccbf1c%2471845830%24548d0890%24%40thetaphi.de%3E] - issue LUCENE-3653 The use cases for RAMDirectory are very limited and to prevent users from using it for e.g. loading a 50 Gigabyte index from a file on disk, we should improve the javadocs. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-3659) Allow per-RAMFile buffer sizes based on IOContext and source of data (e.g. copy from another directory)
[ https://issues.apache.org/jira/browse/LUCENE-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-3659: -- Fix Version/s: (was: 4.3) 4.4 Allow per-RAMFile buffer sizes based on IOContext and source of data (e.g. copy from another directory) --- Key: LUCENE-3659 URL: https://issues.apache.org/jira/browse/LUCENE-3659 Project: Lucene - Core Issue Type: Sub-task Affects Versions: 4.0-ALPHA Reporter: Uwe Schindler Assignee: Uwe Schindler Fix For: 4.4 Attachments: LUCENE-3659.patch, LUCENE-3659.patch, LUCENE-3659.patch, LUCENE-3659.patch Spinoff from several dev@lao issues: - [http://mail-archives.apache.org/mod_mbox/lucene-dev/201112.mbox/%3C001001ccbf1c%2471845830%24548d0890%24%40thetaphi.de%3E] - issue LUCENE-3653 The use cases for RAMDirectory are very limited and to prevent users from using it for e.g. loading a 50 Gigabyte index from a file on disk, we should improve the javadocs. -- 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-3659) Allow per-RAMFile buffer sizes based on IOContext and source of data (e.g. copy from another directory)
[ https://issues.apache.org/jira/browse/LUCENE-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated LUCENE-3659: --- Fix Version/s: (was: 4.1) 4.2 Allow per-RAMFile buffer sizes based on IOContext and source of data (e.g. copy from another directory) --- Key: LUCENE-3659 URL: https://issues.apache.org/jira/browse/LUCENE-3659 Project: Lucene - Core Issue Type: Sub-task Affects Versions: 4.0-ALPHA Reporter: Uwe Schindler Assignee: Uwe Schindler Fix For: 4.2 Attachments: LUCENE-3659.patch, LUCENE-3659.patch, LUCENE-3659.patch, LUCENE-3659.patch Spinoff from several dev@lao issues: - [http://mail-archives.apache.org/mod_mbox/lucene-dev/201112.mbox/%3C001001ccbf1c%2471845830%24548d0890%24%40thetaphi.de%3E] - issue LUCENE-3653 The use cases for RAMDirectory are very limited and to prevent users from using it for e.g. loading a 50 Gigabyte index from a file on disk, we should improve the javadocs. -- 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-3659) Allow per-RAMFile buffer sizes based on IOContext and source of data (e.g. copy from another directory)
[ https://issues.apache.org/jira/browse/LUCENE-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-3659: -- Attachment: LUCENE-3659.patch Patch updated to trunk. I will work on this soon. Allow per-RAMFile buffer sizes based on IOContext and source of data (e.g. copy from another directory) --- Key: LUCENE-3659 URL: https://issues.apache.org/jira/browse/LUCENE-3659 Project: Lucene - Core Issue Type: Sub-task Affects Versions: 4.0-ALPHA Reporter: Uwe Schindler Assignee: Uwe Schindler Fix For: 4.1 Attachments: LUCENE-3659.patch, LUCENE-3659.patch, LUCENE-3659.patch, LUCENE-3659.patch Spinoff from several dev@lao issues: - [http://mail-archives.apache.org/mod_mbox/lucene-dev/201112.mbox/%3C001001ccbf1c%2471845830%24548d0890%24%40thetaphi.de%3E] - issue LUCENE-3653 The use cases for RAMDirectory are very limited and to prevent users from using it for e.g. loading a 50 Gigabyte index from a file on disk, we should improve the javadocs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-3659) Allow per-RAMFile buffer sizes based on IOContext and source of data (e.g. copy from another directory)
[ https://issues.apache.org/jira/browse/LUCENE-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-3659: -- Affects Version/s: (was: 3.5) Fix Version/s: (was: 3.6) Summary: Allow per-RAMFile buffer sizes based on IOContext and source of data (e.g. copy from another directory) (was: Improve Javadocs of RAMDirectory to document its limitations and add improvements to make it more GC friendly on large indexes) Allow per-RAMFile buffer sizes based on IOContext and source of data (e.g. copy from another directory) --- Key: LUCENE-3659 URL: https://issues.apache.org/jira/browse/LUCENE-3659 Project: Lucene - Java Issue Type: Sub-task Affects Versions: 4.0 Reporter: Uwe Schindler Assignee: Uwe Schindler Fix For: 4.0 Attachments: LUCENE-3659.patch, LUCENE-3659.patch, LUCENE-3659.patch Spinoff from several dev@lao issues: - [http://mail-archives.apache.org/mod_mbox/lucene-dev/201112.mbox/%3C001001ccbf1c%2471845830%24548d0890%24%40thetaphi.de%3E] - issue LUCENE-3653 The use cases for RAMDirectory are very limited and to prevent users from using it for e.g. loading a 50 Gigabyte index from a file on disk, we should improve the javadocs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
