Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2370
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 sven0726 closed the pull request at:
https://github.com/apache/zeppelin/pull/2370
---
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 sven0726 reopened a pull request:
https://github.com/apache/zeppelin/pull/2370
change the spark version of dockerfile
### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2371
Thanks for the review @soralee. Let me update.
---
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 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2394
Thanks for your great effort @soralee. LGTM! except
* [ ] - comments 4
* [ ] - comments 8
* [ ] - comments 9-1, 9-2, 9-3
* [ ] - comments 10
* [ ] - comments 11
---
If
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2394
11. Adjustment margin among components
- `padding-bottom: 30px` for `.tech_deploy h2`
- remove the css `tech_deploy` class in `technologies_deployments.md`
LINE16: `tech_deploy
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1970
Actually spark **won't** pass non spark.* properties to executor. This is
why I confuse how does ElasticsEarch use it.
See
Github user Ben-Epstein commented on the pull request:
https://github.com/apache/zeppelin/commit/4d398ef2a6471614cebd6b0177a08333114f5802#commitcomment-22405561
Hey, I'm working on implementing your work in this commit on Splice
Machine's database, and I'm having issues with the
Lee moon soo created ZEPPELIN-2619:
--
Summary: Save note in [Title].zpln instead of [NOTEID]/note.json
Key: ZEPPELIN-2619
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2619
Project: Zeppelin
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1970
If the non spark.* values are passed to executor and being used there, i
think it need to be reverted and be included in 0.7.2. @zjffdu What do you
think?
---
If your project is set up for
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2394
@1ambda , I've update regarding of `7.Improve layout for mobile browsers.`
could you confirm, again?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2394
@sravan-s, I've fixed to match font size as your mention. Regarding of
`uniform margin / padding scheme` I tried to fit the box ratio. could you check
this if you have time?
---
If your project
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2381
Using different background color can be an option, too.
---
If your project
Github user orenpai commented on the issue:
https://github.com/apache/zeppelin/pull/1970
As far as I can tell from the code, yes - it does some verification of this
value on the driver, and then passes it after processing to the executors.
@costin might be able to provide more
Github user randerzander commented on the issue:
https://github.com/apache/zeppelin/pull/2284
Closed in favor of https://github.com/apache/zeppelin/pull/2396
---
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 randerzander closed the pull request at:
https://github.com/apache/zeppelin/pull/2284
---
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 khalidhuseynov reopened a pull request:
https://github.com/apache/zeppelin/pull/2374
[ZEPPELIN-2593] Add storage settings to persist on commit
### What is this PR for?
adding settings to storage layer to let user choose to persist continuously
or only on commits
Github user khalidhuseynov closed the pull request at:
https://github.com/apache/zeppelin/pull/2374
---
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 issue:
https://github.com/apache/zeppelin/pull/2250
I'm a bit confused because there's some unrelated changes regarding this
issue. I don't know why you change zeppelin-interpreter package and why you
make hash code and equals method. Can you
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2368
Thanks. Will merge 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 your project does not have this feature
enabled and
Github user cfries commented on the issue:
https://github.com/apache/zeppelin/pull/2368
Re-open to give Jenkins a ping.
---
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 cfries closed the pull request at:
https://github.com/apache/zeppelin/pull/2368
---
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/2390
@qwemicheal Thanks for the contribution. Can you handle the issues @zjffdu
mentioned?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Swathi Uppala created ZEPPELIN-2618:
---
Summary: Install and configure Zeppelin 0.7.0 on Windows 7.
Key: ZEPPELIN-2618
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2618
Project: Zeppelin
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/2347
Will merge this 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 project does not have this
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/2377
Merging this 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 project does not have this
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/2347
Tried locally works fine.
@tinkoff-dwh can you resolve these conflicts.
---
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 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2370
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 qwemicheal commented on the issue:
https://github.com/apache/zeppelin/pull/2390
@zjffdu Unit test added.
---
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
Github user DrIgor closed the pull request at:
https://github.com/apache/zeppelin/pull/2250
---
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 DrIgor reopened a pull request:
https://github.com/apache/zeppelin/pull/2250
[ZEPPELIN-2085] Interpret scala code in paste mode
### What is this PR for?
Don't split scala code to lines.
Interpreter code becomes more and more complicated because some lines
GitHub user cfries reopened a pull request:
https://github.com/apache/zeppelin/pull/2368
Improved comment, removed admin user definition per default
### What is this PR for?
Improved shiro.ini.template.
Since the file is just a template, it should be such that if the
Github user cfries closed the pull request at:
https://github.com/apache/zeppelin/pull/2368
---
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/2206
@AlexanderShoshin Can you rebase it from current master?
---
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 sven0726 commented on the issue:
https://github.com/apache/zeppelin/pull/2370
@1ambda Could you please check it again ?
@felixcheung Thank you for your guidanceï¼
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2386
Will be modified after resolving the last comment of
https://github.com/apache/zeppelin/pull/2356
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2375
Do we need to keep undocumented emacs shortcuts?
---
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 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2391
@AhyoungRyu Could you help review 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 does not have this feature
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2394
7. Improve layout for mobile browsers.
7-1. each `panel-content` in the **TECHNOLOGIES** section doesn't have
margin-top or bottom. It's not consistent compared to `panel-content-user` in
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2393
@felixcheung Thanks for the review. I'll fix somethings and will remain
others for the community. I think there's Python expert in the community and
they will help to improve this feature.
---
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2381
Additionally, agree with not having too much-shadowed navbar.
But a small amount of box-shadow would help to distinguish where is the
border.
Here is an example, users can't
Cornellius Wade created ZEPPELIN-2617:
-
Summary: Remove hashtags in Zepplin URLs
Key: ZEPPELIN-2617
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2617
Project: Zeppelin
Issue Type:
Github user sravan-s commented on the issue:
https://github.com/apache/zeppelin/pull/2394
I think it would be better if the font sizes inside top box(technologies)
and bottom(deployments) were of same size and had a uniform margin / padding
scheme. Also about **use now** and **learn
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2394
@AhyoungRyu @1ambda @Leemoonsoo, please review again!
---
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 commented on the issue:
https://github.com/apache/zeppelin/pull/2368
ping
---
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 soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2381
@1ambda, @Leemoonsoo, @AhyoungRyu, I created a PR regrading `Technologies
and Deployments`
#2394. Let me make a remainder PR.
---
If your project is set up for it, you can reply to this
GitHub user soralee opened a pull request:
https://github.com/apache/zeppelin/pull/2394
[gh-pages] [ZEPPELIN-2597] adding technologies and deployments (Main Page)
### What is this PR for?
This PR is for Improving more comfortable guidance for point of user view
in the main
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2354
LGTM. Thanks @sohaibiftikhar for the contribution.
Merge to master if no further discussions here.
---
If your project is set up for it, you can reply to this email and have your
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2250
I think we'd better take care of the comments left.
---
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 DrIgor commented on the issue:
https://github.com/apache/zeppelin/pull/2250
Please explain what issues I need to fix)
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2369
Merge to master if no further 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 does not have this
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2372
I failed to test this feature since terminal i am using doesnt support that
option. others can help review. sorry for the late reply.
---
If your project is set up for it, you can reply to this
52 matches
Mail list logo
