Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-221793621
@shijinkui I do not think that mentioned fronted build warnings are
relevant to CI build failure.
It seems that Selenium integration tests are failing
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/913#issuecomment-221796038
@prabhjyotsingh thank you for quick research! I think same CI failure
happened at least in #905 and #917
Shall we merge #862 first and then rebase this
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/862#issuecomment-221796281
Merging as it includes HOTFIX for failing Integration Tests
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user prabhjyotsingh commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/913#issuecomment-221796576
Yes, perfect, it make sense.
---
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 p
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/862
---
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 bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/862#issuecomment-221797090
@sagarkulkarni3592 could you please assign a JIRA issue to yourself?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/913#issuecomment-221797444
Done! @minahlee could you rebase please?
---
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
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/917#issuecomment-221797397
As #862 is merged it should fix the CI, so please rebase on the latest
master.
---
If your project is set up for it, you can reply to this email and have your
r
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-221797699
As #862 is merged - it should fix the CI, so could you please rebase on the
latest master and see if that helps?
---
If your project is set up for it, you can r
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/912#issuecomment-221798075
@astroshim thanks! I think there might be fix for it just merged to master
- could you please rebase this branch and see if that resolves the issue?
---
If your
Shim HyungSung created ZEPPELIN-887:
---
Summary: can change tabsize of paragraph.
Key: ZEPPELIN-887
URL: https://issues.apache.org/jira/browse/ZEPPELIN-887
Project: Zeppelin
Issue Type: Impro
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/918#issuecomment-221800802
@vgmartinez Thank you for contribution!
Befor deep dive into the code, I have a question - could you pelase explain
the use-case you have in mind for th
Github user astroshim commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/912#issuecomment-221803140
@bzz I rebased.
---
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 ha
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/886#issuecomment-221803453
CI has been recently fixed on latest master, @natesammons-nasdaq could you
please rebase and see if that helps?
---
If your project is set up for it, you can re
Github user vgmartinez commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/918#issuecomment-221804094
@cloverhearts @astroshim @felixcheung thks, add more info and doc ASAP.
hi @bzz, I think having the option to send an email when you finish
execut
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/869#issuecomment-221808859
I think there is still a few documentation updates needed, that @AhyoungRyu
pointed out (i.e `{{BASE_PATH}}/interpreter/python.md` ->
`{{BASE_PATH}}/interpreter/
GitHub user astroshim opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/919
support changing tabsize of paragraph
### What is this PR for?
The code editor tab size is fixed as 4.
It would be better to support changing tabsize to users.
###
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/912#issuecomment-221811780
That CI issue is gone, current failure is due to networking issues on Spark
download =\
---
If your project is set up for it, you can reply to this email and h
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/835#issuecomment-221816292
@echarles Thanks for the advices and I've found the reason why
zeppelin.R.render.options. This is because ```-Pr -Pspark```. According to this
PR, Interpret
Github user echarles commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/835#issuecomment-221816775
@jongyoul Building with both -Pr -Pspark may lead to unexpected behavior,
even without the changes you brought...
---
If your project is set up for it, you
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/835#issuecomment-221817376
@echarles You're right but we need to pass the CI first. :-) I don't think
this is a real case and I'll handle it through another PR which may be about
chan
Github user shijinkui commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-221823115
@bzz have rebased. Failed all for the spark archive download timeout by
the url
`http://archive.apache.org/dist/spark/spark-1.6.1/spark-1.6.1-bin-without-
Hi,
Changing the data model was not allowed after metadata restore. Is this a bug
of kylin ? The follow is the wrong message:
Failed to deal with the request: Overwriting conflict /model_desc/Offline.json,
expect old TS 1464228158769, but it is 1464228158000
Best regards,
Tao Li
???(??
Congratulations guys, this is really good!
Good luck going forward :)
- Raj Bains
On Thu, May 26, 2016 at 9:46 AM, Ahyoung Ryu wrote:
> Congratulate all Zeppelin folks! Surely deserved it đź‘Ť
>
> On Thursday, 26 May 2016, Dafeng Wang wrote:
>
>> Congratulations!
>>
>>
>>
>> *From:* moon soo Lee
Github user minahlee commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/913#issuecomment-221831870
@bzz Rebase is done, the failure seems like related to network issue for
downloading spark.
---
If your project is set up for it, you can reply to this ema
Congratulations!!! :) :)
On Thu, May 26, 2016 at 3:20 PM, Raj Bains wrote:
> Congratulations guys, this is really good!
>
> Good luck going forward :)
>
> - Raj Bains
>
> On Thu, May 26, 2016 at 9:46 AM, Ahyoung Ryu
> wrote:
>
>> Congratulate all Zeppelin folks! Surely deserved it đź‘Ť
>>
>> On Th
Github user agura commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/916#issuecomment-221860206
@jongyoul Ignite JDBC interpreter has some specific options, so I need to
investigate possibility of usage generic JDBC interpreter. I think the best way
is to
GitHub user jongyoul reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/835
ZEPPELIN-804 Refactoring registration mechanism on Interpreters
### What is this PR for?
This PR enable Zeppelin server register Interpreters without any
dependencies of their own
Github user jongyoul closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/835
---
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 f
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/835#issuecomment-221870018
re-trigger
---
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 thi
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/916#issuecomment-221882257
@agura I'll thank you if you help merge Ignite JDBC into generic JDBC
interpreter.
And about this PR, it looks good to me. Merging if there's no mo
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/835#issuecomment-221884372
Finally, I've passed CI.
Summary of changes,
- Read interpreter info from file with json format
- Fixed some tests in order to pass without s
Github user natesammons-nasdaq commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/886#issuecomment-221910004
Looks like the tests are passing now! Nice
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/920
Remove incubating tag from website
### What is this PR for?
Remove incubating tag from website
### What type of PR is it?
Improvement
### Todos
* [x]
Github user prabhjyotsingh commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/920#issuecomment-221915198
Missing files:
- CONTRIBUTING.md
- DISCLAIMER
- README.md
- **/pom.xml
- postgresql/README.md
-
zeppelin-interpreter/src/m
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-221920236
@shijinkui It becomes green. Could you please trigger it again?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user cloverhearts commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/920#issuecomment-221925017
congratulation!!
+1
---
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 pro
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/920#issuecomment-221942221
Thanks @prabhjyotsingh and @cloverhearts taking a look.
Merge if there're no more discussions.
---
If your project is set up for it, you can reply to
Prasad Wagle created ZEPPELIN-888:
-
Summary: Build failure due to flaky test -
Key: ZEPPELIN-888
URL: https://issues.apache.org/jira/browse/ZEPPELIN-888
Project: Zeppelin
Issue Type: Bug
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/915
---
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 Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/919#issuecomment-221947360
Thanks for addressing the issue. I think it'll be more useful if tab size
can be configured globally or per interpreter, rater than individual paragraph.
Github user prasadwagle closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/917
---
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 th
Github user prasadwagle commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/917#issuecomment-221947440
@bzz
I had originally created ZeppelinScaldingShell in the
org.apache.zeppelin.scalding package. I moved it to com.twitter.scalding so
that I c
GitHub user prasadwagle reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/917
[ZEPPELIN-840] Scalding interpreter that works in hdfs mode
### What is this PR for?
Scalding interpreter that works in hdfs mode
### What type of PR is it?
Improve
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/920
---
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
Awesome news! Congrats everyone!
On Thu, May 26, 2016 at 5:27 AM, Minudika Malshan
wrote:
> Congratulations!!! :) :)
>
> On Thu, May 26, 2016 at 3:20 PM, Raj Bains wrote:
>
>> Congratulations guys, this is really good!
>>
>> Good luck going forward :)
>>
>> - Raj Bains
>>
>> On Thu, May 26, 201
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/886
---
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
Lee moon soo created ZEPPELIN-889:
-
Summary: Release 0.6.0
Key: ZEPPELIN-889
URL: https://issues.apache.org/jira/browse/ZEPPELIN-889
Project: Zeppelin
Issue Type: Task
Reporter: L
Github user minahlee commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/912#issuecomment-221996644
@astroshim Did you remove tutorial notebook on purpose? If not, can you
revert the last commit?
---
If your project is set up for it, you can reply to this
Github user prasadwagle closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/860
---
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 th
org.apache.zeppelin.notebook.Paragraph:241 - run
paragraph 20160526-212432_3024637 using pyspark
org.apache.zeppelin.interpreter.LazyOpenInterpreter@49dfce80
No output has been received in the last 10 minutes, this potentially
indicates a stalled build or something wrong with the build itself.
---
If your
GitHub user prasadwagle reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/860
[ZEPPELIN-828] Use individual user credentials for data source
authentication
### What is this PR for?
The purpose of this pull request is to allow users to use their own
cred
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/918#issuecomment-222009584
@vgmartinez Thanks for contribution.
@vgmartinez and folks, how about having generalized event hook instead of
just handling email after scheduler
Congrats and best of luck!
Thanks,
Roman.
On Wed, May 25, 2016 at 6:56 AM, moon soo Lee wrote:
> Congratulations and thank you everyone who made it possible!
>
> -- Forwarded message -
> From: Sally Khudairi
> Date: Wed, May 25, 2016 at 3:04 AM
> Subject: The Apache Software Fou
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT.
The report for your podling will form a
Github user astroshim commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/912#issuecomment-222044643
@minahlee It's my mistake. I reverted.
---
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 astroshim commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/919#issuecomment-222048031
@Leemoonsoo Good point. I agree with you that changing tab size in the
interpreter or notebook is better than paragraph. so I think Configuring tab
size of
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/912
---
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 shijinkui commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-222055896
@jongyoul I have no authorization。 cc @bzz
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-222056071
@shijinkui Just close and reopen it. :-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user shijinkui closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/905
---
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
GitHub user shijinkui reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/905
[ZEPPELIN-870] Improvement build and pom normalized
### What is this PR for?
1. frontend-maven-plugin upgrade to 1.0, as low version occur error when
build on osx
2. upgrade
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/917#issuecomment-222064408
@prasadwagle nice!
It definitely does, sounds as a great plan! What do you think about putting
`//TODO(prasadwagle) ...` with this information to the class h
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/860#issuecomment-222065338
@prasadwagle I think it's better to actually rebase (may be even
interactive, to get rid of last 2 commits) the whole branch on top of the
master instead of just
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/856#issuecomment-222065674
Looks good to me. Merging if there is no more discussion.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/835#issuecomment-222066735
The code looks great to me.
Are there any potential side-effects of this change for the existing users?
---
If your project is set up for it, you can r
Alexander Bezzubov created ZEPPELIN-890:
---
Summary: Spark sources download failure
Key: ZEPPELIN-890
URL: https://issues.apache.org/jira/browse/ZEPPELIN-890
Project: Zeppelin
Issue Type:
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/913#issuecomment-222069629
Great! If this happens again - we need to look if there is existing issue
in JIRA for CI failure under `flacky-test` label, and if there is none (as with
this ca
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/880#issuecomment-222070217
@khalidhuseynov if it's ready to merge, can you please rebase it on the
latest master?
---
If your project is set up for it, you can reply to this email and hav
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/900#issuecomment-222070354
Looks good to me. Merging if there is no further discussion.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/902#issuecomment-222070472
@khalidhuseynov seems like we need to rebase on latest master and
re-trigger CI for this one, before merging.
---
If your project is set up for it, you can repl
71 matches
Mail list logo
