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
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
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
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
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
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
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
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 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
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
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:
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
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
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 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
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
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
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
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
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
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
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,
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
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` ->
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
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:
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
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
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/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
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
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
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 astroshim commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/912#issuecomment-221791290
@bzz I made issue(https://issues.apache.org/jira/browse/ZEPPELIN-886).
---
If your project is set up for it, you can reply to this email and have your
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/913#issuecomment-221790721
Guys, what's with CI failure?
We should not be merging PRs in case CI is not green - at least without
some investigation and results posted.
If
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/918#issuecomment-221789778
cool - should we have the info in documentation?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
36 matches
Mail list logo