+1 for me. I think we can use a wiki for maintaining third party
interpreters.
On Thu, May 14, 2015 at 10:23 AM, Alexander Bezzubov wrote:
> Hi,
>
> Damien, thanks for bringing the discussion in, and thank everybody for
> opinions: it is indeed very timely as we see more and more submodules with
Hi,
Damien, thanks for bringing the discussion in, and thank everybody for
opinions: it is indeed very timely as we see more and more submodules with
interpreters implementations and having a consistent strategy on how to
deal with them is very important now.
What I see right now is:
- *number o
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/40#issuecomment-101868074
Good, now we know another error case :)
I did a typo, it was indeed -DskipTests
On Thu, May 14, 2015 at 3:35 AM, liushiqi9 wrote:
> I
Jonathan Kelly created ZEPPELIN-79:
--
Summary: Zeppelin does not kill some interpreters when server is
stopped
Key: ZEPPELIN-79
URL: https://issues.apache.org/jira/browse/ZEPPELIN-79
Project: Zeppelin
liushiqi9 created ZEPPELIN-78:
-
Summary: How to enable env configurations.
Key: ZEPPELIN-78
URL: https://issues.apache.org/jira/browse/ZEPPELIN-78
Project: Zeppelin
Issue Type: Bug
Comp
Github user liushiqi9 commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/40#issuecomment-101770657
I solve this problem.
This is cause by install both maven and maven2 in ubuntu.
As long as I remove maven 2 and upgrade maven to 3.1.1 I build it
Github user liushiqi9 commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/40#issuecomment-101749018
Hi,
I tried your suggestion.
If I use mvn clean package -skipTests same problem remains.
If i use mvn clean package -DskipTests I got
Embedde
Consider this a huge -1 from me
On Wed, May 13, 2015 at 7:39 AM James Carman
wrote:
> Why not invite the contributors to be committers? You don't want to leave
> the contributors out in the cold. Likewise, the interpreters are less
> likely to attract new contributions outside the ASF. You wan
​Thanks for the efforts on the classpath. However, as stated above, the
classpath required to execute Zeppelin and the classpaths required of the
individual interpreters have already diverged. Since it is the interpreters
that will have the most dynamic development, I should actually suggest
separa
+1 from me.
One small downside is, when there're Interpreter API changes, it'll be much
difficult to make all interpreters update.
On Wed, May 13, 2015 at 5:18 PM Corneau Damien
wrote:
> Hi,
>
> I just want to open a discussion about Zeppelin Interpreters.
>
> Currently we are accepting interpr
Why not invite the contributors to be committers? You don't want to leave
the contributors out in the cold. Likewise, the interpreters are less
likely to attract new contributions outside the ASF. You want to build a
community around the code. Vote them in!
On Wed, May 13, 2015 at 4:18 AM Corn
Hi,
I just want to open a discussion about Zeppelin Interpreters.
Currently we are accepting interpreters and merging them to the Zeppelin
Branch when people have some done.
I see more and more issues/post on the mailing list regarding some problems
with interpreters, while it is a big part of Z
Github user khalidhuseynov commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/73#issuecomment-101554581
Triggering CI Build
---
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 do
Github user khalidhuseynov closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/73
---
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 khalidhuseynov reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/73
Tajo jdbc thrift interpreters
This is for decoupling Tajo-jdbc and Tajo-thrift interpreters.
TODO
- [x] Rename Tajo interpreter explicitly into tajo-jdbc
- [x] A
Github user RPCMoritz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/65#issuecomment-101553576
While this was a decent effort (it actually made my classpath-related error
almost readable, where previously it was three screens worth of text), there is
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/67
---
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
17 matches
Mail list logo
