GitHub user PhilippGrulich opened a pull request:
https://github.com/apache/zeppelin/pull/1608
[ZEPPELIN-1633] Flink: Set maxClassfileName to 128
### What is this PR for?
This bug was fixed for the spark interpreter in
https://issues.apache.org/jira/browse/ZEPPELIN-926, but the bug can also
occur in the Flink interpreter.
So we have to migrate the patch to the flink interpreter.
### What type of PR is it?
Bug Fix
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1633
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SWC-SENSE/zeppelin flink_file_name_to_long
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1608.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 #1608
----
commit e31285c0aaab4624dc3bfcb15cc6dd1b722e323a
Author: Philipp <[email protected]>
Date: 2016-11-07T12:00:17Z
Flink: Set maxClassfileName to 128
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
