Github user del680202 closed the pull request at:
https://github.com/apache/zeppelin/pull/1976
---
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 feature
Github user del680202 commented on the issue:
https://github.com/apache/zeppelin/pull/1976
@AhyoungRyu
I test #2149 in my machine.
It works well, Thanks.
But I seem when I edit interpreter config then the zombie process will
be occurred.
Anyway, ``Restart`` button
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2134
@AhyoungRyu
if you configure the note and working only in report mode then you will not
see when the report is incomplete.I can add the close button
---
If your project is set up for it,
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2134
@AhyoungRyu
if you configure the note and working only in report mode then you will not
see when the report is incomplete.I can add the close button
---
If your project is set up for it, you
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2186
@AhyoungRyu This PR reverted some of #2042 and I didn't include to change
[this line](
https://github.com/apache/zeppelin/pull/2042/files#diff-7a20bcbe25109dfb2ad811a62a366cbeL63).
If we
Meethu Mathew created ZEPPELIN-2313:
---
Summary: Run-a-paragraph-synchronously response documented
incorrectly
Key: ZEPPELIN-2313
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2313
Project:
Meethu Mathew created ZEPPELIN-2312:
---
Summary: Allow to Undo edits in a paragraph once its executed and
undo deleted paragraph
Key: ZEPPELIN-2312
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2312
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2186
@Remilito Will be appreciated if you can take a look this :)
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2186
@soralee Thanks for digging it up!
Seems https://github.com/novus/nvd3/pull/1934 fixed this issue and merged
in Jan. Hopefully they have a plan to release another minor version soon
GitHub user soralee opened a pull request:
https://github.com/apache/zeppelin/pull/2186
[ZEPPELIN-2229] revert ndv3 version from 1.8.5 to 1.7.1
### What is this PR for?
After [[ZEPPELIN-1588]: bumping nvd3 to 1.8.5](#2042) merged, Zeppelin was
occurring front-end side error
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2141
---
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 feature is
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2144
---
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 feature is
I propose the following RC to be released for the Apache Zeppelin 0.7.1
release.
The commit id is 163f6730ea91486c581f502863fe62b3cd9b06d4 which is
corresponds to the tag v0.7.1-rc2:
https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=refs/tags/v0.7.1-rc2
The release archives (tgz),
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2119
---
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 feature is
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1872
@epahomov Could you close this PR 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 project does not have this
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1907
Hi @cuspymd, what do you think about @astroshim 's comment?
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2134
Tested and basically agree with @Leemoonsoo. But one thing I just noticed
is this new message can be seen in report mode.
![screen shot 2017-03-24 at 12 20 56
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2181
Merge into master and branch-0.7 if there are no more comments on this.
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2184
Merge into master if there are no more comments.
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2185
@Leemoonsoo Thanks!
Merge into master and branch-0.7 if there are no more comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AhyoungRyu closed the pull request at:
https://github.com/apache/zeppelin/pull/2185
---
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 feature
GitHub user AhyoungRyu reopened a pull request:
https://github.com/apache/zeppelin/pull/2185
[MINOR][ZEPPELIN-2308] Fix vis icon button group
### What is this PR for?
Since "Save" button which shows up when there is change in the package
bundle ordering is included in same
I am canceling the vote due to the interpreter exception propagation issue
[1].
Vote for rc2 will be ready in few hours.
Regards,
Mina
[1] https://issues.apache.org/jira/browse/ZEPPELIN-2294
On Wed, Mar 22, 2017 at 9:57 PM Jeff Zhang wrote:
> I will change my vote to -1, as
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2134
@tinkoff-dwh Ah, i see. i didn't see where this margin comes from.
---
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 tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2134
@Leemoonsoo
possible. This margin within HTML Message maybe there are problems in other
messages (without bootstrap). I'll try.
---
If your project is set up for it, you can reply to
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2134
@tinkoff-dwh thanks!
It's nit, but bottom margin is bit much compare to other margins in
paragraph. i tried mark other margins.
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2134
@Leemoonsoo
I think now is fine (data table + message separated from footer), but I can
increase the top margin
---
If your project is set up for it, you can reply to this email and
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2113
ping @soralee
---
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,
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2134
![image](https://cloud.githubusercontent.com/assets/1540981/24267004/1c4a45d6-0fc6-11e7-8098-8bb923710260.png)
Top margin looks bit small and bottom margin looks too large. What do you
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2135
I tested last commit and it works well.
However the variable can't be read from the other paragraph.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2178
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 feature
enabled and wishes so, or if the
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2179
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 feature
enabled and wishes so, or if the
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2181
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 feature
enabled and wishes so, or if the
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2183
Thanks @andreaTP.
LGTM and merge to branch-0.7 if no further 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
Uwe Zenker created ZEPPELIN-2311:
Summary: leaflet.js polyline not working in %angular
Key: ZEPPELIN-2311
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2311
Project: Zeppelin
Issue
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2168
Thanks @sravan-s for clarify.
Tested and it works well.
Merge to master and branch-0.7 if no further discussions
---
If your project is set up for it, you can reply to this email
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2163
I think it should able to do without refresh().
Do you have idea why it was failed when `waitForParagraph(1, "FINISHED")`
replaced sleep?
---
If your project is set up for it, you can
Tried on my local machine just now. It’s working fine.
It might be a Mesos integration problem
> On Mar 22, 2017, at 10:45 PM, Jeff Zhang wrote:
>
>
> I suspect it is due to spark issue. Can you run it in spark shell local mode
> to verify that ?
>
>
> Chaoran Yu
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2173
LGTM and merge to master and branch-0.7 if no further comments.
Thanks @elkangaroo for the contribution!
---
If your project is set up for it, you can reply to this email and have your
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/780
thanks for reporting this. let me try to test in out in a couple of days
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2185
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 feature
enabled and wishes so, or if the
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2184
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 feature
enabled and wishes so, or if the
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2085
Ok.
Any other comment? Merging if no more discussion.
---
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 AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/2185
[MINOR][ZEPPELIN-2308] Fix vis icon button group
### What is this PR for?
Since "Save" button which shows up when there is change in the package
bundle ordering is included in same button
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/2184
[MINOR][ZEPPELIN-2306] Improve alignment of components in Helium header
### What is this PR for?
If there are 2 more enabled `VISUALIZATION` pkgs, the ordering control
section will be
sam mussell created ZEPPELIN-2310:
-
Summary: Cannot use credentials with JDBC prefix feature
Key: ZEPPELIN-2310
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2310
Project: Zeppelin
GitHub user andreaTP opened a pull request:
https://github.com/apache/zeppelin/pull/2183
[ZEPPELIN-2309] Backport maven and npm repo config to 0.7
### What is this PR for?
Backport configuration settings for maven central and npm repository to 0.7.
### What type of PR
Andrea Peruffo created ZEPPELIN-2309:
Summary: Backport maven and npm repo config to 0.7
Key: ZEPPELIN-2309
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2309
Project: Zeppelin
Ahyoung Ryu created ZEPPELIN-2308:
-
Summary: Rightmost Helium viz icon in button group is not regarded
as last child
Key: ZEPPELIN-2308
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2308
Oleh Martushevskyi created ZEPPELIN-2307:
Summary: ZeppelinContext isn't working in Livy interpreter
Key: ZEPPELIN-2307
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2307
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2175
---
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 feature is
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2175
Will merge it as an hotfix into master and branch-0.7
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2175
Tested restart with notebook and interpreter tab
1. Per user/scoped
2. Per user/isolated
3. Per note/scoped
4. Per note/isolated
5. Shared
---
If your project is set up for
Github user michaelboulter commented on the issue:
https://github.com/apache/zeppelin/pull/2095
Is there a workaround?
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2175
And can you add '[HOTFIX]' into the title of this PR?
---
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
Ahyoung Ryu created ZEPPELIN-2306:
-
Summary: Header section of Helium menu need better alignment
Key: ZEPPELIN-2306
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2306
Project: Zeppelin
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2178
Looks better :)
---
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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2181
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 feature
enabled and wishes so, or if
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2180
@sravan-s Thanks for the suggestion. Addressed in
34dfec8a41a0e998fcc8c030860a6c796d11df86 :)
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2179
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 feature
enabled and wishes so, or if the
Github user sergeymazin commented on the issue:
https://github.com/apache/zeppelin/pull/2120
@1ambda thanks for working on this.
I guess you figured everything out with @FRosner in #2176 and #2177
already. Please let me know if I can help somehow.
---
If your project is set up
GitHub user jongyoul opened a pull request:
https://github.com/apache/zeppelin/pull/2182
[ZEPPELIN-2248] Fix javax.ws.rs and cxf version mismatch
### What is this PR for?
Fixing version mismatch among jetty, cxf, jersey
### What type of PR is it?
[Bug Fix]
Meethu Mathew created ZEPPELIN-2305:
---
Summary: overall experience on auto-completion need to improve.
Key: ZEPPELIN-2305
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2305
Project: Zeppelin
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/2181
[ZEPPELIN-2304] Fix vis Icon sizes in helium page
### What is this PR for?
Icon size of helium vis packages doesn't fit into the container button. I
attached a image.
Github user FRosner commented on the issue:
https://github.com/apache/zeppelin/pull/2177
Gotcha @1ambda,
The gifs make it clear now, thanks! Not sure about the exact code changes
as I'm not that familiar with the code base you're touching. Do you have any
specific part I
Hoon Park created ZEPPELIN-2304:
---
Summary: Fix size of helium vis icon in '#helium'
Key: ZEPPELIN-2304
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2304
Project: Zeppelin
Issue Type:
Github user FRosner commented on the issue:
https://github.com/apache/zeppelin/pull/2176
Understood @1ambda . Thanks for updating the gifs, now it is clear to me
except one thing. When the second notebook had `user1` written and the first
notebook executed the paragraph with `admin`
Github user sravan-s commented on the issue:
https://github.com/apache/zeppelin/pull/2180
Hi, I guess calling it 'recently published' instead of 'lately published'
is a better slang
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user sadhen commented on the issue:
https://github.com/apache/zeppelin/pull/319
@Leemoonsoo the delivery orders do not matter. Since the call of broadcast
on message 1 and the call of broadcast on message 2 would be processed one by
one since `noteSocketMap` is synchronized.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2174
@1ambda I fixed it in the latest commit
bc7643c46dc6690b5b1f1a91249bcf4ee0e93a43. You can simply check whether it was
fixed or not by comparing `INTERPRETER` type of packages are well located
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/2180
[gh-pages][ZEPPELIN-2303] Fix lately published package ordering
### What is this PR for?
I added pagination under Helium package list in
https://zeppelin.apache.org/helium_packages.html
Ahyoung Ryu created ZEPPELIN-2303:
-
Summary: 'Lately published' doesn't show actual latest published
package
Key: ZEPPELIN-2303
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2303
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2130
---
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 feature is
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2139
---
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 feature is
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2158
@felixcheung
I don't see a problem.
1. /**/ will not be processed
2. /*\n*/ will not be processed
---
If your project is set up for it, you can reply to this email and have
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/2179
[ZEPPELIN-2211 Too many WARN logs: "Couldn't get interpreter editor setting'
### What is this PR for?
every time we insert invalid backend magic (e.g `sparc`),
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2158
that's the thing, each of these implementation handles comments differently.
for instance, solr JDBC shares the same spec as
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/2178
[ZEPPELIN-2302] Add info level logs when installing node modules and
bundling helium pkgs
### What is this PR for?
Add info level logs when installing node modules and bundling helium
Hoon Park created ZEPPELIN-2302:
---
Summary: Add info level logging when installing node modules and
bundling
Key: ZEPPELIN-2302
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2302
Project: Zeppelin
79 matches
Mail list logo