Thank you for your kind feedback!
And yes, there definitely was more effort than one wold think, so thank
you for noticing an unconsciousness intention to highlight that fact :)
On Tue, Mar 31, 2015 at 8:33 AM, moon soo Lee wrote:
> Here's few things,
>
> March 2015 report mentioned about Apa
There was already a discussion here to mute JIRA notifications (keep only
'issue creation' forward to dev@) which resulted in
https://issues.apache.org/jira/browse/INFRA-9358
The problem right now is that EVERY comment on PR comes twice to dev@: once
from GH and once from JIRA (because GH-JIRA int
Github user swkimme commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/11#issuecomment-88367266
LGTM! Great!
---
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
[
https://issues.apache.org/jira/browse/ZEPPELIN-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390044#comment-14390044
]
ASF GitHub Bot commented on ZEPPELIN-19:
GitHub user RamVenkatesh opened a pull r
GitHub user RamVenkatesh opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/22
ZEPPELIN-19 Failures from disabled interpreters not reported
Handle all exceptions from NotebookServer runParagraph and update Note
You can merge this pull request into a Git reposit
Ram Venkatesh created ZEPPELIN-19:
-
Summary: Failures from disabled interpreters not reported
Key: ZEPPELIN-19
URL: https://issues.apache.org/jira/browse/ZEPPELIN-19
Project: Zeppelin
Issue T
To me, having separate mailing list
'issues' for JIRA
'reviews' for Pull Request
Sounds great.
Best,
moon
On Wed, Apr 1, 2015 at 1:31 PM Konstantin Boudnik wrote:
> IIRC there were an attempt to move all JIRA notifications to issues@
> list, is
> it not?
>
> Cos
>
> On Wed, Apr 01, 2015 at 1
Hi Damien,
Thanks for the quick and descriptive reply. I will go through each of them
and update you on those and I will share my experiences in my blog too. I
will go through the code-base with consideration for the above files.
Thanks
On Wed, Apr 1, 2015 at 7:36 AM, Corneau Damien
wrote:
> H
IIRC there were an attempt to move all JIRA notifications to issues@ list, is
it not?
Cos
On Wed, Apr 01, 2015 at 11:43AM, Corneau Damien wrote:
> I too prefer using basic Github notifications than ASF Git bot, they are
> more readable.
>
> We can't really turn everything off because it's part o
I too prefer using basic Github notifications than ASF Git bot, they are
more readable.
We can't really turn everything off because it's part of Apache Zeppelin
discussions, but filtering so that people can subscribe if they want is
better.
For the duplicates however, it would be nice to turn it o
My eye was bleeding for too many emails, too.
I filtered out all emails from ASF Git bot and just using dev@ mailing list
and email from github.
On Wed, Apr 1, 2015 at 11:29 AM Corneau Damien
wrote:
> Hi,
>
> I find it difficult to follow the dev mailing list recently, there is a lot
> of noise
Hi,
At first, I totally agree with you, I don't think It's good to receive
multiple same messages from JIRA and Github. I suggest we turn should off
one of them.
JL.
On Wed, Apr 1, 2015 at 11:28 AM, Corneau Damien
wrote:
> Hi,
>
> I find it difficult to follow the dev mailing list recently, th
Hi,
I find it difficult to follow the dev mailing list recently, there is a lot
of noise because of JIRA and GITHUB. We even get some emails twice (GITHUB
comment on JIRA issues).
Some projects have different mailing list to separate all of those.
For example:
'issues' for JIRA
'reviews' for Pu
Right,
With that maven-web plugin updates we now have to use maven 3.1.0 minimum.
It seems there was problem with the maven-web plugin 0.2.0, but not sure why
On Wed, Apr 1, 2015 at 6:21 AM, RJ Nowling wrote:
> "requires a newer version"
>
> On Tue, Mar 31, 2015 at 4:08 PM, RJ Nowling wrote:
>
Hi,
First of all we use angularjs so you might want to familiarize yourself
with it.
Currently the code is not well organized (big files), and not really
angular friendly either, but we are working on fixing that.
We also were preparing a switch to Typescript, so you might want to read
about it t
[
https://issues.apache.org/jira/browse/ZEPPELIN-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jongyoul Lee updated ZEPPELIN-13:
-
Component/s: Core
> ZEPPELIN_CONF_DIR cannot be reached until ZEPPELIN_CONF_DIR become set
>
[
https://issues.apache.org/jira/browse/ZEPPELIN-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lee moon soo updated ZEPPELIN-13:
-
Fix Version/s: 0.5.0
Assignee: Jongyoul Lee
> ZEPPELIN_CONF_DIR cannot be reached until
[
https://issues.apache.org/jira/browse/ZEPPELIN-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389868#comment-14389868
]
ASF GitHub Bot commented on ZEPPELIN-7:
---
GitHub user jongyoul opened a pull request:
GitHub user jongyoul opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/21
[ZEPPELIN-7] Minor. Removed SPARK_YARN_JAR from zeppelin-env.sh.template
I missed removing configuration option.
You can merge this pull request into a Git repository by running:
$
GitHub user jongyoul opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/20
[ZEPPELIN-13] ZEPPELIN_CONF_DIR cannot be reached until ZEPPELIN_CONF_DIR
become set
bin/common.sh tries to find and set ZEPPELIN_CONF_DIR in order to read
zeppelin-env.sh, but ZEPPELIN
[
https://issues.apache.org/jira/browse/ZEPPELIN-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389854#comment-14389854
]
ASF GitHub Bot commented on ZEPPELIN-13:
GitHub user jongyoul opened a pull reque
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/15
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/14
---
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
Github user swkimme commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/19#issuecomment-88302569
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 featur
[
https://issues.apache.org/jira/browse/ZEPPELIN-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389826#comment-14389826
]
ASF GitHub Bot commented on ZEPPELIN-17:
Github user swkimme commented on the pul
[
https://issues.apache.org/jira/browse/ZEPPELIN-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389813#comment-14389813
]
ASF GitHub Bot commented on ZEPPELIN-17:
Github user Leemoonsoo commented on the
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/19#issuecomment-88300939
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 feat
[
https://issues.apache.org/jira/browse/ZEPPELIN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jongyoul Lee updated ZEPPELIN-18:
-
Description: We only use python sources under SPARK_HOME/python for
PySpark. I think copying thes
Jongyoul Lee created ZEPPELIN-18:
Summary: Remove setting SPARK_HOME for PySpark
Key: ZEPPELIN-18
URL: https://issues.apache.org/jira/browse/ZEPPELIN-18
Project: Zeppelin
Issue Type: Improvem
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/11#issuecomment-88299077
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 featur
[
https://issues.apache.org/jira/browse/ZEPPELIN-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389751#comment-14389751
]
ASF GitHub Bot commented on ZEPPELIN-17:
Github user jongyoul commented on the pu
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/19#issuecomment-88292716
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 featur
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/15#issuecomment-88292163
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 featur
[
https://issues.apache.org/jira/browse/ZEPPELIN-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389482#comment-14389482
]
RJ Nowling commented on ZEPPELIN-10:
[~epakhomov] is currently using -p (what you sug
[
https://issues.apache.org/jira/browse/ZEPPELIN-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389473#comment-14389473
]
Felix Cheung commented on ZEPPELIN-10:
--
I think RJ is saying you could config Docker
"requires a newer version"
On Tue, Mar 31, 2015 at 4:08 PM, RJ Nowling wrote:
> Hi all,
>
> I noticed that the maven web front end plugin was recently updated.
> Unfortunately, this requires a never version of Maven which may be an issue
> for CentOS / RHEL users since EPEL has an older version
Hi all,
I noticed that the maven web front end plugin was recently updated.
Unfortunately, this requires a never version of Maven which may be an issue
for CentOS / RHEL users since EPEL has an older version of Maven.
I realize that this is a challenge for Zeppelin and ideally, would not be
some
[
https://issues.apache.org/jira/browse/ZEPPELIN-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389377#comment-14389377
]
Felix Cheung commented on ZEPPELIN-17:
--
https://github.com/apache/incubator-zeppelin
[
https://issues.apache.org/jira/browse/ZEPPELIN-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389376#comment-14389376
]
ASF GitHub Bot commented on ZEPPELIN-17:
GitHub user felixcheung opened a pull re
GitHub user felixcheung opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/19
[ZEPPELIN-17] PySpark Interpreter should allow starting with a specific
version of Python
Add PYSPARK_PYTHON.
We could also add PYSPARK_DRIVER_PYTHON (Zeppelin Interpreter is the
Felix Cheung created ZEPPELIN-17:
Summary: PySpark Interpreter should allow starting with a specific
version of Python
Key: ZEPPELIN-17
URL: https://issues.apache.org/jira/browse/ZEPPELIN-17
Project:
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/17#issuecomment-88191513
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
[
https://issues.apache.org/jira/browse/ZEPPELIN-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389031#comment-14389031
]
ASF GitHub Bot commented on ZEPPELIN-16:
Github user felixcheung commented on the
Hi All,
Can you point out some resources / tutorials to understand the code base
of zeppelin?
Since I am trying to familiarize myself with the zeppelin code structure
and architecture
Thanks
On Fri, Mar 20, 2015 at 10:57 AM, madhuka udantha
wrote:
> Hi All,
>
> I'm Udantha, MSc. Student at
I've been using zeppelin.sh as well.
On Mon, Mar 30, 2015 at 7:54 PM, Jongyoul Lee wrote:
> Hi Anthony,
>
> Yeap, I just wondering who uses this script because I don't use that.
>
> Regards,
> Jongyoul Lee
>
> On Tue, Mar 31, 2015 at 9:49 AM, Anthony Corbacho <
> anthonycorba...@apache.org> wrot
Hi,
I have been looking at zeppelin 56 in jira have question on where this is
going...
When you refer to job page and a dataset page - what does it mean?
currently it is up for the user to create the dataset by registering a
table in some way then running queries on this set.
I am not sure if thi
Hi,
Do you think it is valuable to have a "Dependent paragraph" feature in
zeppelin - e.g. to be able to mark a paragraph dependent on another
paragraph. - that way, a paragraph is not executed if the parent paragraph
did not complete successfully.
--
Eran | CTO
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/15#issuecomment-88053443
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 feat
Hi Heiko,
It's really great to hear about interpreter to prestodb.
I think there were no issue or discussion about presto db so far, so please
feel free to create new issue.
Best,
moon
On Tue, Mar 31, 2015 at 8:08 PM Heiko Braun
wrote:
>
> I am looking into wirting an interpreter to support pr
I am looking into wirting an interpreter to support prestodb [1]. Is anybody
aware of some work in this area? I've been looking at the Jira, but couldn't
find anything. So if there are no objections, I would create a new issue and
assign it to myself.
[1] http://prestodb.io
Regards, Heiko
GitHub user corneadoug opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/18
Replace ngMin by ngAnnotate
Improve Grunt Build, by replacing ngMin with ngAnnotate
ngMin is deprecated and ngAnnotate is its replacement.
Zeppelin-web compilation tim
Hi,
So far I was involved through mails so I am not sure about the process of
fixing\correcting something but after reading the contributing.md document
I though we need to fix the git reference to the new apache reference:
Software Configuration Management(SCM)
Zeppelin uses Git for it's SCM sy
52 matches
Mail list logo
