Github user avnerl commented on the issue:
https://github.com/apache/zeppelin/pull/3258
> also we could upgrade beam interpreter to "require" beam 2.3 also (so it
does build with scala-2.11)
this's what i did in:
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/3258
also we could upgrade beam interpreter to "require" beam 2.3 also (so it
does build with scala-2.11)
---
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/3258
what about we don't build beam and scio if scala-2.11?
---
And for testing Z as well, we don't have to build Spark Interpreter again
for integration tests. and even, we don't have to build zeppelin server and
web for integration test for spark. We just use components built. I believe
it makes our CI as well faster.
On Wed, Dec 12, 2018 at 3:29 PM
Yes, right. BTW, I think we need to make dependencies clearly between
zeppelin-server and interpreters, and even among interpreters. Some
versions properties are used in zeppelin-server and interpreters, but no
one has any clear view for them. So I thought it would be a change when we
divide
Hi Jongyoul,
Thanks for bring this up. I don't understand how different repo will help
here, but I thought about moving interpreters out of zeppelin for a long
time, but don't have bandwidth for it. The release cycle of zeppelin core
component (zeppelin-zengine, zeppelin-server) should not block
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/3259
We had two different CI. one is for appveyor which actually doesn't test
anything. another one is travis. Could you please check your travis? I don't
think you set the CI correctly. Please see
Mark Bidewell created ZEPPELIN-3904:
---
Summary: R Interpreter does not work for All Spark Versions
Key: ZEPPELIN-3904
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3904
Project: Zeppelin
Github user fred521 commented on the issue:
https://github.com/apache/zeppelin/pull/3259
here is the link
https://ci.appveyor.com/project/ApacheSoftwareFoundation/zeppelin/builds/20912238
On Tue, Dec 11, 2018 at 6:37 PM Fred wrote:
> Yes, It passes all the
Hi, dev and committers,
Currently, I'm seeing the repositories of another apache projects. They
have some several repositories with different purposes. I'd like to suggest
you that we divide repositories between zeppelin-server and others.
This will help you develop zeppelin-server without
Github user fred521 commented on the issue:
https://github.com/apache/zeppelin/pull/3259
Yes, It passes all the tests
On Tue, Dec 11, 2018 at 6:31 PM Jongyoul Lee
wrote:
> Could you please check your CI? I think this should pass all of our tests
>
> â
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/3259
Could you please check your CI? I think this should pass all of our tests
---
Github user HyukjinKwon commented on the issue:
https://github.com/apache/zeppelin/pull/3253
I'm not aware of release plan in Zeppelin since I'm just one of
contributors. For the current status, the Spark should be downgraded as far as
I can tell.
---
Hi, devs,
I'd like to make a consensus to move our repository from git-wip to gitbox.
Please give your opinions with replies from this email.
Thanks in advance,
JL
--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net
Github user HyukjinKwon commented on the issue:
https://github.com/apache/zeppelin/pull/3253
Spark 2.4 support was added at
https://github.com/apache/zeppelin/pull/3206, which exactly addresses the issue
you faced. This will be available in new release of Zeppelin.
---
Github user GezimSejdiu commented on the issue:
https://github.com/apache/zeppelin/pull/3253
Hi @HyukjinKwon ,
any news about this PR? Does it support Spark 2.4.0 (Scala 2.11.x)
interpreter already? I just created a new branch which builds a [customized
zeppelin
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/3250
---
Yes that’s all it takes to migrate.
(And committers to setup gitbox link)
Any more thoughts from the community?
From: Jongyoul Lee
Sent: Tuesday, December 11, 2018 1:38 AM
To: dev
Subject: Re: [DISCUSS] Fwd: [NOTICE] Mandatory relocation of Apache git
Github user avnerl commented on the issue:
https://github.com/apache/zeppelin/pull/3258
do you think it's a good idea to tamper with beam version in
`dev/change_scala_version.sh` too?
build will not pass if you do not use the `-Pscala-2.11` profile explicitly
---
Github user avnerl commented on the issue:
https://github.com/apache/zeppelin/pull/3258
you are right. it didn't make sense. the reason i did this is because i
wanted the build to pass. i remove the beam interpreter afterwards as i dint
need it.
last 2 commits is reverting back
We could create a ticket for the infra only, correct?
On Mon, Dec 10, 2018 at 12:45 PM Jeff Zhang wrote:
> Definitely +1 for earlier, anyone volunteer for this ?
>
>
> Jongyoul Lee 于2018年12月10日周一 上午11:34写道：
>
> > I don't think we have any special reason not to move there.
> >
> > +1 for
Github user Savalek commented on the issue:
https://github.com/apache/zeppelin/pull/3235
@felixcheung, I'm trying to fix the tests but I can't even run `npm run
test` in `zeppelin-web` because the file `webpack.config.js` made for version
`webpack 1` but the current version `4`.
22 matches
Mail list logo
