[
https://issues.apache.org/jira/browse/FLINK-7676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321631#comment-17321631
]
Flink Jira Bot commented on FLINK-7676:
---------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> ContinuousFileMonitoringFunction fails with GoogleHadoopFileSystem
> ------------------------------------------------------------------
>
> Key: FLINK-7676
> URL: https://issues.apache.org/jira/browse/FLINK-7676
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Common
> Reporter: Ufuk Celebi
> Priority: Minor
> Labels: stale-minor
>
> The following check in ContinuousFileMonitoringFunction fails when running
> against a file in Google Cloud Storage:
> {code}
> Path p = new Path(path);
> FileSystem fileSystem = FileSystem.get(p.toUri());
> if (fileSystem.exists(p)) {
> throw new FileNotFoundException("The provided file path " + path + " does
> not exist.");
> }
> {code}
> I suspect this has something to do with consistency guarantees provided by
> GCS. I'm wondering if it's better to fail lazily at a later stage (e.g. when
> opening the stream and it doesn't work).
> After removing this check, everything works as expected. I can also run a
> batch WordCount job against the same file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
