Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/955
LGTM except minor comments.
---
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
Github user SachinJanani commented on the issue:
https://github.com/apache/zeppelin/pull/955
@jongyoul @corneadoug Done with the docs can you please have a look.
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/955
@SachinJanani Yes, it's one of the best place.
---
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 mwkang commented on the issue:
https://github.com/apache/zeppelin/pull/806
@corneadoug I fix whole issue. Can you check my code?
---
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
Github user jongyoul closed the pull request at:
https://github.com/apache/zeppelin/pull/981
---
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
GitHub user jongyoul opened a pull request:
https://github.com/apache/zeppelin/pull/985
ZEPPELIN-974 Merge TajoInterpreter into JdbcInterpreter
### What is this PR for?
Merging TajoInterpreter into JdbcInterpreter, and removing TajoInterprete
### What type of PR is
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/955
@corneadoug Thanks, and about review, I have been worried that you have
been pressed with all of review requests of front-side issues.
---
If your project is set up for it, you can reply to this
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/965
Tested
Merging if there is no more discussions
---
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
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/955
@jongyoul Tested, LGTM.
What about the doc? Should it be part of this PR or a separate one?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/955
@Leemoonsoo Yes, I just think there're too many requests for him, so I'm
asking you to have another candidate.
---
If your project is set up for it, you can reply to this email and have your
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/976
@bzz
I think this is a very serious problem.
In my personal opinion, first merge this PR, and improve Credentials
feature in future ( new pr ).
Problem situation, please
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/983
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, or if the
Ahyoung created ZEPPELIN-983:
Summary: org.apache.thrift.TApplicationException: Internal error
processing createInterpreter when running SparkR
Key: ZEPPELIN-983
URL:
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/955
@jongyoul We have some front-end expert in the community like @corneadoug.
But basically anyone in the community can participate review.
Thanks @SachinJanani for the contribution. It
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/980
I'm trying to combine 2.10 and 2.11 into one implementation in lresende#1
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/950
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 appear on GitHub as well. If your project does not have this feature
Github user cloverhearts closed the pull request at:
https://github.com/apache/zeppelin/pull/908
---
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 AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/984
[ZEPPELIN-982] Improve interpreter completion API
### What is this PR for?
When people implement a new interpreter, they extend
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/975
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/947
---
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
Ahyoung created ZEPPELIN-982:
Summary: Improve Interpreter completion API
Key: ZEPPELIN-982
URL: https://issues.apache.org/jira/browse/ZEPPELIN-982
Project: Zeppelin
Issue Type: Improvement
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/983
I think it's not changed only in github ui.
you can see that you can access to https://git.apache.org/zeppelin.git/ but
not to https://git.apache.org/incubator-zeppelin.git/
---
If your
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/983
The mirror is still pointing to
`git://git.apache.org/incubator-zeppelin.git`
Is it safe to change this info?
---
If your project is set up for it, you can reply to this email and have
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/973
@jasonxh I managed to do it, thanks
---
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
+1, how far along is support for Spark 2.0?
On Thursday, June 9, 2016, Trevor Grant wrote:
> +1 to release ASAP, Spark 2.0 should not be a blocker in anyway imho.
>
> Trevor Grant
> Data Scientist
> https://github.com/rawkintrevo
>
+1 to release ASAP, Spark 2.0 should not be a blocker in anyway imho.
Trevor Grant
Data Scientist
https://github.com/rawkintrevo
http://stackexchange.com/users/3002022/rawkintrevo
http://trevorgrant.org
*"Fortunate is he, who is able to know the causes of things." -Virgil*
On Thu, Jun 9, 2016
Matt created ZEPPELIN-981:
-
Summary: Sometimes error information is provided, sometimes not
provided.
Key: ZEPPELIN-981
URL: https://issues.apache.org/jira/browse/ZEPPELIN-981
Project: Zeppelin
Big +1 for 0.6.0 release.
@Prabhjyot Appreciate for letting us know, finally we have *Zeppelin
*repository
not incubator-zeppelin :)
2016년 6월 9일 (목) 오후 1:56, Khalid Huseynov 님이 작성:
> +1 on release.
>
> On Thu, Jun 9, 2016 at 11:13 AM, Prabhjyot Singh
+1 on release.
On Thu, Jun 9, 2016 at 11:13 AM, Prabhjyot Singh
wrote:
> +1 for release.
>
> And just noticed https://github.com/apache/zeppelin.
>
>
> On 9 June 2016 at 23:29, Alexander Bezzubov wrote:
>
> > +1 for cutting a release ASAP
> >
> > And
+1 for release.
And just noticed https://github.com/apache/zeppelin.
On 9 June 2016 at 23:29, Alexander Bezzubov wrote:
> +1 for cutting a release ASAP
>
> And thank you Mina for volunteering to manage the next release!
>
> On Thu, Jun 9, 2016, 18:21 moon soo Lee
+1 for cutting a release ASAP
And thank you Mina for volunteering to manage the next release!
On Thu, Jun 9, 2016, 18:21 moon soo Lee wrote:
> +1 on dedicated release manager (thanks for volunteering, Mina!)
>
> On Thu, Jun 9, 2016 at 7:41 AM Felix Cheung
Github user echarles commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/980
Sure, we can wait on #747 merge.
I see there is a
`spark/src/main/scala-2.11/org/apache/zeppelin/spark/SparkInterpreter.java`:
does this mean that there will be 2 separate
Github user Leemoonsoo commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/980
@echarles Thanks for the contribution.
How about we divide problem into
- scala 2.11 support
- spark 2.0 support
- reimplement spark interpreter in scala
Github user Leemoonsoo commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/747
Still working in progress, created a pullrequest to this branch,
https://github.com/lresende/incubator-zeppelin/pull/1 which is trying to merge
2.10 and 2.11 code using reflection
+1 on dedicated release manager (thanks for volunteering, Mina!)
On Thu, Jun 9, 2016 at 7:41 AM Felix Cheung
wrote:
> +1 on release branch+1 on dedicated release manager (thanks for
> volunteering, Mina!)
>
>
>
> _
> From:
GitHub user jongyoul reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/974
ZEPPELIN-614 Part 1. Merge PostgresqlInterpreter's sql completer into JDBC
Interpreter
### What is this PR for?
Supporting Sql completer into JDBC Interpreter which is merged by
Github user jongyoul closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/974
---
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/917
---
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 jongyoul opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/982
ZEPPELIN-934 Merge Phoenix interpreter into JDBC interpreter
### What is this PR for?
Removing Phoenix interpreter and adding example for using it through JDBC
### What
GitHub user jongyoul reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/974
ZEPPELIN-614 Part 1. Merge PostgresqlInterpreter's sql completer into JDBC
Interpreter
### What is this PR for?
Supporting Sql completer into JDBC Interpreter which is merged by
Github user jongyoul closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/974
---
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 jongyoul opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/981
ZEPPELIN-925 Part 2. Merge Hive Interpreter into JDBC
### What is this PR for?
Fixed some wrong documentation and settings. This is minor issue.
### What type of PR is it?
Github user astroshim commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/919
@corneadoug Thank you for your concern! I'm thinking to find right way how
to handle this issue.
---
If your project is set up for it, you can reply to this email and have your
reply
+1 on release branch+1 on dedicated release manager (thanks for volunteering,
Mina!)
_
From: mina lee
Sent: Wednesday, June 8, 2016 9:50 AM
Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
To:
GitHub user echarles opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/980
[ZEPPELIN-871] [WIP] spark 2.0 interpreter on scala 2.11
### What is this PR for?
Spark interpreter for spark version 2.0.0 and scala 2.11 (implemented in
Scala)
### What
Github user jongyoul commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/974
@bzz I updated license files. could you please check it again?
https://github.com/apache/incubator-zeppelin/pull/974/commits/99ce452b68c757c1959b9d4b7983f7d81000256e
---
If
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/943
---
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 astroshim opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/979
Alert message when trying to delete last paragraph.
### What is this PR for?
This PR is for giving proper information to users and blocking unnecessary
communication with zeppelin
Github user cloverhearts closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/908
---
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 cloverhearts reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/908
ZEPPELIN-598 ] Dynamic loading for Interpreter and API
### What is this PR for?
Use of external libraries that are included in the Roadmap,
The interpreter needs related
Github user bzz commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/966
Merging if there is no further discussion
---
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 sagarkulkarni3592 commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/971
@minahlee Thank you for that suggestion.
What if we push all the buttons to the new div present on next line, like :
![screen shot 2016-06-09 at 3 44 20
Github user bzz commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/978
@ravicodder thank you for improvement!
\cc @felizbear as original author of search frontend for a review
---
If your project is set up for it, you can reply to this email and have
GitHub user ravicodder opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/978
[ZEPPELIN-869] Search notebook to handle empty result.
### What is this PR for?
Search notebook to handle empty result.
### What type of PR is it?
Bug Fix
###
Github user bzz commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/974
Great work @jongyoul !
Looks good to me except minor things listed above
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
shruti created ZEPPELIN-978:
---
Summary: grunt build fails
Key: ZEPPELIN-978
URL: https://issues.apache.org/jira/browse/ZEPPELIN-978
Project: Zeppelin
Issue Type: Bug
Environment: linux
Github user bzz commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/966
Looks great to me, let's merge as a short term solution.
And yes, as @felixcheung mentioned - in a mid\long term, it would be great
for interpreter to encapsulate this knowledge!
Github user bzz commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/977
Looks great to me, @rerngvit thank you for contribution!
Have update JIRA issues assignment.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user corneadoug commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/947
No problem of rendering with the new "theme"
Merging if there is no more discussions
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user corneadoug commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/973
@jasonxh I can't find you somehow on the JIRA user id.
Could you give it to me?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/973
---
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 jongyoul commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/955
@Leemoonsoo Who's proper reviewer for UI part?
---
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
Github user corneadoug commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/975
Merging if there is 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. If your project does not have
Github user jongyoul commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/977
I've tested it and worked well. LGTM. Merging if there's no more
discussion. @rerngvit Could you please your jira id? I cannot assign you as a
contributor
---
If your project is set
Github user zuny25 closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/817
---
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 zuny25 reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/817
[ZEPPELIN-792]Misspelt words and Wrong method parameters
### What is this PR for?
Fix misspelt words and wrong method parameter on zeppelin-interpreter
Github user cloverhearts commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/908
Merge master branch into 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 project does not have this
Github user SachinJanani commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/955
@jongyoul Yes you are right.But this changes will allow user to connect to
existing remote process instead of zeppelin running the interpreter.I think we
should create a separate
Github user corneadoug closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/975
---
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 corneadoug commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/904
@mwkang It's fine, we can always reopen it if necessary. Just wanted
@Leemoonsoo go to close it since he was the one to report it
---
If your project is set up for it, you can reply
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/946
---
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 mwkang commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/904
Oh.. I closed JIRA issue.
I am so sorry that I act at my discretion.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user corneadoug commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/904
@Leemoonsoo Can we close this JIRA issue then?
https://issues.apache.org/jira/browse/ZEPPELIN-835
---
If your project is set up for it, you can reply to this email and have your
Github user jongyoul commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/955
@SachinJanani Thanks for sharing. I also think we should consider running
Zeppelin's interpreters in a different machine. This would be a starting point
to do this.
---
If your
Github user mwkang commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/904
Related PR: https://github.com/apache/incubator-zeppelin/pull/860
Related Issue: https://issues.apache.org/jira/browse/ZEPPELIN-828
---
If your project is set up for it, you can reply
Github user mwkang closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/904
---
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 mwkang commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/904
While I rebase this PR, I found this issue was been resolved
[AuthenticationInfo in master].
So I closed PR.
[AuthenticationInfo in master]:
Github user SachinJanani commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/955
@jongyoul There can be scenarios where user is starting RemoteInterpreter
embedded in his service by calling
`RemoteInterpreterServer server = new RemoteInterpreterServer(port)
Github user jongyoul commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/955
That failure is related to
https://issues.apache.org/jira/browse/ZEPPELIN-878, but I have a question. What
kind of procedure do you do while you run Zeppelin? Generally, when you stop
79 matches
Mail list logo