[
https://issues.apache.org/jira/browse/LUCENE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614861#comment-14614861
]
Dawid Weiss commented on LUCENE-6563:
-------------------------------------
I honestly think this is a quirk/bug in the JVM... and perhaps should be
reported. Setting LANG=C shouldn't be affecting how filenames are (mis)handled
(and it currently does).
bq. so if we are not able to create non-ASCII filenames to begin with,
shouldn't the mock filesystem not try to use them?
Well, it's a good test, isn't it? :) Caught the nasty thing right away... I
don't have a strong opinion. I think modifying the mock filesystem to enforce
ASCII-only names and them removing that non-ascii test section sounds all
right. Could you provide a patch and check if it passes on your systems?
> sun.jnu.encoding to match file.encoding system property
> (MockFileSystemTestCase.testURI)
> ----------------------------------------------------------------------------------------
>
> Key: LUCENE-6563
> URL: https://issues.apache.org/jira/browse/LUCENE-6563
> Project: Lucene - Core
> Issue Type: Wish
> Reporter: Christine Poerschke
> Assignee: Dawid Weiss
> Priority: Minor
>
> {{ant test -Dtestcase=TestVerboseFS -Dtests.method=testURI
> -Dtests.file.encoding=UTF-8}} fails (for example) with 'Oracle Corporation
> 1.8.0_45 (64-bit)' when the default {{sun.jnu.encoding}} system property is
> (for example) {{ANSI_X3.4-1968}}
> [details to follow]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
