spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Iljya Kalai (JIRA)" <>
Subject [jira] [Commented] (SPARK-4820) Spark build encounters "File name too long" on some encrypted filesystems
Date Tue, 23 Dec 2014 15:51:14 GMT


Iljya Kalai commented on SPARK-4820:

Thanks for creating this issue, and thanks to Luchesar for providing a workaround. Are the
ramifications of pulling this into the head repository known? It would be great if compiling
on encrypted drives just worked. It's a bit unfortunate that new Spark users with encrypted
drives will get slammed by this issue upon trying to compile Spark for the first time.

> Spark build encounters "File name too long" on some encrypted filesystems
> -------------------------------------------------------------------------
>                 Key: SPARK-4820
>                 URL:
>             Project: Spark
>          Issue Type: Bug
>            Reporter: Patrick Wendell
> This was reported by Luchesar Cekov on github along with a proposed fix. The fix has
some potential downstream issues (it will modify the classnames) so until we understand better
how many users are affected we aren't going to merge it. However, I'd like to include the
issue and workaround here. If you encounter this issue please comment on the JIRA so we can
assess the frequency.
> The issue produces this error:
> {code}
> [error] == Expanded type of tree ==
> [error] 
> [error] ConstantType(value = Constant(Throwable))
> [error] 
> [error] uncaught exception during compilation:
> [error] File name too long
> [error] two errors found
> {code}
> The workaround is in maven under the compile options add: 
> {code}
> +              <arg>-Xmax-classfile-name</arg>
> +              <arg>128</arg>
> {code}
> In SBT add:
> {code}
> +    scalacOptions in Compile ++= Seq("-Xmax-classfile-name", "128"),
> {code}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message