Github user astroshim commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/959
LGTM
---
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,
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/958
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/931
---
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
Github user minahlee commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/959
Same test failure is already reported by @bzz in
https://issues.apache.org/jira/browse/ZEPPELIN-942
---
If your project is set up for it, you can reply to this email and have your
GitHub user cloverhearts reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/921
Zeppelin-531 ] Job management
### What is this PR for?
Zeppelin job management.
Zeppelin job monitoring and control page for Notebooks and Paragraphs.
You can
GitHub user cloverhearts opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/960
ZEPPELIN-953 ] Jquery.floatThead delete the information from the license
file.
### What is this PR for?
is no longer used.
But the license document contains the
Github user cloverhearts commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/921
![zjobmaneger](https://cloud.githubusercontent.com/assets/10525473/15797104/64748768-2a48-11e6-9595-69126f6dc998.gif)
1. Support Live change - notebook information (cron,
Github user cloverhearts commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/959
LGTM
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/959
LGTM
---
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,
Github user Leemoonsoo commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/955
Thanks @SachinJanani for the contribution.
Ideally configure host and port can be moved from Property to
GitHub user minahlee opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/959
[ZEPPELIN-951] Update cron expression link and fix broken cron container
style
### What is this PR for?
Update cron expression link and fix broken cron container style
###
Mina Lee created ZEPPELIN-952:
-
Summary: Update document style to be more readable
Key: ZEPPELIN-952
URL: https://issues.apache.org/jira/browse/ZEPPELIN-952
Project: Zeppelin
Issue Type:
Mina Lee created ZEPPELIN-951:
-
Summary: Cron expression link is outdated and layout is broken
Key: ZEPPELIN-951
URL: https://issues.apache.org/jira/browse/ZEPPELIN-951
Project: Zeppelin
Issue
Github user Leemoonsoo commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/951
Cool. Font size of "Connected" text seems changed. Is it intended?
Before
Github user rawkintrevo commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/928
my thought is only support spark. If you want to use pyspark/spark/ blah -
use the spark interpreter.
We'll only support additional langs as Mahout introduces interpreters for
Github user prasadwagle commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/917
@felixcheung @lresende I agree. I wanted to see the build errors before I
started a discussion on the dev list. In the previous build, one check didn't
complete, many failed with
Github user lresende commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/917
Agreed @felixcheung , at least we should have a discussion on the dev list
if we plan to have some changes like this.
---
If your project is set up for it, you can reply to this email
Github user felixcheung commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/917
Hmm... I'm not sure sure we should move to jdk8 completely by default -
there are some interpreters that only runs with jdk7 last time we checked.
Similarly for Scala 2.1, but that's
Github user felixcheung commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/928
Then perhaps it should be a separate one (eg. %mahout)
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/940
Thanks @cloverhearts @felixcheung @bzz taking a look.
Merge if there're no more discussions
---
If your project is set up for it, you can reply to this email and have your
reply
Github user felixcheung commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/957
WIP?
---
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
Github user rawkintrevo commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/928
@Leemoonsoo definitely the latter... *sigh*. Beginning work on a refactor
(actually already begun bc I had reached the same conclusion).
---
If your project is set up for it, you
Github user felixcheung commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/940
Agreed. I think the model used in Spark is that if an API is:
- new
- expecting (significant) discussions/changes in this or the next minor
release
Then it should be
Github user Leemoonsoo commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/928
I think whether creating mahout interpreter or not will be depends on
expectation that how user uses mahout.
If usecase is let spark user uses mahout during their work along
Github user ralphge closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/954
---
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
GitHub user ralphge reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/954
[ZEPPELIN-915] New registration mechanism applied to JDBCInterpreter
### What is this PR for?
This PR applies the new interpreter registration mechanism to the
JDBCInterpreter.
GitHub user ralphge reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/954
[ZEPPELIN-915] New registration mechanism applied to JDBCInterpreter
### What is this PR for?
This PR applies the new interpreter registration mechanism to the
JDBCInterpreter.
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/958
Tried it 4 different times
- https://travis-ci.org/apache/incubator-zeppelin/builds/135110386
- https://travis-ci.org/apache/incubator-zeppelin/builds/135119542
-
Github user bbuild11 commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/868
I saw that the config file zeppelin-env.sh contents are different than
previous versions. It uses âsetâ instead of âexportâ. So, I tried to
use the old config file from Zeppelin
GitHub user prabhjyotsingh opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/958
[Hot Fix] Fix flaky ZeppelinIT build
### What is this PR for?
Master is failing for ZeppelinIT at
testSparkInterpreterDependencyLoading:243, as the previous line's
Prabhjyot Singh created ZEPPELIN-950:
Summary: Fix flaky ZeppelinIT build
Key: ZEPPELIN-950
URL: https://issues.apache.org/jira/browse/ZEPPELIN-950
Project: Zeppelin
Issue Type: Bug
GitHub user jongyoul opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/957
ZEPPELIN-900 Show interpreter logs in front side's result area while
processing
### What is this PR for?
Showing logs while running paragraph. This is POC level now.
###
Github user prasadwagle commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/917
@felixcheung yes, it should be. I have moved the classes to
org.apache.zeppelin.scalding but we need
[this](https://github.com/twitter/scalding/pull/1563) scalding change. The
Github user AhyoungRyu commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/956
@jongyoul I see. Okay Thanks for letting me know :)
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/956
@AhyoungRyu One looks irrelevant and another is about rat plugin. you need
to exclude interpreter-setting.json in a rat plugin.
---
If your project is set up for it, you can reply to
Github user felixcheung commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/868
Can you check the log file?
---
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
Github user bbuild11 commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/868
Hi all,
I downloaded the latest master clone from github and built it using this
command:
mvn clean package -DskipTests -Pspark-1.6 -Phadoop-2.6
Hello,
Minudika, there are three different 'big tracks of integration':
1. Integrate Beam's spark runner as a spark package, ideally with a Beam
spark SDK.
This is what I am starting to do right now.
2. Integrate the core Beam Java SDK and all the runners. This is a BIG task:
As you said we
Github user doanduyhai closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/950
---
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
GitHub user SachinJanani opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/955
[ZEPPELIN-940] Allow zeppelin server to connect to already executing Remote
Interpreter
### What is this PR for?
Currenlty zeppelin server starts interpreter on localhost and
Github user doanduyhai closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/746
---
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
GitHub user doanduyhai reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/746
[ZEPPELIN-699] Add new synchronous paragraph run REST API
### What is this PR for?
Right now, when calling the REST API
`http://:/api/notebook/job//` Zeppelin always
returns
Hi all,
Are you gonna use JavaREPL[1] for this implementation?
[1] https://github.com/albertlatacz/java-repl
On Fri, Jun 3, 2016 at 3:23 PM, Felix Cheung
wrote:
> Absolutely! We would welcome your contribution for this!
>
>
>
>
Github user doanduyhai commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/746
@felixcheung Done, I've added 2 new screen captures of the API
documentation update
---
If your project is set up for it, you can reply to this email and have your
reply appear on
44 matches
Mail list logo