Hi Jongyoul,
Try build again after this,
rm -rf zeppelin-web/bower_components/
Best,
moon
On Wed, Jan 21, 2015 at 3:30 PM, Jongyoul Lee wrote:
> Hi, Moon,
>
> I've tried to compile code on that branch. It, However, occurs error like:
>
> [INFO] bower angular#~1.x ca
Hi, Moon,
I've tried to compile code on that branch. It, However, occurs error like:
[INFO] bower angular#~1.x cached git://
github.com/angular/bower-angular.git#1.3.10
[INFO] bower angular#~1.x validate 1.3.10 against
git://github.com/angular/bow
Btw, any of you guys plan to be at FOSDEM in two weeks?
Thanks,
Roman.
On Mon, Jan 19, 2015 at 10:54 PM, Konstantin Boudnik wrote:
> Good idea!
>
> Be aware that CFP is closing in about two weeks.
>
> Cos
>
> On Tue, Jan 20, 2015 at 12:03PM, Alex B. wrote:
>> Hey guys,
>>
>> what do you think if
Hi Jongyoul,
I just pushed an branch for Spark 1.2
https://github.com/NFLabs/zeppelin/pull/294
This is still in development and not fully tested, but as you can see the
screenshots, the default functions are working.
If you're interested, please test this branch and give some feedback.
Hope this
There are couple of problems with Spark 1.2 support, some of them will be
solved by recent Spark 1.2.1 release soon (unpublished artifacts) and
others (classloading issues) hopefully with remote process interpreter I'm
working on right now.
Mesos might be an option, although I do not have much exp
I guess supporting Spark 1.2 is one of the most important issue today and
probably will be resolved soon,
Until then, you might try Zeppelin in local mode with local data for try
and learn!
Maybe @moon will comment more for Spark 1.2 support.
And I'm running standalone spark cluster and have no
Hi Kevin,
Thanks for quick reply. I've checked maven central and figured it out as a
spark issue. Unfortunately, I have 1.2.0 cluster only. And have you tested
zeppelin on a mesos cluster?
Thanks,
Jongyoul
On Wed, Jan 21, 2015 at 10:52 AM, Kevin (Sangwoo) Kim
wrote:
> Hi Jongyoul,
> Great to s
Hi Jongyoul,
Great to see you in mailing list!
Sadly, for now Zeppelin not work with Spark 1.2.
https://github.com/NFLabs/zeppelin/issues/260
Please try with Spark 1.1.1 version.
Regards,
Kevin (Sangwoo)
On Wed Jan 21 2015 at 10:46:35 AM Jongyoul Lee wrote:
> Hi dev,
>
> I'm new to use Zeppel
Hi dev,
I'm new to use Zeppelin. I've failed while building from source. The
following is error messages.
[ERROR] Failed to execute goal on project zeppelin-spark: Could not resolve
dependencies for project com.nflabs.zeppelin:zeppelin-spark:jar:0.4.0:
Failure to find org.apache.spark:spark-repl_
Current plan on Subj is to do it as a last step of whole migration process:
right after source code is moved to ASF Git and Github mirror is created.
FYI: sign-up is disabled now on old project JIRA
https://zeppelin-project.atlassian.net and as soon as issues are migrated I
think we will add a not
If all contributions to Zeppelin legally belongs to NFLabs I think we
could just attach the full history donation.
- Henry
On Tue, Jan 20, 2015 at 3:53 AM, Alex wrote:
> I have a question to contributors: do we want full Git history to be donated
> to ASF and migrated to ASF git or only the lat
I have a question to contributors: do we want full Git history to be donated to
ASF and migrated to ASF git or only the latest state would be enough I.e HEAD
of the master?
Therefor another question is to mentors: in case of full history donation,
would it be enough to just mention full history
12 matches
Mail list logo
