+1 on quality and stabilization.
I'm not sure if releasing as preview or calling it unstable fits with the ASF
release process though.
Other projects have code freeze, RC (and longer RC iteration time) etc. - do we
think those will help improve quality when the release is finally cut?
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2161
I tested two scenarios that you described and both(turn on & off Shiro) are
working well.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2163
I rebased but failed again in Selenium test. All test cases that I added
passed in my local but it's failed in here. Seem I need to do something more to
avoid this..
---
If your project is
Github user tinkoff-dwh closed the pull request at:
https://github.com/apache/zeppelin/pull/2112
---
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 tinkoff-dwh reopened a pull request:
https://github.com/apache/zeppelin/pull/2112
[ZEPPELIN-2228] precode for SparkRInterpreter
### What is this PR for?
Added parameter zeppelin.pyspark.precode to SparkRInterpreter. This is
snippet of code which executes when
Github user tinkoff-dwh closed the pull request at:
https://github.com/apache/zeppelin/pull/2085
---
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 tinkoff-dwh closed the pull request at:
https://github.com/apache/zeppelin/pull/2134
---
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 tinkoff-dwh reopened a pull request:
https://github.com/apache/zeppelin/pull/2085
[ZEPPELIN-1999] get interpreter property with replaced context parameters
### What is this PR for?
Adds posibility to use context parameters (types: String.class,
Double.class,
GitHub user tinkoff-dwh reopened a pull request:
https://github.com/apache/zeppelin/pull/2134
[ZEPPELIN-2257] notification about incompleteness of data
### What is this PR for?
Added notification about exceeding the limit in the result.
### What type of PR is it?
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2158
@Leemoonsoo
it works, thx!
---
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 tinkoff-dwh reopened a pull request:
https://github.com/apache/zeppelin/pull/2158
[ZEPPELIN-2279] excluded comments from SQL
### What is this PR for?
Exclusion comments (single-, multiline) from queries before execution.
Comments don't need to execute query and
Github user tinkoff-dwh closed the pull request at:
https://github.com/apache/zeppelin/pull/2158
---
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 tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2158
@felixcheung
example in jira
---
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 khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/2161
@anthonycorbacho thanks for the feedback, addressed them above. Let me know
if there's something else and if it works fine for you.
Also would be nice if other members could
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/2166
Thank you for the contribution.
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
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2158
could you elaborate on what errors would come from comment in SQL?
generally we should avoid trying to pre-parse the paragraph text since we
don't necessarily know the SQL dialect the
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1934
---
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 zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2139
I am afraid not, ssh need keystore file which is host dependent.
---
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
Strongly +1 for adding system test for different interpreter modes and focus on
bug fixing than new features. I do heard from some users complain about the
bugs of zeppelin major release. A stabilized release is very necessary for
community.
Best Regard,
Jeff Zhang
From: moon soo Lee
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2158
I fixed Jenkins build command the problem taking wrong commit hash when
it's got merge commit.
Now Jenkins will take correct commits. @tinkoff-dwh Could you try close /
re-open this PR and
GitHub user Leemoonsoo reopened a pull request:
https://github.com/apache/zeppelin/pull/2169
[CI-TEST] Jenkins build script test
Jenkins build script test with organization repository.
Won't be merged.
You can merge this pull request into a Git repository by running:
$ git
Github user Leemoonsoo closed the pull request at:
https://github.com/apache/zeppelin/pull/2169
---
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 Leemoonsoo closed the pull request at:
https://github.com/apache/zeppelin/pull/2169
---
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 Leemoonsoo reopened a pull request:
https://github.com/apache/zeppelin/pull/2169
[CI-TEST] Jenkins build script test
Jenkins build script test with organization repository.
Won't be merged.
You can merge this pull request into a Git repository by running:
$ git
Github user Leemoonsoo closed the pull request at:
https://github.com/apache/zeppelin/pull/2169
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2150
I made a mistake. And updated the jenkins command again. @andreaTP Could
you close/reopen once more? :-)
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user Leemoonsoo reopened a pull request:
https://github.com/apache/zeppelin/pull/2169
[CI-TEST] Jenkins build script test
Jenkins build script test with organization repository.
Won't be merged.
You can merge this pull request into a Git repository by running:
$ git
Github user andreaTP commented on the issue:
https://github.com/apache/zeppelin/pull/2150
Done, let see the result!
---
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 andreaTP closed the pull request at:
https://github.com/apache/zeppelin/pull/2150
---
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 andreaTP reopened a pull request:
https://github.com/apache/zeppelin/pull/2150
[ZEPPELIN-2278] Env variable to configure Npm registry
### What is this PR for?
When deploying Zeppelin in private Cloud or within closed networks, it
happens that Npm Registry isn't
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2150
I updated Jenkins build command. @andreaTP can you close / reopen this PR?
Jenkins now will check https://travis-ci.org/nokia/zeppelin/builds/213131116
correctly.
---
If your project is set
Github user Leemoonsoo closed the pull request at:
https://github.com/apache/zeppelin/pull/2169
---
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 tinkoff-dwh closed the pull request at:
https://github.com/apache/zeppelin/pull/2134
---
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 tinkoff-dwh reopened a pull request:
https://github.com/apache/zeppelin/pull/2134
[ZEPPELIN-2257] notification about incompleteness of data
### What is this PR for?
Added notification about exceeding the limit in the result.
### What type of PR is it?
Github user tinkoff-dwh closed the pull request at:
https://github.com/apache/zeppelin/pull/2085
---
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 tinkoff-dwh reopened a pull request:
https://github.com/apache/zeppelin/pull/2085
[ZEPPELIN-1999] get interpreter property with replaced context parameters
### What is this PR for?
Adds posibility to use context parameters (types: String.class,
Double.class,
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/2169
[CI-TEST] Jenkins build script test
Jenkins build script test with organization repository.
Won't be merged.
You can merge this pull request into a Git repository by running:
$ git
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2150
Looks like Jenkins build script still does not handle contribution from
organization repository very well.
Let me try fix this.
---
If your project is set up for it, you can reply to this
Great to see discussion for 0.8.0.
List of features for 0.8.0 looks really good.
*Interpreter factory refactoring*
Interpreter layer supports various behavior depends on combination of
PerNote,PerUser / Shared,Scoped,Isolated. We'll need strong test cases for
each combination as a first step.
GitHub user tinkoff-dwh reopened a pull request:
https://github.com/apache/zeppelin/pull/2085
[ZEPPELIN-1999] get interpreter property with replaced context parameters
### What is this PR for?
Adds posibility to use context parameters (types: String.class,
Double.class,
Github user tinkoff-dwh closed the pull request at:
https://github.com/apache/zeppelin/pull/2085
---
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 andreaTP commented on the issue:
https://github.com/apache/zeppelin/pull/2150
no luck 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 this feature
enabled and wishes
Github user andreaTP closed the pull request at:
https://github.com/apache/zeppelin/pull/2150
---
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 andreaTP commented on the issue:
https://github.com/apache/zeppelin/pull/2150
@Leemoonsoo
rebased.
Unfortunately again failures on CI, this is on Jenkins side I guess
https://builds.apache.org/job/zeppelin-pull-request/580/console
this is spurious since travis
GitHub user andreaTP reopened a pull request:
https://github.com/apache/zeppelin/pull/2150
[ZEPPELIN-2278] Env variable to configure Npm registry
### What is this PR for?
When deploying Zeppelin in private Cloud or within closed networks, it
happens that Npm Registry isn't
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2158
@Leemoonsoo
fix it.
CI green, https://travis-ci.org/tinkoff-dwh/zeppelin/builds/213118918
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2167
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 tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2158
@Leemoonsoo
i rebase from master. because if merge then CI red (jenking ignore merge
commits).
---
If your project is set up for it, you can reply to this email and have your
reply
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2158
Looks like somehow this branch includes commits not part of this
contribution.
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/2161
/cc @anthonycorbacho @Leemoonsoo @AhyoungRyu plz help to review and test
this one
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2158
@Leemoonsoo
done
---
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 tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2134
CI green https://travis-ci.org/tinkoff-dwh/zeppelin/builds/213063178
---
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 sravan-s opened a pull request:
https://github.com/apache/zeppelin/pull/2168
[ZEPPELIN-1889] [FIX] Multiple groups in chart doesn't work
### What is this PR for?
Fix for multiple group in multi-bar chart
If any value is missing under any domain key in
Github user sravan-s closed the pull request at:
https://github.com/apache/zeppelin/pull/2160
---
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 felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2130
merging if no more 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 feature
enabled
Github user sravan-s closed the pull request at:
https://github.com/apache/zeppelin/pull/2160
---
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 sravan-s reopened a pull request:
https://github.com/apache/zeppelin/pull/2160
[ZEPPELIN-1889] Fill missing values to grouped data
### What is this PR for?
Fix for multiple group in multi-bar chart
If any value is missing under any domain key in stacked
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2139
is it possible to add tests for https?
---
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 sravan-s reopened a pull request:
https://github.com/apache/zeppelin/pull/2160
[ZEPPELIN-1889] Fill missing values to grouped data
### What is this PR for?
Fix for multiple group in multi-bar chart
If any value is missing under any domain key in stacked
Github user sravan-s closed the pull request at:
https://github.com/apache/zeppelin/pull/2160
---
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 sravan-s commented on the issue:
https://github.com/apache/zeppelin/pull/2160
Sorry, it's my mistake, I did a pull instead of rebase
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2099
@Remilito Thanks for great work!
LGTM and merge to master 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 user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/2161
yes, i think my fork was integrated with travis since i have the build here
https://travis-ci.org/khalidhuseynov/incubator-zeppelin/builds/212981024 . also
the branch was rebased today and
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2160
I checked Jenkins log for last commit 368a50e. And looks like Jenkins build
script somehow confused with 'merge' and handling it not very well. :-(
---
If your project is set up for it, you
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2161
Current jenkins script check only
https://travis-ci.org/khalidhuseynov/zeppelin/ not
https://travis-ci.org/khalidhuseynov/incubator-zeppelin/. Could you setup
travis with 'zeppelin'
Github user elek commented on the issue:
https://github.com/apache/zeppelin/pull/2166
Branch is rebased to apache/master and travis is enabled.
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2158
@tinkoff-dwh Thanks for contribution.
CI failure on exceeding timelimit has fixed on master branch. Can you try
rebase this branch and see if CI becomes green?
---
If your project is
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2133
@soralee can you rebase or merge master and see if ci becomes green?
---
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/2150
@andreaTP
Problem on CI just has fixed on master branch.
Could you try rebase or merge master branch and see if CI passes?
---
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/2161
Can you setup
[CI](http://zeppelin.apache.org/contribution/contributions.html#continuous-integration)
for you fork?
And then you'll need rebase this branch to include some fixes for
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2163
CI problem has fixed on master branch. Can you rebase and see if this PR
passes the tests?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2166
Tested and it works well.
Could you setup travis-ci for your fork and see if it passes the test?
Please take a look
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2162
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2162
I rebased to current master and CI becomes green!
Merge this PR to master and branch-0.7 as a hotfix while it significantly
reduce chance of failing 2nd and 3rd test matrix by timeout.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2162
@sravan-s Test failure
`NotebookTest.testAngularObjectRemovalOnInterpreterRestart:699` is already
addressed in the commit
Github user khalidhuseynov closed the pull request at:
https://github.com/apache/zeppelin/pull/2161
---
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
There are several pending visualization improvements/PRs that would be very
good to get them in as well.
From: Jongyoul Lee
Sent: Sunday, March 19, 2017 9:03:24 PM
To: dev; us...@zeppelin.apache.org
Subject: Roadmap for 0.8.0
Hi dev &
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2164
Tested and LGTM.
It fixes test failure on SELENIUM test matrix.
Merge to master as an hotfix.
---
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/zeppelin/pull/2164
---
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 khalidhuseynov reopened a pull request:
https://github.com/apache/zeppelin/pull/2161
[ZEPPELIN-1697] Fix multiuser ws connection for secondary ZeppelinHubRepo
storage
### What is this PR for?
This is to fix problem with ws connection that was introduced in 0.7.0
Github user Remilito commented on the issue:
https://github.com/apache/zeppelin/pull/2111
@jongyoul : https://github.com/apache/zeppelin/pull/2167 should help
---
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 Remilito commented on the issue:
https://github.com/apache/zeppelin/pull/2099
@Leemoonsoo : updated!
---
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 elek opened a pull request:
https://github.com/apache/zeppelin/pull/2166
[ZEPPELIN-2288] Fix Cross-Site WebSocket check
Change-Id: Iad87ebe0b5dd6bd67a12e47fe83fbd0e1e71bda9
### What is this PR for?
ZEPPELIN-173 implemented an optional check for the
GitHub user Remilito opened a pull request:
https://github.com/apache/zeppelin/pull/2167
[ZEPPELIN-2230] .travis.yml protecting against ambiguous commit range
### What is this PR for?
Following the revert of [](https://github.com/apache/zeppelin/pull/2111
) I added some
Elek, Marton created ZEPPELIN-2288:
--
Summary: Fix Cross-Site WebSocket check
Key: ZEPPELIN-2288
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2288
Project: Zeppelin
Issue Type: Bug
Github user dwhsys commented on the issue:
https://github.com/apache/zeppelin/pull/2145
@felixcheung @jongyoul ,
I want to discuss the problem of "false sense of security". I hope that
anyone who want to use "credentials feature" in enterprise solution will be
aware of low
Github user guicaro commented on the issue:
https://github.com/apache/zeppelin/pull/2141
Selenium tests are red in Travis but due to:
`SparkParagraphIT.testSqlSpark:185 » NoSuchElement Unable to locate
element: {"... `
Github user sravan-s commented on the issue:
https://github.com/apache/zeppelin/pull/2162
Hi,
Recently, I have been facing two issues in the CI
First one is CI getting timed out, which is getting addressed here
The other one is:
`
Github user guicaro commented on the issue:
https://github.com/apache/zeppelin/pull/2141
@AhyoungRyu Fixed the issue with my commits, big shoutout to @DrIgor for
helping resolve my issue! I also updated the tests (ex.
`testSingleDynamicFormSelectForm`,
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2134
![_jdbc](https://cloud.githubusercontent.com/assets/25951039/24098459/4ab4a646-0d8c-11e7-95bd-3360fa22a27c.png)
Yeah, make sense.
Jongyoul Lee 于2017年3月20日周一 下午7:21写道:
> Thanks for letting me know. I agree almost things we should develop.
> Personally, concerning refactoring it, I'm doing a bit with several PRs but
> we need to restructure InterpreterFactory. At first, list up all
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2098
Few things are left. Thus i'v just changed to WIP again. Sorry for
confusing.
- adding more `transformation.method` for columnar and drill-down charts:
`array:key`, `array:group`,
Thanks for letting me know. I agree almost things we should develop.
Personally, concerning refactoring it, I'm doing a bit with several PRs but
we need to restructure InterpreterFactory. At first, list up all issues and
make some groups and handle it. How do you think?
On Mon, Mar 20, 2017 at
Github user jongyoul closed the pull request at:
https://github.com/apache/zeppelin/pull/2165
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2165
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 wishes so, or
GitHub user jongyoul opened a pull request:
https://github.com/apache/zeppelin/pull/2165
[HOTFIX] Disabled to close interpreters when option is shared globally
### What is this PR for?
Avoid closing interpreter in shared mode
### What type of PR is it?
[Hot
GitHub user jongyoul opened a pull request:
https://github.com/apache/zeppelin/pull/2164
[HOTFIX] Disabled to close interpreters when option is shared globally
### What is this PR for?
Avoid closing interpreter in shared mode
### What type of PR is it?
[Hot
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2104
ping @felixcheung
---
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 andreaTP commented on the issue:
https://github.com/apache/zeppelin/pull/2150
probably you have a problem on Jenkins, Travis is currently building
without errors:
https://travis-ci.org/nokia/zeppelin
still this PR is marked as Failed...
---
If your project
GitHub user andreaTP reopened a pull request:
https://github.com/apache/zeppelin/pull/2150
[ZEPPELIN-2278] Env variable to configure Npm registry
### What is this PR for?
When deploying Zeppelin in private Cloud or within closed networks, it
happens that Npm Registry isn't
1 - 100 of 104 matches
Mail list logo