GitHub user rawkintrevo reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/794
[ZEPPELIN-760] Companion object bug fix for Flink Interpretter
### What is this PR for?
This implements the solution presented for the Spark interpreter in PR-780
for the Flink, Scalding, and Ignite interpreters.
### What type of PR is it?
Improvement
### Todos
* [x] - Fix line splitting
* [x] - Add tests
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-658
* https://issues.apache.org/jira/browse/ZEPPELIN-747
### How should this be tested?
Add a new paragraph with each interpreter and define a class with its
companion object.
See bug ZEPPELIN-658 for more details
### Screenshots (if appropriate)
### 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/rawkintrevo/incubator-zeppelin
flink-companion-objects
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/794.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 #794
----
commit 994312c80745fd1d23db09396a5704d77d87177d
Author: Trevor Grant <[email protected]>
Date: 2016-03-23T18:58:57Z
[ZEPPELIN-658] Companion object bug fix for Flink Interpretter
push torestart build
[ZEPPELIN-760] Companion objects in Flink, Scalding, and Ignite interpreters
[ZEPPELIN-760] Fixed Tests
[ZEPPELIN-760] Fixed Ignite Test
[ZEPPELIN-760] Fixed Ignite Test
commit ff086c77a954433e65e0b3f850ab2503d029d212
Author: Trevor Grant <[email protected]>
Date: 2016-03-25T15:38:34Z
[ZEPPELIN-760] Dropped duplicate Scalding Test
commit b37adbbec4e14ef7264ac750a3d7a4cdc04599e8
Author: Trevor Grant <[email protected]>
Date: 2016-03-25T16:05:20Z
[ZEPPELIN-760] Dropped redundent Flink Test
----
---
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.
---
