[
https://issues.apache.org/jira/browse/LUCENE-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966508#action_12966508
]
Robert Muir commented on LUCENE-2791:
-------------------------------------
bq. And Mike also said that we may create files by codecs with names that are
non-ascii. And as you are the unicode policeman, I dont unterstand how you can
live with default charsets...
its my understanding that all indexfiles/codecs are ascii-only.
If this is going to change, then there is a lot of policework to do. Personally
i would really prefer if we simply keep codecs and lucene filenames as
ascii-only!
For non-ascii filenames, java.io.File is broken, its equals() is inconsistent
with its hashCode(), even on windows, and definitely on things like macos (as i
think it still uses unicode normalization to normalize filenames). We should
seriously avoid the system-dependent problems that will arise by using
non-ascii filenames in these parts of lucene: i don't see this bringing a lot
of benefits either.
> WindowsDirectory
> ----------------
>
> Key: LUCENE-2791
> URL: https://issues.apache.org/jira/browse/LUCENE-2791
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Store
> Reporter: Robert Muir
> Attachments: LUCENE-2791.patch, LUCENE-2791.patch,
> WindowsDirectory.dll, WindowsDirectory_amd64.dll
>
>
> We can use Windows' overlapped IO to do pread() and avoid the performance
> problems of SimpleFS/NIOFSDir.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
