[ 
https://issues.apache.org/jira/browse/BEAM-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132109#comment-17132109
 ] 

Beam JIRA Bot commented on BEAM-1045:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it 
has been labeled "stale-P2". If this issue is still affecting you, we care! 
Please comment and remove the label. Otherwise, in 14 days the issue will be 
moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed 
explanation of what these priorities mean.


> Windows OS compatibilities
> --------------------------
>
>                 Key: BEAM-1045
>                 URL: https://issues.apache.org/jira/browse/BEAM-1045
>             Project: Beam
>          Issue Type: Sub-task
>          Components: io-java-gcp, sdk-java-core
>            Reporter: Pei He
>            Priority: P2
>              Labels: stale-P2
>
> One known issue is "*" is not allowed in Windows OS.
> For example, Paths.get("tempDir/*") might throw when code runs in Windows OS.
> http://stackoverflow.com/questions/27522581/asterisks-in-java-path
> This affecting IOChannelFactory.resolve(), toPath(), and match().
> For match(), since it only requires support globs in the final component of a 
> path. (local) FileIOChannelFactory could do things similar as 
> GcsIOChannelFactory:
> First, list all files under the directory path (this won't contain glob, such 
> as *).
> Then, check each returned files whether it matches glob.
> In this way, glob (*) stays within Apache Beam's code.
> From match()'s javadoc:
> """
> Glob handling is dependent on the implementation.  Implementations should
>    * all support globs in the final component of a path (eg /foo/bar/*.txt),
>    * however they are not required to support globs in the directory paths.
> """



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to