[
https://issues.apache.org/jira/browse/FLINK-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733774#comment-14733774
]
ASF GitHub Bot commented on FLINK-2003:
---------------------------------------
GitHub user thvasilo opened a pull request:
https://github.com/apache/flink/pull/1100
[FLINK-2003] [docs] Building on some encrypted filesystems leads to "File
name too long" error
Replaces #690, adding docs instead of changing the pom files.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/thvasilo/flink encfs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1100.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1100
----
commit 0e1d83a58047a4af5a991e2c30bc8fc1398139fb
Author: Theodore Vasiloudis <t...@sics.se>
Date: 2015-09-07T14:25:58Z
Added instructions for encrypted filesystems
----
> Building on some encrypted filesystems leads to "File name too long" error
> --------------------------------------------------------------------------
>
> Key: FLINK-2003
> URL: https://issues.apache.org/jira/browse/FLINK-2003
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Reporter: Theodore Vasiloudis
> Priority: Minor
> Labels: build, starter
>
> The classnames generated from the build system can be too long.
> Creating too long filenames in some encrypted filesystems is not possible,
> including encfs which is what Ubuntu uses.
> This the same as this [Spark
> issue|https://issues.apache.org/jira/browse/SPARK-4820]
> The workaround (taken from the linked issue) is to add in Maven under the
> compile options:
> {code}
> + <arg>-Xmax-classfile-name</arg>
> + <arg>128</arg>
> {code}
> And in SBT add:
> {code}
> + scalacOptions in Compile ++= Seq("-Xmax-classfile-name", "128"),
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
