Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/835#issuecomment-222427837
:shipit:
---
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 featu
Github user agura commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/916#issuecomment-222477037
Guys, can anybody merge this PR into master branch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
Github user mwkang commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/806#issuecomment-222479738
- [ ] When you create a new notebook, the interpreter is listed as: %...
Any way to get the default interpreter from back-end and insert it instead?
- [ ]
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT.
The report for your podling will form a
DOAN DuyHai created ZEPPELIN-901:
Summary: Cassandra Interpreter V3
Key: ZEPPELIN-901
URL: https://issues.apache.org/jira/browse/ZEPPELIN-901
Project: Zeppelin
Issue Type: Improvement
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/916#issuecomment-222491988
@agura Hi, one of CI test is failed. Could you please check it?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user agura commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/916#issuecomment-222492624
@jongyoul How to rerun tests?
---
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 pull request:
https://github.com/apache/incubator-zeppelin/pull/916#issuecomment-222493080
@agura Close and re-open this PR
---
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 pro
GitHub user agura reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/916
[ZEPPELIN-881] Apache Ignite version updated to 1.6
### What is this PR for?
Apache Ignite 1.6 contains JDBC driver improvements that affect Zeppelin
Ignite interpreter user experien
Github user agura closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/916
---
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 feat
Eric Charles created ZEPPELIN-902:
-
Summary: Build can break with pyspark profile due to not
accessible path
Key: ZEPPELIN-902
URL: https://issues.apache.org/jira/browse/ZEPPELIN-902
Project: Zeppelin
GitHub user echarles opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/930
Make path for .spark-dist folder always accessible
### What is this PR for?
Current Path for .spark-dist is outside the reactor, which can breaks build.
[INFO]
-
Github user mwkang commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/806#issuecomment-222498405
@corneadoug
Hello, I have a question.
Only after running a query, the cursor go to line end in new paragraph.
If It is added manually, the cursor d
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/916#issuecomment-222504357
@Leemoonsoo Could you please check that failure due to flaky test?
---
If your project is set up for it, you can reply to this email and have your
reply app
Eric Charles created ZEPPELIN-903:
-
Summary: Jersey2 instead of CXF for better JSON REST
Key: ZEPPELIN-903
URL: https://issues.apache.org/jira/browse/ZEPPELIN-903
Project: Zeppelin
Issue Type
Eric Charles created ZEPPELIN-904:
-
Summary: commons-exec should be in compile scope of zeppelin-server
Key: ZEPPELIN-904
URL: https://issues.apache.org/jira/browse/ZEPPELIN-904
Project: Zeppelin
GitHub user echarles opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/931
Remove unnedeed commons-exec declaration in scope test [ZEPPELIN-904]
### What is this PR for?
zeppelin-server should simply rely on transitive commons-exec from
zeppelin-interprete
GitHub user echarles opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/932
Replace CXF with Jersey2 [ZEPPELIN-903]
### What is this PR for?
Use jersey2 instead of CXF to manage JSON REST requests and responses.
Jersey2 can better manage the JSON bodies
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/925
---
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 fea
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/926
---
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 fea
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/927
---
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 fea
Github user hriviere commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/869#issuecomment-222549087
I made two commits :
* One to add a new line in python.md (cf. AhyoungRyu review)
* One to revert LICENSE file and to move py4j license from lic
Hi to all,
i'm developing an intepreter for apache zeppelin (EclairJS:
https://github.com/conker84/incubator-zeppelin/tree/master/eclairjs), and i
have some questions.
1) How can i debug Zeppelin via eclipse in order to get all the intepreters?
2) When i try to execute a sample script like this:
%
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/930#issuecomment-222575332
Hi, thanks for taking care of the build stability!
`.spark-dist` was introduced as our CI build cache dir, and is used in
[multiple
places](https://gith
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/923#issuecomment-222576247
Thanks, looks good to me.
\cc @Leemoonsoo @jongyoul @felixcheung for a final review
---
If your project is set up for it, you can reply to this email and hav
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/924#issuecomment-222577126
Thank you for improving Scala style!
Generally, such big changes that touch multiple subsystems (spark,
cassandra, angular, etc) are VERY hard to review
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/916#issuecomment-222577722
@jongyoul first thing to do is to check JIRA `flaky-test` label and see if
there is an existing issue for this failure.
The CI failure is not related to
Github user AhyoungRyu commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/869#issuecomment-222577784
@hriviere I checked and it looks good ð
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/869#issuecomment-222577855
@hriviere looks great to me, thank you for taking care!
Going to merge it, if there is no more discussion.
---
If your project is set up for it, you can
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/929#issuecomment-222578009
Looks good to me
\cc @felizbear @corneadoug for double-check
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user felizbear commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/929#issuecomment-222578766
looks good
---
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 th
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/918#issuecomment-222578818
@vgmartinez thank you for explaining the use case, it makes perfect sense
and is not covered by the case I was referring to. May it's worth putting it in
JIRA\PR
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/929#issuecomment-222578940
As it's marked as HOTFIX (urgent), I will proceed merging it if there is no
further discussion
---
If your project is set up for it, you can reply to this email
Github user cloverhearts commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/921#issuecomment-222579048
@astroshim Thank you for feedback.
I'll check it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/928#issuecomment-222579453
@rawkintrevo thank you for contribution!
In my experience, if CI is failing and no reason is investigated\posted on
PR by the author - it takes much long
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/923#issuecomment-222579535
I agree to change the default version of Spark. LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/860#issuecomment-222579904
Let me look into that again and get back to you
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/916
---
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 fea
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/931#issuecomment-222580712
LGTM. Merging if there's no more discussion
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user cloverhearts commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/931#issuecomment-222581135
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
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/835
---
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 fea
Thanks for sharing, Anish!
You can also use a public service of Zeppelin notebooks Viewer [0] to
showcase your work as [1].
As a feedback over notebook structure - I think it's a great start, but did
you know that paragraph width can be adjusted though UI to accommodate the
reader's flow? Sometim
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/931#issuecomment-222581686
Looks great to me
---
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 t
Kevin (Sangwoo) Kim created ZEPPELIN-905:
Summary: Fail to import notebook with error result
Key: ZEPPELIN-905
URL: https://issues.apache.org/jira/browse/ZEPPELIN-905
Project: Zeppelin
Jongyoul Lee created ZEPPELIN-906:
-
Summary: Apply new mechanism to AlluxioInterpreter
Key: ZEPPELIN-906
URL: https://issues.apache.org/jira/browse/ZEPPELIN-906
Project: Zeppelin
Issue Type:
GitHub user swkimme opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/933
[ZEPPELIN-905] fix failed notebook import bug
### What is this PR for?
When notebook has a result with Exceptions, it always fail to import. This
PR fix it.
### What type of
Jongyoul Lee created ZEPPELIN-907:
-
Summary: Apply new mechanism to AngularInterpreter
Key: ZEPPELIN-907
URL: https://issues.apache.org/jira/browse/ZEPPELIN-907
Project: Zeppelin
Issue Type:
Jongyoul Lee created ZEPPELIN-908:
-
Summary: Apply new mechanism to CassandraInterpreter
Key: ZEPPELIN-908
URL: https://issues.apache.org/jira/browse/ZEPPELIN-908
Project: Zeppelin
Issue Type
Jongyoul Lee created ZEPPELIN-909:
-
Summary: Apply new mechanism to ElasticsearchInterpreter
Key: ZEPPELIN-909
URL: https://issues.apache.org/jira/browse/ZEPPELIN-909
Project: Zeppelin
Issue
Jongyoul Lee created ZEPPELIN-910:
-
Summary: Apply new mechanism to HDFSFileInterpreter
Key: ZEPPELIN-910
URL: https://issues.apache.org/jira/browse/ZEPPELIN-910
Project: Zeppelin
Issue Type:
Jongyoul Lee created ZEPPELIN-911:
-
Summary: Apply new mechanism to FlinkInterpreter
Key: ZEPPELIN-911
URL: https://issues.apache.org/jira/browse/ZEPPELIN-911
Project: Zeppelin
Issue Type: Su
Jongyoul Lee created ZEPPELIN-912:
-
Summary: Apply new mechanism to GeodeOqlInterpreter
Key: ZEPPELIN-912
URL: https://issues.apache.org/jira/browse/ZEPPELIN-912
Project: Zeppelin
Issue Type:
Jongyoul Lee created ZEPPELIN-913:
-
Summary: Apply new mechanism to HbaseInterpreter
Key: ZEPPELIN-913
URL: https://issues.apache.org/jira/browse/ZEPPELIN-913
Project: Zeppelin
Issue Type: Su
Jongyoul Lee created ZEPPELIN-914:
-
Summary: Apply new mechanism to IgniteInterpreter and
IgniteSqlInterpreter
Key: ZEPPELIN-914
URL: https://issues.apache.org/jira/browse/ZEPPELIN-914
Project: Zeppel
Jongyoul Lee created ZEPPELIN-915:
-
Summary: Apply new mechanism to JDBCInterpreter
Key: ZEPPELIN-915
URL: https://issues.apache.org/jira/browse/ZEPPELIN-915
Project: Zeppelin
Issue Type: Sub
Jongyoul Lee created ZEPPELIN-916:
-
Summary: Apply new mechanism to KylinInterpreter
Key: ZEPPELIN-916
URL: https://issues.apache.org/jira/browse/ZEPPELIN-916
Project: Zeppelin
Issue Type: Su
Jongyoul Lee created ZEPPELIN-917:
-
Summary: Apply new mechanism to LensInterpreter
Key: ZEPPELIN-917
URL: https://issues.apache.org/jira/browse/ZEPPELIN-917
Project: Zeppelin
Issue Type: Sub
Jongyoul Lee created ZEPPELIN-918:
-
Summary: Apply new mechanism to Livy*Interpreter
Key: ZEPPELIN-918
URL: https://issues.apache.org/jira/browse/ZEPPELIN-918
Project: Zeppelin
Issue Type: Su
Jongyoul Lee created ZEPPELIN-919:
-
Summary: Apply new mechanism to Markdown
Key: ZEPPELIN-919
URL: https://issues.apache.org/jira/browse/ZEPPELIN-919
Project: Zeppelin
Issue Type: Sub-task
Jongyoul Lee created ZEPPELIN-920:
-
Summary: Apply new mechanism to PostgreSqlInterpreter
Key: ZEPPELIN-920
URL: https://issues.apache.org/jira/browse/ZEPPELIN-920
Project: Zeppelin
Issue Typ
Jongyoul Lee created ZEPPELIN-921:
-
Summary: Apply new mechanism to KnitR and RRepl
Key: ZEPPELIN-921
URL: https://issues.apache.org/jira/browse/ZEPPELIN-921
Project: Zeppelin
Issue Type: Sub
Jongyoul Lee created ZEPPELIN-922:
-
Summary: Apply new mechanism to ScaldingInterpreter
Key: ZEPPELIN-922
URL: https://issues.apache.org/jira/browse/ZEPPELIN-922
Project: Zeppelin
Issue Type:
Jongyoul Lee created ZEPPELIN-923:
-
Summary: Apply new mechanism to ShellInterpreter
Key: ZEPPELIN-923
URL: https://issues.apache.org/jira/browse/ZEPPELIN-923
Project: Zeppelin
Issue Type: Su
Jongyoul Lee created ZEPPELIN-924:
-
Summary: Apply new mechanism to TajoInterpreter
Key: ZEPPELIN-924
URL: https://issues.apache.org/jira/browse/ZEPPELIN-924
Project: Zeppelin
Issue Type: Sub
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/918#issuecomment-222587470
@vgmartinez I think move email facilities from `Notebook.java` to new
class, like @bzz mentioned, would be the first step to generalize it. Doesn't
need t
Hi zeppelin users/developers,
Are any of you going to attend the spark summit in June?
Zeppelin is an awesome project, and we had a great experience using
Zeppelin and working with the community this year. I would like to meet
with anyone who is interested in Zeppelin in person and chat about
int
GitHub user jongyoul opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/934
[DOC] Added the link of Apache's Jira for beginner
### What is this PR for?
Added documentation for new contributors
### What type of PR is it?
[Documentation]
Jongyoul Lee created ZEPPELIN-925:
-
Summary: Merge HiveInterpreter into JDBCInterpreter
Key: ZEPPELIN-925
URL: https://issues.apache.org/jira/browse/ZEPPELIN-925
Project: Zeppelin
Issue Type:
Hi all,
Seems like this project is going to be taken care of. I submitted two
proposals for gsoc and the other proposal got accepted.
However I'm more than happy to contribute for this project.
Please let me know if there's anything I can do.
Thanks
Minidika
On Mar 25, 2016 10:53 AM, "Alexande
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/923#issuecomment-222589969
Thanks @shijinkui for quick update.
Looks good to me!
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/934#issuecomment-222590123
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 fe
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/933#issuecomment-222590736
Looks good to me.
How about adding an unittest for it in
[NotebookTest.java](https://github.com/apache/incubator-zeppelin/blob/18fa33a9b1127efd7b059804
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/843#issuecomment-222591848
@Leemoonsoo @felixcheung Ping.
---
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 proje
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/928#issuecomment-222592450
Thanks @rawkintrevo for the contribution.
I think mahout support can be
a) integrated into SparkInterpreter (like this patch)
b) pro
Github user swkimme commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/933#issuecomment-222594140
@Leemoonsoo
I've added some 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 yo
Polina Marasanova created ZEPPELIN-926:
--
Summary: Getting 'File name too long' error when running scala
code in Zeppelin
Key: ZEPPELIN-926
URL: https://issues.apache.org/jira/browse/ZEPPELIN-926
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/935
[ZEPPELIN-926] Set maxClassfileName to 128
### What is this PR for?
set scala Settings.numClassFileSetting to 128 to prevent "Getting 'File
name too long'" error.
See https://
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/934#issuecomment-222600583
I'll merge it in a minute.
---
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 d
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/934
---
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 fea
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/929#issuecomment-222601917
Tested and looks good to me
---
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 projec
Hi devs,
I've updated a jira query link into CONTRIBUTING.md. This link will help
you start to contribute Zeppelin easily. Please check the link below:
https://github.com/apache/incubator-zeppelin/blob/master/CONTRIBUTING.md#where-to-start
Or you can reach it directly:
https://issues.apache.org
GitHub user jongyoul opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/936
[MINOR] fixed a logic to find issue number from title
### What is this PR for?
Changed the regex to find a issue number from title
### What type of PR is it?
[Bug Fix]
82 matches
Mail list logo
