Github user thvasilo commented on a diff in the pull request:
https://github.com/apache/flink/pull/690#discussion_r30577392
--- Diff: flink-yarn/pom.xml ---
@@ -113,6 +113,10 @@ under the License.
<jvmArg>-Xms128m</jvmArg>
<jvmArg>-Xmx512m</jvmArg>
</jvmArgs>
+ <args>
+ <arg>-Xmax-classfile-name</arg>
+ <arg>128</arg>
--- End diff --
According to the [man pages for
EncFS](http://manpages.ubuntu.com/manpages/trusty/man1/encfs.1.html):
> One such limitation is filename length. If your underlying filesystem
limits you to N characters in a filename, then EncFS will limit you
to
approximately 3*(N-2)/4. For example if the host filesystem limits
to
256 characters, then EncFS will be limited to 190 character
filenames.
This is because encrypted filenames are always longer then plaintext
filenames.
So that would be <190 characters for ext4, but it depends on the
filesystem.
I get the feeling that this creates unneeded headaches. I could change this
PR into a docs one instead, and add a mention of the workaround in the docs as
you suggested.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
