METRON-1382 Run Stellar in a Zeppelin Notebook #884

nickwallen · 2017-12-25T20:57:47Z

Stellar in a Zeppelin Notebook

The goal of this effort was to have the shell-like experience of the command-line driven REPL, but inside a web-based Zeppelin Notebook. This makes the existing functionality provided by the REPL more accessible and approachable for the average user.

This also opens up interesting additional scenarios like "executable" use cases or plotting profile data. Definitely more work to do on those fronts, but this is a first step.

Changes

There was a good amount of refactoring that I needed to do to achieve this. Prior to this effort different aspects of the REPL's functionality were tied together in the StellarShell class. To be able to have the same shell-like experience in both the REPL and Zeppelin, I needed to factor this logic out separately to allow for reuse.

This included the following bits.
- Console logic tied to the AESH library
- Stellar execution logic
- Autocomplete logic
- Variable assignment (only available in the shell)
- Magics
- Docstrings
- Comments
- quit
We had very few automated tests around the shell/REPL, primarily because all these bits were tied together, which made testing difficult. Separating out this logic allowed me to add a large number of unit tests around each of these pieces of logic.
This also adds a separate project metron-stellar/stellar-zeppelin that provides a Zeppelin interpreter that allow you to run Stellar in a notebook. The interpreter acts as the front-end that then re-uses all of the bits that I refactored as described above.

What does this do?

This allows you to run Stellar expressions in a Zeppelin Notebook.
This provides auto-complete in the Zeppelin Notebook by pressing the CTRL + . keys.

What does this not do?

This does not automatically prepare the Zeppelin environment to run Stellar. Meaning it does not install the Stellar interpreter in Zeppelin. You have to manually install the zinterpreter in Zeppelin by following the directions described in the metron-stellar/stellar-zepelin README.

Testing

Run Stellar in Notebook

Build Metron.
Follow the instructions in metron-stellar/stellar-zepelin/README.md to download/run Zeppelin locally.
Follow the same instructions to execute Stellar expressions in a Zeppelin Notebook.
Use CTRL + . to try out autocomplete.

Validate the CLI REPL

Deploy Full Dev
Run the existing CLI-driven REPL
Validate that we have feature parity

Pull Request Checklist

Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically master)?
Have you included steps to reproduce the behavior or problem that is being changed or addressed?
Have you included steps or a guide to how the change may be verified and tested manually?
Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
Have you written or updated unit tests and or integration tests to verify your changes?
If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

nickwallen

A few notes to guide reviewers...

nickwallen · 2017-12-25T21:01:11Z

...common/src/main/java/org/apache/metron/stellar/common/shell/DefaultStellarAutoCompleter.java

+/**
+ * Provides auto-completion for Stellar.
+ */
+public class DefaultStellarAutoCompleter implements StellarAutoCompleter {


This class provides the core auto-completion logic for both the CLI-based REPL and Zeppelin.

nickwallen · 2017-12-25T21:01:49Z

...common/src/main/java/org/apache/metron/stellar/common/shell/DefaultStellarAutoCompleter.java

+    this.autocompleteIndex = initializeIndex();
+
+    // TODO is this needed?  FunctionResolver functionResolver
+//    // asynchronously update the index with function names found from a classpath scan.


Is this logic needed any longer? I don't feel it is, but need to dig on this some more.

nickwallen · 2017-12-25T21:03:12Z

...common/src/main/java/org/apache/metron/stellar/common/shell/DefaultStellarShellExecutor.java

+ * Default implementation of a StellarShellExecutor.
+ */
+public class DefaultStellarShellExecutor implements StellarShellExecutor {
+


This class provides the core execution logic for both the REPL and Zeppelin. It handles core Stellar in addition to the "extensions" like assignment, magics, docstrings, etc.

nickwallen · 2017-12-25T21:06:00Z

...common/src/main/java/org/apache/metron/stellar/common/shell/DefaultStellarShellExecutor.java

+    for(SpecialCommand command : commandRegistry) {
+      if(command.getMatcher().apply(expression)) {
+        return command.execute(expression, this);
+      }


Anything that is not "core" Stellar is defined separately as a SpecialCommand.

nickwallen · 2017-12-25T21:06:39Z

...common/src/main/java/org/apache/metron/stellar/common/shell/DefaultStellarShellExecutor.java

+            new MagicDefineGlobal(),
+            new MagicUndefineGlobal(),
+            new MagicListGlobals()
+    );


All the specials are made available here.

If we ever do something like add assignment to the core Stellar language (like #687) then all we have to do is not use/remove the AssignmentCommand class.

nickwallen · 2017-12-25T21:09:24Z

...r-common/src/main/java/org/apache/metron/stellar/common/shell/StellarExecutionListeners.java

+
+  public interface SpecialDefinedListener {
+    void whenSpecialDefined(SpecialCommand magic);
+  }


Event listeners can be notified when variables, functions, or specials are defined. Useful in our case for notifying the autocompleter.

nickwallen · 2017-12-25T21:11:42Z

...ar/stellar-common/src/main/java/org/apache/metron/stellar/common/shell/cli/StellarShell.java

+ *
+ * Useful for debugging Stellar expressions.
+ */
+public class StellarShell extends AeshConsoleCallback implements Completion {


The StellarShell now only contains logic to drive the Aesh console.

nickwallen · 2017-12-25T21:13:49Z

...ar/stellar-common/src/main/java/org/apache/metron/stellar/common/shell/cli/StellarShell.java

+   */
+  @Override
+  public void complete(CompleteOperation completeOperation) {
+    String buffer = completeOperation.getBuffer();


Ties our generic autocompleter to the autocomplete interface required by Aesh.

nickwallen · 2017-12-25T21:15:40Z

...lar-common/src/main/java/org/apache/metron/stellar/common/shell/specials/SpecialCommand.java

+   * @param executor A stellar execution environment.
+   * @return The result of executing the magic command.
+   */
+  StellarShellResult execute(String expression, StellarShellExecutor executor);


The interface for all specials; assignment, comments, magics, docstrings, etc.

nickwallen · 2017-12-25T21:17:09Z

metron-stellar/stellar-zeppelin/README.md

+
+[Apache Zeppelin](https://zeppelin.apache.org/) is a web-based notebook that enables data-driven, interactive data analytics and collaborative documents with SQL, Scala and more.  This project provides a means to run the Stellar REPL directly within a Zeppelin Notebook.
+
+## Installation


Instructions for installing/running in a notebook.

Can you please add the license header to this? #884 is close to going in and enforcing this, so I'm hoping to avoid impact to master.

Sure, done.

…plify its use

…m Stellar

nickwallen

More notes to help guide reviewers through the code.

nickwallen · 2018-01-03T18:34:12Z

...on-platform/metron-management/src/main/java/org/apache/metron/management/ShellFunctions.java

        data[i++] = new String[] { toWrappedString(kv.getKey().toString(), wordWrap)
                                 , toWrappedString(result.getResult(), wordWrap)
-                                 , toWrappedString(result.getExpression(), wordWrap)
+                                 , toWrappedString(result.getExpression().get(), wordWrap)


The VariableResult.expression field is now optional. We do not always know the expression that resulted in a value. The ShellFunctions just needed updated to treat this as an Optional.

nickwallen · 2018-01-03T18:36:53Z

metron-stellar/stellar-common/README.md

 ```
 $ mvn exec:java \
-   -Dexec.mainClass="org.apache.metron.stellar.common.shell.StellarShell" \
+   -Dexec.mainClass="org.apache.metron.stellar.common.shell.cli.StellarShell" \


StellarShell, the main driver class for the CLI-based REPL, was moved to its own package since it is only used by the CLI-based REPL. This separates it from the other core classes that are used by both the Zeppelin and CLI-based REPLs.

nickwallen · 2018-01-03T18:39:35Z

...common/src/main/java/org/apache/metron/stellar/common/shell/DefaultStellarShellExecutor.java

+            new MagicDefineGlobal(),
+            new MagicUndefineGlobal(),
+            new MagicListGlobals()
+    );


If we ever do something like add assignment to the core Stellar language (like #687) then all we have to do is not use/remove the AssignmentCommand class.

nickwallen · 2018-01-03T18:41:50Z

...r-common/src/main/java/org/apache/metron/stellar/common/shell/StellarExecutionListeners.java

+   */
+  public interface FunctionDefinedListener {
+    void whenFunctionDefined(StellarFunctionInfo functionInfo);
+  }


I used an event listener pattern so that external entities could get notified when things occur during the execution of Stellar. For example, the auto-completer needs to know when a variable is defined.

Nothing seems to be ever removed, can that ever be a problem? That will typically cause retention... and 'leaks'.

I don't see how this would cause a leak. Yes, in some cases listeners can cause troubles, but I don't see how it is a problem here. Can you be more specific? Otherwise, I don't know what needs a fixin' here.

Sorry, battle scars.

nickwallen · 2018-01-03T18:43:00Z

...ar-common/src/main/java/org/apache/metron/stellar/common/shell/StellarExecutionNotifier.java

+   * Add a listener that will be notified when a magic command is defined.
+   * @param listener The listener to notify.
+   */
+  void addSpecialListener(StellarExecutionListeners.SpecialDefinedListener listener);


Our DefaultStellarShellExecutor is a StellarExecutionNotifier as it is able to notify event listeners when variables, functions or specials are defined.

nickwallen · 2018-01-03T18:49:27Z

...stellar-common/src/main/java/org/apache/metron/stellar/common/shell/specials/DocCommand.java

+ *
+ * For example `?TO_STRING` will output the docs for the function `TO_STRING`
+ */
+public class DocCommand implements SpecialCommand {


Doc strings are not part of the core language.

nickwallen · 2018-01-03T18:50:17Z

...tellar-common/src/main/java/org/apache/metron/stellar/common/shell/specials/QuitCommand.java

+ *
+ *    quit
+ */
+public class QuitCommand implements SpecialCommand {


This is what allows a user to execute quit within the REPL. Again, not part of core Stellar.

nickwallen · 2018-01-03T18:51:03Z

...lar-common/src/main/java/org/apache/metron/stellar/common/shell/specials/SpecialCommand.java

+ * This is typically an action performed on the execution
+ * environment, not something that could be executed within Stellar.
+ */
+public interface SpecialCommand {


The interface that I used for any logic that we had implemented in the REPL that is not part of the Stellar language.

nickwallen · 2018-01-03T18:53:16Z

...ar/stellar-zeppelin/src/main/java/org/apache/metron/stellar/zeppelin/StellarInterpreter.java

+/**
+ * A Zeppelin Interpreter for Stellar.
+ */
+public class StellarInterpreter extends Interpreter {


This is what allows us to run Stellar in a Notebook.

nickwallen · 2018-01-03T18:54:40Z

...ar/stellar-zeppelin/src/main/java/org/apache/metron/stellar/zeppelin/StellarInterpreter.java

+  }
+
+  @Override
+  public List<InterpreterCompletion> completion(String buf, int cursor) {


This is where we connect our generic auto-completer that is used across both REPLs into the auto-complete extension point offered by Zeppelin.

ottobackwards · 2018-01-03T19:18:05Z

This is quite a bit to go over.... can I trade you a similarly large review task?

merrimanr · 2018-01-03T21:49:51Z

I think this is an excellent start. So far I have only reviewed it from a user perspective and it's working well.

I've spun it up in full dev (not sure that's even necessary) and installed this via the instructions in the README. I was able to run most of the examples in the Stellar README.

I found that the functions available in Zeppelin are a subset of what's available in the Stellar shell. The missing functions include IS_EMAIL, ENRICHMENT*, GEO*, STATS* and many others. Is this expected?

Is there a way to pass in the zookeeper url in Zeppelin?

merrimanr · 2018-01-03T21:58:45Z

I also noticed that functions returning a list only display the first item in both the shell and Zeppelin output.

For example, the expression MAP([ 'foo', 'bar'], (x) -> TO_UPPER(x) ) returns FOO when I would expect it to return ['FOO', 'BAR'].

From what I can tell the problem is only in how the result is displayed. For example, the expression 'BAR' in MAP([ 'foo', 'bar'], (x) -> TO_UPPER(x) ) returns true as expected.

nickwallen · 2018-01-03T22:50:27Z

Thanks for digging into it @merrimanr . You uncovered some good stuff.

I found that the functions available in Zeppelin are a subset of what's available in the Stellar shell. The missing functions include IS_EMAIL, ENRICHMENT*, GEO*, STATS* and many others. Is this expected?

Yes, since we only added stellar-common to the interpreter, only the functions defined in that library are available.

I just updated the README to clarify this point. I also added instructions for adding additional libraries to gain access to more Stellar functions.

nickwallen · 2018-01-03T22:52:16Z

@merrimanr: Is there a way to pass in the zookeeper url in Zeppelin?

No, I did not implement that in this PR. As a next step I was going to do whatever needs done to get the management functions working in Zeppelin. That would include adding a Zookeeper URL.

nickwallen · 2018-01-03T22:53:11Z

@merrimanr: From what I can tell the problem is only in how the result is displayed. For example, the expression 'BAR' in MAP([ 'foo', 'bar'], (x) -> TO_UPPER(x) ) returns true as expected.

BUG! Good find. The value getting returned is always the first. I'll fix that.

nickwallen · 2018-01-03T23:44:19Z

The problem is on the UI side of things; for both Zeppelin and the CLI. When I get the result back from Stellar, I was using ConversionUtils.convert(value, String.class) to get me a result that I can display. ConversionUtils just gives you the first item back if you ask it to convert a list to a String. Oops.

nickwallen · 2018-01-04T02:02:27Z

@merrimanr Fixed that bug and was able to add a good amount of unit tests around it. Also figured out a way to unit test the Aesh-driven StellarShell class.

…tion instructions in the README

nickwallen · 2018-01-06T16:27:20Z

Ok will do @ottobackwards

nickwallen · 2018-01-06T17:04:00Z

And done. Please take a look when you get a chance.

ottobackwards · 2018-01-07T16:19:44Z

Is there a 'supported' or tested version of zeppelin?
I have 0.7.3 installed locally.

I am getting exceptions starting the stellar interpreter

org.apache.zeppelin.interpreter.InterpreterException: org.apache.thrift.TApplicationException: Internal error processing getFormType
	at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.getFormType(RemoteInterpreter.java:450)
	at org.apache.zeppelin.interpreter.LazyOpenInterpreter.getFormType(LazyOpenInterpreter.java:111)
	at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:387)
	at org.apache.zeppelin.scheduler.Job.run(Job.java:175)
	at org.apache.zeppelin.scheduler.RemoteScheduler$JobRunner.run(RemoteScheduler.java:329)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.thrift.TApplicationException: Internal error processing getFormType
	at org.apache.thrift.TApplicationException.read(TApplicationException.java:111)
	at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:71)
	at org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Client.recv_getFormType(RemoteInterpreterService.java:337)
	at org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Client.getFormType(RemoteInterpreterService.java:323)
	at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.getFormType(RemoteInterpreter.java:446)
	... 11 more

Also:

In the zeppelin site file, there is already a zeppelin.interpreters property, which in a comma separated list of class names. Is it right to create a new property vs. adding to the existing?

ottobackwards · 2018-01-07T16:21:15Z

Another question:
Even through it is consistent with the other interpreters, I am not sure that we should not have Apache Stellar, or Apache Metron Stellar and not just stellar as the name. It does not seem right to not have Apache there.

nickwallen · 2018-01-09T19:04:36Z

Is there a 'supported' or tested version of zeppelin? I have 0.7.3 installed locally.

0.7.3 is what the unit tests and what my manual testing have used.

I added this to the README.

nickwallen · 2018-01-09T19:05:22Z

@ottobackwards : In the zeppelin site file, there is already a zeppelin.interpreters property, which in a comma separated list of class names. Is it right to create a new property vs. adding to the existing?

Both work, but adding it to the existing is probably the better approach. I updated the README to reflect this.

nickwallen · 2018-01-09T19:11:16Z

@ottobackwards : I am getting exceptions starting the stellar interpreter

I have never seen this. I need more context unfortunately.

What do you mean by "starting the stellar interpreter"?
Is the exception coming from the Zeppelin logs or are you seeing this in a notebook?
When do you see the exception? After starting Zeppelin or after running Stellar in a notebook? Or sometime else?
Are you successfully running Stellar in a notebook at all?
I am assuming you followed the instructions in the README exactly? Is there anything in there that might be different from what you did?

ottobackwards · 2018-01-09T19:52:59Z

When I type something in the notebook and hit run. At least I think that is when I get the error. It may happen when selecting the interpreter for the notebook.
Yes
Running TO_UPPER('foo')
no, I get this for every statement I run.
Also, I don't get %stellar for the prompt like your screenshots

I set the interpreter through the dropdown not by typing %stellar
I didn't have to 'create' the stellar interpreter after starting, there was already an entry, I think from the site config

nickwallen · 2018-01-09T20:19:32Z

I didn't have to 'create' the stellar interpreter after starting, there was already an entry, I think from the site config

That does not (should not) happen. It should only be there when after you have created it in the UI.

Are you sure you haven't tried this a few times and either...
(1) There are left-over files in $ZEPPELIN_HOME between attempts
(2) Something is stored in browser cache, or even that...
(3) The Zeppelin instance was launched (and remains running) from one of your first attempts?

When I was playing with this a few weeks ago and was seeing weird behavior, I found that (3) was a problem for me. I either left the Zeppelin process running accidentally or the stop script in Zeppelin does not work all the time. I had to ps -ef | grep Zep and forcibly kill processes to make sure that the process was running with the configuration I expected.

ottobackwards · 2018-01-09T21:21:13Z

I think creating the /interpreters/stellar/x.json creates the entry?

I just tried again, ( new mvn install , new site file ) and I checked the interpreter log:

INFO [2018-01-09 16:14:22,873] ({Thread-0} RemoteInterpreterServer.java[run]:97) - Starting remote interpreter server on port 63321
2 ERROR [2018-01-09 16:14:23,545] ({pool-1-thread-3} RemoteInterpreterServer.java[createInterpreter]:204) - java.lang.ClassNotFoundException: org.apache.metron.stellar.zepplin.StellarInterpreter
3 java.lang.ClassNotFoundException: org.apache.metron.stellar.zepplin.StellarInterpreter
4 > at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
5 > at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
6 > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
7 > at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
8 > at java.lang.Class.forName0(Native Method)
9 > at java.lang.Class.forName(Class.java:264)
10 > at org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer.createInterpreter(RemoteInterpreterServer.java:178)
11 > at org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Processor$createInterpreter.getResult(RemoteInterpreterService.java:1662)
12 > at org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Processor$createInterpreter.getResult(RemoteInterpreterService.java:1647)
13 > at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
14 > at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
15 > at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:285)
16 > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
17 > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
18 > at java.lang.Thread.run(Thread.java:745)

ottobackwards · 2018-01-09T22:50:13Z

Can you run the check style against the interpreter class?
Also, do we want to use @Override?

nickwallen · 2018-01-10T13:29:37Z

Also, do we want to use @OverRide?

Done.

ottobackwards · 2018-01-10T13:57:51Z

@nickwallen I'm not sure what to do to get this going. The jar is in maven. I tried to path directly to it as well. I can attach my site and interpreter json files, and screenshot my settings....

ottobackwards · 2018-01-10T14:06:33Z

I'm going to try a clean zeppelin install I guess.

ottobackwards · 2018-01-10T14:43:28Z

ok, starting over

First difference, is on first start ( new install ) the stellar interpreter / group is already created in zeppelin when I go to configure the stellar interpreter

So I update and restart with new settings.

Interpreter is green.

Run the first two tasks with the following results:

I was able to run other stellar statements fine, so it is better

nickwallen · 2018-01-10T15:36:57Z

Ok, so it looks like it is working for you.

Zeppelin interprets the first line as the interpreter spec (or whatever they call it). That's why %functions failed because it thinks you want to use an interpreter called 'functions'. If you want to use a magic function like %functions either put that on a second line or make sure to specify %stellar explicitly like so...

%stellar

%functions

ottobackwards · 2018-01-12T14:30:23Z

Is the plan to deploy the jar file in the interpreter directory like the other interpreters?

nickwallen · 2018-01-12T14:36:02Z

Is the plan to deploy the jar file in the interpreter directory like the other interpreters?

I don't know what that is going to look like. We need to do more research to see how the setup can be automated by the Mpack. I don't want the user to have to do all this manual setup.

ottobackwards · 2018-01-12T15:20:47Z

Do we have jiras for the next steps on this yet? I would be good if we recored our intent, and who knows, maybe someone will want to work on it.

ottobackwards · 2018-01-12T16:18:09Z

This is really good work @nickwallen. I am +1 on this, but would like to see jiras on the next steps entered if possible as a side note.

nickwallen · 2018-01-12T18:05:06Z

Thanks for the reviews @ottobackwards and @merrimanr.

Here are next steps for where I'd like to use this functionality.

…ache#884

METRON-1382 Run Stellar in a Zeppelin Notebook

49fba6a

nickwallen commented Dec 25, 2017

View reviewed changes

nickwallen added 5 commits December 27, 2017 12:41

Rename StellarShellResult to StellarResult for simplicity

162f1f4

Added withExpression and withValue to the VariableResult class to sim…

b7cf23e

…plify its use

Created a separate interface for notification of events

4b65b26

Clean-up

031f65c

Simple clean-up

790cdd5

nickwallen force-pushed the METRON-1382 branch from 26f6558 to 790cdd5 Compare December 27, 2017 21:50

nickwallen added 3 commits December 28, 2017 13:21

Improved the installation instructions

18fe04c

Fixed a bug in the Zeppelin interpreter when no value is returned fro…

98f73bc

…m Stellar

Should be using System.lineSeparator()

fc74720

This was referenced Dec 30, 2017

METRON-1380: Create a typosquatting use-case (commit after METRON-1379, METRON-1377, METRON-1378) #882

Closed

METRON-939: Upgrade ElasticSearch and Kibana #840

Closed

nickwallen added 3 commits December 31, 2017 13:34

Added license header to README

e98b3ef

Merge remote-tracking branch 'apache/master' into METRON-1382

2a67e38

Updated to version 0.4.3

2b51128

nickwallen commented Jan 3, 2018

View reviewed changes

Updated the README to clarify usage

be412d8

Fixed the 'only shows first item in list' bug identified by @merrimanr.

2e001af

nickwallen added 3 commits January 3, 2018 21:06

Added a missing license header

9cc1de2

Minor cleanup

ceb55e4

Updated the interpreter settings to match what I have in the installa…

30654f3

…tion instructions in the README

nickwallen added 2 commits January 6, 2018 11:39

Added tests for isValueNull() behavior

4c1cd2e

Added implementation notes as requested by @ottobackwards

53c1c2d

nickwallen added 2 commits January 9, 2018 13:52

Added note about specific Zeppelin version support in REAEDME

3247851

Updated README instructions for adding Stellar interpreter

915fdc1

Changes to satisfy checkstyle and findbugs

f779bde

Error message then stack trace

f6cfe22

asfgit closed this in 2dd01b1 Jan 12, 2018

iraghumitra pushed a commit to iraghumitra/incubator-metron that referenced this pull request Feb 17, 2018

METRON-1382 Run Stellar in a Zeppelin Notebook (nickwallen) closes ap…

5aa048e

…ache#884

nickwallen deleted the METRON-1382 branch September 17, 2018 19:28


		[Apache Zeppelin](https://zeppelin.apache.org/) is a web-based notebook that enables data-driven, interactive data analytics and collaborative documents with SQL, Scala and more. This project provides a means to run the Stellar REPL directly within a Zeppelin Notebook.

		## Installation

METRON-1382 Run Stellar in a Zeppelin Notebook #884

METRON-1382 Run Stellar in a Zeppelin Notebook #884

Uh oh!

Conversation

nickwallen commented Dec 25, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Stellar in a Zeppelin Notebook

Changes

What does this do?

What does this not do?

Testing

Pull Request Checklist

Uh oh!

nickwallen left a comment

Choose a reason for hiding this comment

Uh oh!

nickwallen Dec 25, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

nickwallen left a comment

Choose a reason for hiding this comment

Uh oh!

nickwallen Jan 3, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ottobackwards commented Jan 3, 2018

Uh oh!

merrimanr commented Jan 3, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nickwallen commented Dec 25, 2017 •

edited

Loading

nickwallen Dec 25, 2017 •

edited

Loading

nickwallen Jan 3, 2018 •

edited

Loading

merrimanr commented Jan 3, 2018 •

edited

Loading

ottobackwards commented Jan 10, 2018 •

edited

Loading