You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2015/09/09 20:17:48 UTC
[jira] [Resolved] (FLINK-2003) Building on some encrypted
filesystems leads to "File name too long" error
[ https://issues.apache.org/jira/browse/FLINK-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-2003.
---------------------------------
Resolution: Fixed
Assignee: Theodore Vasiloudis
Fix Version/s: 0.10
Documentation how to deal with this has been added in 4b6eae5a612ab1b28b64715acd831dccc0ea6d35
> 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
> Assignee: Theodore Vasiloudis
> Priority: Minor
> Labels: build, starter
> Fix For: 0.10
>
>
> 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)