Eric,
There are elements in 702 that I think would be great to see in the final merge!
Great to hear your open to Plan B.
Jeff
On 3/7/16, 11:20 PM, "Eric Charles" wrote:
>Small precisions on #702:
>
>(snip...)
>>
>> - 702
>>* CI fails
>
>Just pushed and it is failing for non R relat
Small precisions on #702:
(snip...)
- 702
* CI fails
Just pushed and it is failing for non R related reasons...
Most importantly, I have seen since a few days that the test are no more
executed for the spark interpreter for all PR builds
[INFO] --- maven-surefire-plugin:2.17:test (de
That's not the current vote. The vote for C is 1, which is alex.
> On Mar 8, 2016, at 1:15 AM, Alexander Bezzubov wrote:
>
> Ok, thank you all for participating in this public discussion - there is no
> reason for anybody to stay out of it, community opinions are very welcome.
>
> To summarize
Hello,
Kindly let me know if I've been granted the edit rights on [0]. I opened
[0] and tried to upload the proposal pdf file but the page asked me to take
permission first and no upload happened. I also found an option to edit
labels but I didn't create one because it was mentioned in the help pa
Ok, thank you all for participating in this public discussion - there is no
reason for anybody to stay out of it, community opinions are very welcome.
To summarize, here is the tally I can see:
a) for picking ONLY 208, as soon as it is ready: +2 Amos, Jeff
b) for asking both authors to come up
Github user zhongneu commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/767#issuecomment-193622520
@corneadoug I've created a new pr here. Thanks for your review!
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user zhongneu opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/767
[ZEPPELIN-209] Folder structure for notebook (based on pr-190)
### What is this PR for?
This PR is based on #190
### What type of PR is it?
Feature
### To
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/190#issuecomment-193620763
@zhongneu How about creating a PR instead?
It will be easier to comment on the code. You can always base your PR on
this one.
Once it's done, ping
Github user zhongneu commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/190#issuecomment-193619788
@Leemoonsoo @corneadoug I've made a coupe of fixes, and now it works pretty
well, but still have one problem: we can click the folder in dropdown, and goes
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-193619433
@elbamos sorry for slow re, the only things that are left:
- [ ] master and this branch have diverged: we need to either merge master
in here, or rebase it o
I should clarify my preference regarding Plan A (to only merge 1 - at least
initially).
“Which” PR to merge (or merge first) is TBD - at least for myself. I’m still
testing both PR options.
Since the original request was not to debate the fate\merit\features of any
particular contribution in
Github user chrismattmann commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/757#issuecomment-193618284
thank you for merging @Leemoonsoo ! great work @sujen1412
---
If your project is set up for it, you can reply to this email and have your
reply appear
Zhong Wang created ZEPPELIN-724:
---
Summary: Add a link to access to the paragraph's corresponding
spark job in SparkUI
Key: ZEPPELIN-724
URL: https://issues.apache.org/jira/browse/ZEPPELIN-724
Project: Z
Github user Madhuka commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/728#issuecomment-193616050
@corneadoug : #765 is contain the basic map feature which is in #152. #765
all checks have passed and no build failures.
@eddies : Heatmaps is nice addit
Prasad Wagle created ZEPPELIN-723:
-
Summary: Implement logout for security
Key: ZEPPELIN-723
URL: https://issues.apache.org/jira/browse/ZEPPELIN-723
Project: Zeppelin
Issue Type: Bug
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/692#issuecomment-193590836
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
-- Forwarded message -
From: Amos Elberg
Date: Mon, Mar 7, 2016 at 4:12 PM
Subject: Re: R interpreter in Zeppelin: further steps
To: moon soo Lee
Moon - No, I do not accept what you just wrote. None of the 'technical'
claims in your email are correct. In addition, your descrip
c) was more a way of saying that there could be multiple interpreters for
the same technology.
There was multiple discussions about trying to have interpreters outside of
the project core, and it could probably be easier for it to happen at that
time.
I think that a) or c) doesn't matter since it
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/752#issuecomment-193553923
It's more recommended to merge current master to solve conflict. That'll
run additional CI test before merge it into master.
---
If your project is set
Github user runyontr commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/752#issuecomment-193548418
Thank you all for the comments. I've noticed that now there is a note for
this pull request that this branch has conflicts that must be resolved. Would
yo
Zhong Wang created ZEPPELIN-722:
---
Summary: Spark interpreter log doesn't goes to zeppelin-sever.out
instead zeppelin-interpreter.log if we set SPARK_HOME in environment
Key: ZEPPELIN-722
URL: https://issues.apache.o
Here's technical differences between 208 and 702.
- 208 includes rscala depenency as a source, 702 download dependency
library on buildtime
- 208 placed in separate maven sub module r, 702 placed in existing spark
submodule.
- 208 creates another socket to communicate to interpreter, 702 does not
Justin Cameron created ZEPPELIN-721:
---
Summary: Cassandra interpreter missing Guava dependency in v0.5.6
Key: ZEPPELIN-721
URL: https://issues.apache.org/jira/browse/ZEPPELIN-721
Project: Zeppelin
GitHub user prasadwagle opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/766
[ZEPPELIN-666] Change location of notebook authorization information.
### What is this PR for?
Currently, notebook authorization information is stored in the note file
(note.json
Yes I do - I don’t see that there’s been *any* technical reason at all raised
in your email below, or in Alex’s.
I think statements like this: “Technically implementation of 208 and 702 are
different. No reason to reject one because of the other while they're not
identical.” are nonsense.
Amos,
Do you see any single non technical reason being discussed for not merging
208, in this thread or anywhere else? Please share them if you have.
Thanks,
moon
On Mon, Mar 7, 2016 at 10:21 AM Amos B. Elberg
wrote:
> Moon, I thought you were staying out of this?
>
> It sure sounds like we're
Jeff,
Thank you for the link about Semantic Versioning.
I don't think Zeppelin project were following versioning scheme described
at http://semver.org/, right now.
But it's good idea to define one for the project.
Amos,
People asking schedule of next version is coming out because of they don't
kn
Moon, I thought you were staying out of this?
It sure sounds like we're back on the same path we were on before, where
there's just a series of excuses for not merging 208, none of which have any
technical justification.
> On Mar 7, 2016, at 1:11 PM, moon soo Lee wrote:
>
> Hi,
>
> I agree
Hi,
I agree on c), merge both, in my strong opinion.
Regarding a) I agree on Eran, it's better let user and contributor decide
them selves.
For example, there can be other spark, sparkR interpreter implementation
based on Apache Toree (incubating) [1] or Livy[2]. If someone contribute
spark, spa
A Semantic Versioning “How To” for reference:
http://semver.org/
On 3/7/16, 9:24 AM, "moon soo Lee" wrote:
>Thanks for the feedbacks.
>
>Jeff,
>If we define version number X.Y.Z as MAJOR, MINOR, PATCH, then regular
>MINOR / PATCH release make sense to me.
>
>Amos,
>One of the most frequent
Moon - people asking when the next version is coming out, I don't think that's
a request to shift from a feature-based to a date-based release people policy.
It's just asking when the next release is.
The logic that even without date-based releases there will be releases every
2-4 months becau
Thanks for the feedbacks.
Jeff,
If we define version number X.Y.Z as MAJOR, MINOR, PATCH, then regular
MINOR / PATCH release make sense to me.
Amos,
One of the most frequent questions i got from users, in the conference,
meetups, personal email are when the next version will be released. And I
th
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/760#issuecomment-193361720
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 y
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/762
---
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 AhyoungRyu commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/754#issuecomment-193308252
@echarles I faced the same issue. I think it's a bug..
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Hello,
My user name on the CWiki : anish18sun
Thanks,
Anish.
Hi Anish,
that sounds great. You are right, notebooks at the end are just .json files
A very quick feedback - apache mailing list do not tolerate attachments, so
if you could let me know your username on a wiki [0] I'll be glad to grant
you edit rights, so you could post your proposal draft there
Hello,
Attached is a first draft of proposal for Zeppelin-684 (creating
notebooks). Please review and suggest changes.
Zeppelin is up and running on my machine. As far as I have grasped, the
changes in the different notebooks for the various datasets will be at the
json level. I have gained a fair
Github user ravicodder commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/690#issuecomment-193222906
@felixcheung rebase done.
---
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 Madhuka opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/765
[ZEPPELIN-157] GAdding Map Visualization for Zeppelin
### What is this PR for?
Adding Map Visualization for Zeppelin using Leaflet[1]
[1] http://leafletjs.com/
Github user echarles commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/754#issuecomment-193176072
Tested with zeppelin.spark.sql.stacktrace being false and true, and it
works fine.
Good to merge.
PS: With HEAD source, I have issues setti
Zhong Wang created ZEPPELIN-720:
---
Summary: Scrolling output doesn't follow the end of output for a
running job
Key: ZEPPELIN-720
URL: https://issues.apache.org/jira/browse/ZEPPELIN-720
Project: Zeppelin
42 matches
Mail list logo
