[
https://issues.apache.org/jira/browse/FLINK-9739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534592#comment-16534592
]
Stephan Ewen commented on FLINK-9739:
-------------------------------------
Do we have some more details on this?
{{File.isAbsolute()}} only looks at the path, does not have to access the file.
However, the decision of whether the path is absolute depends on the client's
file system.
We could
- undo FLINK-6557
- Skip the check for absolute file
> Regression in supported filesystems for RocksDB
> -----------------------------------------------
>
> Key: FLINK-9739
> URL: https://issues.apache.org/jira/browse/FLINK-9739
> Project: Flink
> Issue Type: Bug
> Components: FileSystem, State Backends, Checkpointing
> Affects Versions: 1.5.0, 1.6.0
> Reporter: Chesnay Schepler
> Priority: Major
>
> A user reporter on the [mailing
> list|http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Checkpointing-in-Flink-1-5-0-tt21173.html]
> has reported that the {{RocksDBStateBackend}} no longer supports GlusterFS
> mounted volumes.
> Configuring {{file:///home/abc/share}} lead to an exception that claimed the
> path to not be absolute.
> This was working fine in 1.4.2.
> In FLINK-6557 the {{RocksDBStateBackend}} was refactored to use java
> {{Files}} instead of Flink {{Paths}}, potentially causing the issue.
> It introduced an {{File#isAbsolute}} check, which for inaccessible files
> returns false.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
