Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1360
@jongyoul Then can we use JDBC interpreter as described in [How to
use](http://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/interpreter/jdbc.html#how-to-use)
section like before? I just wondered :D
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1356
@felixcheung I agree with @corneadoug. If this document page need to be
posted to the external resources, then we may need to attach `Apache` in front
of every `Zeppelin`. But we don't need
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1339
@bzz Thank you for saying so! Then I'll continue my work in here and let
you know :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1356
@corneadoug Don't worry about that. Let me repush 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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1354
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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1354
@corneadoug Thank you for the explanation. Since it's a only one page, i've
created a PR at your repo :)
(Just combined `docs/README.md` & `docs/CONTRIBUTING.md` contents)
---
If
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1354
@corneadoug Great work! Definitely this way would be better than we put
`CONTRIBUTING.md` under each component dir in Zeppelin github. I also left some
minor comments.
One question
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1355
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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1346
@oeegee Yeah I saw your (unofficial?)issue report on FB. Thanks for fixing
this! LGTM ð
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1302
@astroshim Oh that was my bad. Please ignore my above comment. I only build
`zeppelin-web` not backend side.
Tested again and it works well as expected. Let's wait the other reviewers
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1302
@astroshim I've also thought the interpreter `restart` button in separated
page quite uncomfortable. This PR can be a good start for the better UX i think
:)
I tested your patch
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1340
@anthonycorbacho Updated the image as you said. You can check `before` &
`after` in the PR description.
---
If your project is set up for it, you can reply to this email and have your
r
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1346
@oeegee Thank you for the contribution :) Could you elaborate more ` What
is this PR for?`, `What is the Jira issue?` and `How should this be tested?`
sections by editing your PR description
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1339
@bzz Thank you for such precise comment! Let me break down your feedback
one by one(just for making it clear) :)
1.
>/.spark-dist/ is under cache on TravisCI which is S3 buc
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1208
Using this PR I updated Spark logo to new one as #1279 did.
---
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/1340
@anthonycorbacho Sure. Let me update then :)
---
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 reopened a pull request:
https://github.com/apache/zeppelin/pull/1339
[WIP][ZEPPELIN-1332] Remove spark-dependencies & suggest new way
### What is this PR for?
Currently, Zeppelin's embedded Spark is located under `interpreter/spark/`.
For
Github user AhyoungRyu closed the pull request at:
https://github.com/apache/zeppelin/pull/1339
---
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 opened a pull request:
https://github.com/apache/zeppelin/pull/1339
[WIP][ZEPPELIN-1332] Remove spark-dependencies & suggest new way
### What is this PR for?
Currently, Zeppelin's embedded Spark is located under `interpreter/spark/`.
For whom **bu
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1208
Since Zeppelin is about to release `0.6.1` version, I'll add `0.6.1` column
as well.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1326
[ZEPPELIN-1323] Add contribution guide for Zeppelin documentation
### What is this PR for?
Recently I added auto generated Table of Contents by #1031 and searching
feature by #1266. So I
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1318
@astroshim Great work indeed! As just proof of reading
`spark_cluster_mode.md`, I updated a few minor things in
[here](https://github.com/astroshim/zeppelin/pull/9). Could you check this one
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1314
[MINOR] Update outdated contents in zeppelin-distribution/*.md files
### What is this PR for?
It seems some outdated contents are remained in
`zeppelin-distribution/*.md` files.
e.g
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1311
@cloverhearts Thanks for the patch! I faced this wired 503 error several
times.
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/681
>someone can create/delete notebook
Regarding this, please refer to [Notebook Authorization
setting](http://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/security/notebook_authorization.h
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1266
@bzz After re-triggered CI build, it fails again only in `spark 1.4\ scala
2.10` with
```
Running org.apache.zeppelin.rest.ZeppelinSparkClusterTest
...
No output has been
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1266
@bzz
>In my experience if PR author try to follow such steps - that speeds up
the review process by order of magnitude AND helps the project to make CI more
stable.
Yeah right
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1266
It seems the CI failure is irrelevant with this PR. Can someone review this
one?
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1294
@yoonjs2 Thank you for taking care of this. Could you update the below
sentence as well in [this
section](https://github.com/yoonjs2/zeppelin/blob/5ac7de7a4f235cd7b1f27cc4d3c5c76d35dca019/docs
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1290
@mwkang Thanks for the improvement! Tested locally and it works well as
expected.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1284
@astroshim Thank you for the prompt 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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1280
@sarutak Thanks for your contribution!
I checked both Spark 1.4.1 and 1.5.0 docs
-
[http://spark.apache.org/docs/1.4.1/configuration.html#application-properties](http
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1279
@sarutak Thanks for taking care of this. Looks good!
---
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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1257
@astroshim Tested again and checked the bug is gone. Thanks for the prompt
fix ð
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1257
@astroshim
>Does this needs documentation? no
I think we need a documentation for "Interpreter Authorization" feature
like we have below docs pages.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1257
@astroshim Awesome. I saw many people have talked about this feature :) I
tested your patch locally, it works well as expected. But I found one issue
regarding user suggestion
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1271
@sarutak Looks good. Thanks!
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1271
@sarutak Thanks for fixing this. I found more `SparkSQL` in the below 2
files.
-
[docs/manual/dynamicform.md#using-form-templates](https://github.com/apache/zeppelin/blob/master/docs
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1266
@bzz Really appreciate for your all precise comments! Updated several docs
as you suggested :)
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1207
CI build failure is irrelevant with this PR i think. Can this be merged
then?
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1268
@zjffdu you have good eyes :) Looks good.
---
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 opened a pull request:
https://github.com/apache/zeppelin/pull/1266
[ZEPPELIN-1219] Add searching feature to Zeppelin docs site
### What is this PR for?
As more and more document pages are added, it's really hard to find
specific pages. So I added
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1241
@zjffdu Yeah I also struggled with ruby and my OSX version issues. Anyway
thanks for providing the link :)
---
If your project is set up for it, you can reply to this email and have your
GitHub user AhyoungRyu reopened a pull request:
https://github.com/apache/zeppelin/pull/1241
[ZEPPELIN-1217] Remove horizontal scrollbar in Zeppelin conf table
### What is this PR for?
This PR will fix
[ZEPPELIN-1217](https://issues.apache.org/jira/browse/ZEPPELIN-1217
Github user AhyoungRyu closed the pull request at:
https://github.com/apache/zeppelin/pull/1241
---
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 commented on the issue:
https://github.com/apache/zeppelin/pull/1241
@zjffdu I'm not sure, your issue is related with [this
issue](https://github.com/bundler/bundler/issues/4065#issuecomment-149596385),
could you try
```
gem uninstall bundler
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1241
@zjffdu Did you run `bundle install` under `ZEPPELIN_HOME/docs` dir?
---
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/1241
@zjffdu Could you review this PR as a reporter?
---
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 opened a pull request:
https://github.com/apache/zeppelin/pull/1241
[ZEPPELIN-1217] Remove horizontal scrollbar in Zeppelin conf table
### What is this PR for?
This PR will fix
[ZEPPELIN-1217](https://issues.apache.org/jira/browse/ZEPPELIN-1217
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1227
CI failure with below error
```
Summary
---
Generated at: 2016-07-25T16:46:38+00:00
Notes: 3
Binaries: 152
Archives: 0
Standards: 108
Apache
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1227
@astroshim Cool! Is this PR only for Spark standalone mode? If so, why
don't you edit TODO list?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1214
@karup1990 Thanks! Looks good ð
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1173
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
Github user AhyoungRyu commented on the pull request:
https://github.com/apache/zeppelin/commit/5a27871f5a9e436653c8862e6d2ecc8913fdd496#commitcomment-18350624
In docs/security/shiroauthentication.md:
In docs/security/shiroauthentication.md on line 121:
Here is a typo. `easely
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1208
@Leemoonsoo Can you review this one? I updated the PR description :)
---
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/1207
@zjffdu @jongyoul Could you review this one? :)
---
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 opened a pull request:
https://github.com/apache/zeppelin/pull/1207
[DOC][ZEPPELIN-1209] Remove a useless sentence about default interpreter in
docs
### What is this PR for?
As new interpreter registration mechanism which was started in
[ZEPPELIN-804
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1203
[DOC][MINOR] Fix 'Drill JDBC Driver' link in jdbc.md
### What is this PR for?
This PR is for fixing odd 'Drill JDBC Driver' link in `jdbc.md`
### What type of PR
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1198
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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1170
+1 for technical docs `bigquery/README.md` that @bzz suggested and it looks
great that you added!
How about adding below one sentence in the end of `bigquery.md` so that
users can know
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1187
Is this PR WIP? I think `rest-notebook.md` file needs to be updated as well.
[docs/rest-api/rest-notebook.md](https://github.com/apache/zeppelin/blob/master/docs/rest-api/rest-notebook.md
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1185
@astroshim Right. And agree with @felixcheung. Let do that in separate PR
then :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1185
@astroshim Good catch! How about adding 404 page (like github does) instead
of just redirecting `Home` without any message. In 404 page, we can add sth
like "This is not the notebook pag
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1162
@bzz Sure that make sense and thanks for clarifying it. Let me do that in
other PR then :)
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1177
@corneadoug I also saw this error in my console. 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
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1179
[ZEPPELIN-1109] Remove bootstrap dialog fade-in/out animation
### What is this PR for?
This PR will fix
[ZEPPELIN-1109](https://issues.apache.org/jira/browse/ZEPPELIN-1109).
I'm
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1162
@bzz CI is green now :)
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1176
@cloverhearts Is this PR WIP?
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1172
@corneadoug When I build this PR in my local, i got this jscs warnings.
https://cloud.githubusercontent.com/assets/10060731/16793638/7b1dc450-490d-11e6-837d-8f271a40d049.png
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1172
@corneadoug more graceful! Thanks for taking care of 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/1172
@corneadoug Wasn't it intended behaviour because of
[https://github.com/apache/zeppelin/pull/862#issuecomment-221474937](https://github.com/apache/zeppelin/pull/862#issuecomment-221474937
Github user AhyoungRyu closed the pull request at:
https://github.com/apache/zeppelin/pull/1161
---
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/1161
[ZEPPELIN-906] Apply new mechanism to AlluxioInterpreter
### What is this PR for?
This PR applies the [new interpreter registration
mechanism](https://issues.apache.org/jira/browse
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1162
[ZEPPELIN-909] Apply new mechanism to Elasticsearch interpreter
### What is this PR for?
This PR applies the [new interpreter registration
mechanism](https://issues.apache.org/jira/browse
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1161
[ZEPPELIN-906] Apply new mechanism to AlluxioInterpreter
### What is this PR for?
This PR applies the [new interpreter registration
mechanism](https://issues.apache.org/jira/browse
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/993
@prabhjyotsingh Since #1100 was merged into master, I updated
`credential.controler.js`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1135
@davidtzoor Oh sorry for my late response. Did you fetch the latest version
of upstream `master`?
```
git checkout master
git fetch upstream
git pull upstream master
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/993
@prabhjyotsingh i'll rebase after #1100 merged and add the alert message to
credential page as well :)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/993
@prabhjyotsingh Thanks for your feedback. I addressed it in the last commit
:)
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/993
@prabhjyotsingh Sorry for my late response. Since i think they need to know
the existence of those menus(`Interpretes`, `Configurations` and
`Credentials`), I added `ngToast` error message
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1100
@corneadoug yeah I did :)
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1143
@jeffsteinmetz Right. So Firefox users can know they can scroll down and
there is more menus even though this PR couldn't be applied to Firefox.
Thanks for testing this @Leemoonsoo
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1143
@jeffsteinmetz It will be appreciate if you can review this PR as a
reporter of this issue :)
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1138
@felixcheung I updated `shell.md` as you suggested :)
I also applied TOC(Table of Contents) to `rest-credential.md` which is from
#1030.
---
If your project is set up for it, you can
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1100
@corneadoug All CI builds failed. Seems they are related with
[ZEPPELIN-1016](https://issues.apache.org/jira/browse/ZEPPELIN-1016) or
[ZEPPELIN-1126](https://issues.apache.org/jira/browse
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1138
[DOC][MINOR] Add shell interpreter docs to _navigation.html
### What is this PR for?
After #1087 merged, a new docs `shell.md` was added. But in the docs
website, still Shell interpreter
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1044
@davidtzoor Never mind. Please feel free to do that :)
---
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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1088
@prabhjyotsingh Sorry for my late response. You're right. After just
clicking `cancel`, it should focus on textbox again as you said. And regarding
your second comment, I blocked ESC back
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1131
[gh-pages] Update Zeppelin screenshot images in gh-pages index.md
### What is this PR for?
This PR is for updating screenshot images in `index.md`(gh-pages branch)
as #1089 merged
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1100
Ready for review.
---
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/1117
@astroshim Awesome! :+1:
I'm not sure where can be the proper place, it would be better users can
know this feature's existence since it's really useful. How about adding this
info
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/836
@Leemoonsoo Thanks. Awesome work indeed!
---
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/1106
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
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1100
[ZEPPELIN-1054] Improve "Credentials" UI
### What is this PR for?
Currently, users can add new their credential info for data source
authentication in Zeppelin "Credenti
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1088
[ZEPPELIN-1062] Get original InterpreterSetting when there is no change
### What is this PR for?
When we update interpreter property values, we edit some values and click
"save&qu
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1060
@prabhjyotsingh I see. Thanks for your suggestion. I addressed 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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1062
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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1076
@fabriziopandini Thanks for your contribution! Could you edit your
description with [PR
template](https://github.com/apache/zeppelin/blob/master/CONTRIBUTING.md#creating-a-pull-request)?
Just
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1064
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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1071
Yeah it works well. 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
701 - 800 of 866 matches
Mail list logo
