You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by GitBox <gi...@apache.org> on 2022/02/15 19:10:30 UTC

[GitHub] [lucenenet] NightOwl888 commented on issue #262: Lucene & Memory Mapped Files

NightOwl888 commented on issue #262:
URL: https://github.com/apache/lucenenet/issues/262#issuecomment-1040634847


   @hamzashoukat94
   
   Actually, it was @vvdb that [first reported this](https://lists.apache.org/thread/dwnk27cjppjc12pnwq4w4jlzg08rqlrr) on the [dev mailing list](https://lucenenet.apache.org/contributing/mailing-lists.html#developers-dev). He was instrumental in helping to bridge the gap on many components in the Lucene.Net.Store namespace, however hasn't contributed in a couple of years. To track the progress of the issue, I posted it on [JIRA as LUCENENET-629](https://issues.apache.org/jira/browse/LUCENENET-629) and then we eventually migrated from JIRA to GitHub issues.
   
   A lot has changed since this was first reported.
   
   1. The `MemoryMappedFileByteBuffer` was refactored and moved to J2N as 4 classes in the [J2N.IO.MemoryMappedFiles namespace](https://github.com/NightOwl888/J2N/tree/ceaa3d17f3866a5ec4865f9be600b76c5303764c/src/J2N/IO/MemoryMappedFiles).
   2. A test was done on the changes, and they functioned, but did not pass all of the tests as-is.
   
   As of now, we don't consider this to be an issue blocking the 4.8.0 release, but an optional performance enhancement that we might be able to look into after the release. Thanks for the link, though. It does seem related, and it may be that we don't need to fix anything on our end.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@lucenenet.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org