[GitHub] zeppelin issue #2056: ZEPPELIN-2151. Add integration test for livy cancel ap...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2056
  
Even though test is not directly related to this PR
I have experienced some code change or additional test may break other 
test, because of resource consumption or other unexpected reason.

Once master branch CI fails, it'll impact all other pullrequest 
review/verification.

If it change is not super urgent, i suggest we first figure out CI problem 
and then merge this code after the 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
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2056: ZEPPELIN-2151. Add integration test for livy cancel ap...

[khalidhuseynov]

Github user khalidhuseynov commented on the issue:

https://github.com/apache/zeppelin/pull/2056
  
I also think those tests not related to this PR and can be handled in that 
separate issue, probably some resource note name was changed


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2056: ZEPPELIN-2151. Add integration test for livy cancel ap...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2056
  
CI continue fail in the same place. But this is not livy relevant, as I 
didn't change any code outside livy interpreter. I have created ticket 
ZEPPELIN-2155 for this 

```
Failed tests: 
  NotebookTest.testPublicPrivateNewNote:1173 expected:<2C[B7YJQ16]> but 
was:<2C[A45Z6X7]>
  NotebookTest.testAuthorizationRoles:759 expected: but was:
```


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (ZEPPELIN-2155) Flaky test: NotebookTest

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-2155:


 Summary: Flaky test: NotebookTest
 Key: ZEPPELIN-2155
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2155
 Project: Zeppelin
  Issue Type: Bug
Reporter: Jeff Zhang


https://travis-ci.org/zjffdu/zeppelin/jobs/204447551

{noformat}
Failed tests: 
  NotebookTest.testPublicPrivateNewNote:1173 expected:<2C[B7YJQ16]> but 
was:<2C[A45Z6X7]>
  NotebookTest.testAuthorizationRoles:759 expected: but was:
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ZEPPELIN-2154) Not work in the web dev mode if changing default port

[Sora Lee (JIRA)]

Sora Lee created ZEPPELIN-2154:
--

 Summary: Not work in the web dev mode if changing default port
 Key: ZEPPELIN-2154
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2154
 Project: Zeppelin
  Issue Type: Bug
  Components: front-end
Affects Versions: 0.8.0
Reporter: Sora Lee
Assignee: Sora Lee
Priority: Minor


If user change port variable (zeppelin.server.port), zeppelin doesn't work in 
web development. Thus currently user should change from custom port to default 
port (8080). It would be nice to fix because It's quite inconvenient.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [DISCUSS] Admin feature

[Jeff Zhang]

I think in authenticated mode, admin is necessary.  What admin should take
charge can be in the following 4 areas:

1.  Interpreter setting. Admin can control a template for each interpreter,
and each user's template extend this base template but can also customize
his own setting. Besides that, admin can control which user can use which
interpreter. Because some interpreter has some potential security issue, we
should not allow everyone to use it (like shell interpreter)
2.  Note and user management. Admin can control the permission of notes and
users.  Like which user can use which note.
3.  Job management.
4.  Not sure about helium. But I think admin should be responsible for
helium plugins because plugins are external code which could bring some
potential security issue.

Besides that I have 2 concerns:
1.  Is admin mandatory in shrio ? Is it possible that I enable shrio but no
admin is defined ?
2. Should zeppelin take care of these or integrate the authorization of
shiro and let shrio to take care of these ? e.g. We can treat interpreter
and note as resource of shiro, and let shiro to control their permission
and relationship.



Alec Lee 于2017年2月23日周四 下午1:23写道：

> We have multiple uses in our organization share same anonymous account,
> which will potentially cause the problems, we hope to have true
> authenticated mode.
>
> thanks
>
> AL
>
> On Feb 22, 2017, at 9:14 PM, Jongyoul Lee  wrote:
>
> Hi folks,
>
> Recently, I've heard some new feature assumed that it needed the admin
> account or similar role. But Apache Zeppelin doesn't have any admin feature
> like hiding/showing menu and settings. I want to know how community thinks
> about that feature.
>
> My first concern is that we have to consider two modes: anonymous and
> authenticated.
>
> Feel free to start the discussion on pros and cons.
>
> Regards,
> Jongyoul
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>
>
>

Re: [DISCUSS] Admin feature

[Alec Lee]

We have multiple uses in our organization share same anonymous account, which 
will potentially cause the problems, we hope to have true authenticated mode. 

thanks

AL
> On Feb 22, 2017, at 9:14 PM, Jongyoul Lee  wrote:
> 
> Hi folks,
> 
> Recently, I've heard some new feature assumed that it needed the admin 
> account or similar role. But Apache Zeppelin doesn't have any admin feature 
> like hiding/showing menu and settings. I want to know how community thinks 
> about that feature.
> 
> My first concern is that we have to consider two modes: anonymous and 
> authenticated.
> 
> Feel free to start the discussion on pros and cons.
> 
> Regards,
> Jongyoul
> 
> -- 
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net 

[GitHub] zeppelin pull request #1794: [WIP][MINOR][ZEPPELIN-804] Remove static method...

[jongyoul]

Github user jongyoul closed the pull request at:

https://github.com/apache/zeppelin/pull/1794


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #1794: [WIP][MINOR][ZEPPELIN-804] Remove static method...

[jongyoul]

GitHub user jongyoul reopened a pull request:

https://github.com/apache/zeppelin/pull/1794

[WIP][MINOR][ZEPPELIN-804] Remove static method for static initialization

### What is this PR for?
This is one of steps of ZEPPELIN-804 to change the way of registration of 
interpreter. This PR removes some static method and replace those code to use 
new mechanism


### What type of PR is it?
[Refactoring]

### Todos
* [ ] - Remove `public static void register(...)`

### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-804

### How should this be tested?
N/A

### Screenshots (if appropriate)
N/A

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jongyoul/zeppelin 
minor/remove-interpreter-register

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/1794.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1794






---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2057: ZEPPELIN-2057 InterpreterSettingManager for branch-0.7

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2057
  
Will merge it into 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 have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2057: ZEPPELIN-2057 InterpreterSettingManager for bra...

[jongyoul]

GitHub user jongyoul opened a pull request:

https://github.com/apache/zeppelin/pull/2057

ZEPPELIN-2057 InterpreterSettingManager for branch-0.7

### What is this PR for?
ZEPPELIN-2057 is already merged into master but it's conflicted when it 
merges into branch-0.7. 


### What type of PR is it?
[Refactoring]

### Todos
* [x] - Fix it to fit branch-0.7

### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-2057

### How should this be tested?
N/A

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jongyoul/zeppelin ZEPPELIN-2057-branch-0.7

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2057.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2057






---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1985: [ZEPPELIN-2075] Can't stop infinite `while` statement ...

[astroshim]

Github user astroshim commented on the issue:

https://github.com/apache/zeppelin/pull/1985
  
@FireArrow Note has permission in the zeppelin so if user doesn't have 
`write` permission on that note, user can't cancel job.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[DISCUSS] Admin feature

[Jongyoul Lee]

Hi folks,

Recently, I've heard some new feature assumed that it needed the admin
account or similar role. But Apache Zeppelin doesn't have any admin feature
like hiding/showing menu and settings. I want to know how community thinks
about that feature.

My first concern is that we have to consider two modes: anonymous and
authenticated.

Feel free to start the discussion on pros and cons.

Regards,
Jongyoul

-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

Re: [DISCUSS] Behaviour of Interpreter when it is restarted

[Jongyoul Lee]

Yes, we can set some roles by Shiro but what I mean is we didn't implement
role-based functions like hiding or showing some menu.

On Thu, Feb 23, 2017 at 12:17 PM, Prabhjyot Singh  wrote:

> Yes, agreed we need some components to manage lifecycle of interpreters.
>
>  > "I agree that we need to keep same behavior even though users restart
> in any place."
> I too agree we should have same behaviour.
>
>  > Thus we must not assume that "admin" exists.
> In Zeppelin we can do this https://github.com/apache/
> zeppelin/blob/master/conf/shiro.ini.template#L82 , and when this is
> enabled, that is the case which concerns me.
>
>
>
> On 22 February 2017 at 23:03, Jongyoul Lee  wrote:
>
>> Basically, I agree that we need to keep same behavior even though users
>> restart in any place. I don't have any preference between restarting all
>> processes and starting user's process but currently Zeppelin doesn't have
>> any "admin" feature and no concept like admin by default. Thus we must not
>> assume that "admin" exists. And in my opinion, we need to treat
>> "edit/delete" action as special cases because these are disruptive thus all
>> interpreters should be shutdown.
>>
>> And as Jeff mentioned - I'm not sure if this issue is related or not -,
>> we need some components to manage lifecycle of interpreters.
>>
>> On Wed, Feb 22, 2017 at 6:18 PM, Jeff Zhang  wrote:
>>
>>>
>>> I think we can combine scenario 2 and 3 if user click yes button on the
>>> popup window of whether you want to restart interpreter in scenario 3.
>>>
>>> Regarding the restarting scenario of 1,2,3, IMHO I think we don't need
>>> to differentiate them. Otherwise it might confuse users that restarting in
>>> different places have different behavior. Zeppelin as a notebook should not
>>> do too much assumption and do too much extra work implicitly for users, let
>>> user to control what they want to do.
>>>
>>> IMHO I think the behavior of restarting should be just restarting the
>>> current user's interpreter and don't affect other users. If it's admin
>>> perform the restarting operation in interpreter setting page, I also think
>>> we should not restart all the users' interpreters by default. Because I
>>> think the admin's intention of updating interpreter setting is just to
>>> update the interpreter setting so that all the users can use the latest
>>> interpreter setting (e.g. update SPARK_HOME in spark interpreter setting.
>>> For now everyone share the same interpreter setting, but in the long term I
>>> think everyone should has his own setting that extend from admin's setting.
>>> But this is another story, not related to this thread ), admin doesn't want
>>> to interrupt and close the current other users' active interpreters. Of
>>> course, this is just my biased thinking, some customer may indeed want to
>>> close all the interpreters when admin perform restarting operation. Then we
>>> can provide one configuration in zeppelin-site to allow user to do that,
>>> but by default I think we should not allow admin to close all users' active
>>> interpreter.
>>>
>>> Delete is a very special scenario among them, for now I think we can
>>> terminate all the interpreter processes when interpreter is deleted.
>>> Because after interpreter is deleted, there's no way to shutdown the
>>> interpreter in zeppelin for now. If we don't close and shutdown them, then
>>> that means resource leakage.
>>>
>>> Besides these, another thing I want to mention is that there's no
>>> dedicated component or concept in zeppelin to control lifecycle of
>>> interpreter. E.g. for now if user don't restart interpreter, his
>>> interpreter will be alive forever. This is almost unacceptable for
>>> enterprise usage.  I think we should have some component to do that work to
>>> manage the lifecycle of interpreter.
>>>
>>>
>>>
>>>
>>> Prabhjyot Singh 于2017年2月22日周三 下午4:17写道：
>>>
 This is WRT the PR that I've created
 https://github.com/apache/zeppelin/pull/2034.

 The issue that I want to discuss over here is how should an Interpreter
 behave when it is;
  - restarted from notebook
  - restarted from Interpreter setting page
  - edited from Interpreter setting page
  - deleted from Interpreter setting page


 Assuming Zeppelin is being used in Enterprise world, where not all user
 may
 have access to Zeppelin's Interpreter setting page, say only restricted
 user say "admin-group" have access to this page. Now when a restart,
 edit
 or delete action is performed from Interpreter setting page; any of this
 operation should terminate all the processes of that particular
 Interpreter. On the other hand if it is restarted from the notebook
 page by
 any User, then only process of that logged-in User should get affected.

 How do you guys think of it?

 --

 Warm Regards,

[GitHub] zeppelin issue #2049: [ZEPPELIN-1586][MINOR] add new line char before "[urls...

[anthonycorbacho]

Github user anthonycorbacho commented on the issue:

https://github.com/apache/zeppelin/pull/2049
  
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2049: [ZEPPELIN-1586][MINOR] add new line char before "[urls...

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2049
  
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 feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Behaviour of Interpreter when it is restarted

[Prabhjyot Singh]

Yes, agreed we need some components to manage lifecycle of interpreters.

 > "I agree that we need to keep same behavior even though users restart in
any place."
I too agree we should have same behaviour.

 > Thus we must not assume that "admin" exists.
In Zeppelin we can do this
https://github.com/apache/zeppelin/blob/master/conf/shiro.ini.template#L82
, and when this is enabled, that is the case which concerns me.



On 22 February 2017 at 23:03, Jongyoul Lee  wrote:

> Basically, I agree that we need to keep same behavior even though users
> restart in any place. I don't have any preference between restarting all
> processes and starting user's process but currently Zeppelin doesn't have
> any "admin" feature and no concept like admin by default. Thus we must not
> assume that "admin" exists. And in my opinion, we need to treat
> "edit/delete" action as special cases because these are disruptive thus all
> interpreters should be shutdown.
>
> And as Jeff mentioned - I'm not sure if this issue is related or not -, we
> need some components to manage lifecycle of interpreters.
>
> On Wed, Feb 22, 2017 at 6:18 PM, Jeff Zhang  wrote:
>
>>
>> I think we can combine scenario 2 and 3 if user click yes button on the
>> popup window of whether you want to restart interpreter in scenario 3.
>>
>> Regarding the restarting scenario of 1,2,3, IMHO I think we don't need to
>> differentiate them. Otherwise it might confuse users that restarting in
>> different places have different behavior. Zeppelin as a notebook should not
>> do too much assumption and do too much extra work implicitly for users, let
>> user to control what they want to do.
>>
>> IMHO I think the behavior of restarting should be just restarting the
>> current user's interpreter and don't affect other users. If it's admin
>> perform the restarting operation in interpreter setting page, I also think
>> we should not restart all the users' interpreters by default. Because I
>> think the admin's intention of updating interpreter setting is just to
>> update the interpreter setting so that all the users can use the latest
>> interpreter setting (e.g. update SPARK_HOME in spark interpreter setting.
>> For now everyone share the same interpreter setting, but in the long term I
>> think everyone should has his own setting that extend from admin's setting.
>> But this is another story, not related to this thread ), admin doesn't want
>> to interrupt and close the current other users' active interpreters. Of
>> course, this is just my biased thinking, some customer may indeed want to
>> close all the interpreters when admin perform restarting operation. Then we
>> can provide one configuration in zeppelin-site to allow user to do that,
>> but by default I think we should not allow admin to close all users' active
>> interpreter.
>>
>> Delete is a very special scenario among them, for now I think we can
>> terminate all the interpreter processes when interpreter is deleted.
>> Because after interpreter is deleted, there's no way to shutdown the
>> interpreter in zeppelin for now. If we don't close and shutdown them, then
>> that means resource leakage.
>>
>> Besides these, another thing I want to mention is that there's no
>> dedicated component or concept in zeppelin to control lifecycle of
>> interpreter. E.g. for now if user don't restart interpreter, his
>> interpreter will be alive forever. This is almost unacceptable for
>> enterprise usage.  I think we should have some component to do that work to
>> manage the lifecycle of interpreter.
>>
>>
>>
>>
>> Prabhjyot Singh 于2017年2月22日周三 下午4:17写道：
>>
>>> This is WRT the PR that I've created
>>> https://github.com/apache/zeppelin/pull/2034.
>>>
>>> The issue that I want to discuss over here is how should an Interpreter
>>> behave when it is;
>>>  - restarted from notebook
>>>  - restarted from Interpreter setting page
>>>  - edited from Interpreter setting page
>>>  - deleted from Interpreter setting page
>>>
>>>
>>> Assuming Zeppelin is being used in Enterprise world, where not all user
>>> may
>>> have access to Zeppelin's Interpreter setting page, say only restricted
>>> user say "admin-group" have access to this page. Now when a restart, edit
>>> or delete action is performed from Interpreter setting page; any of this
>>> operation should terminate all the processes of that particular
>>> Interpreter. On the other hand if it is restarted from the notebook page
>>> by
>>> any User, then only process of that logged-in User should get affected.
>>>
>>> How do you guys think of it?
>>>
>>> --
>>>
>>> Warm Regards,
>>>
>>> Prabhjyot Singh
>>>
>>
>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>



-- 

Warm Regards,

Prabhjyot Singh

[GitHub] zeppelin issue #2056: ZEPPELIN-2151. Add integration test for livy cancel ap...

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2056
  
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2015: [ZEPPELIN-2103] Unnecessary read to Helium regi...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/zeppelin/pull/2015


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2036: [ZEPPELIN-2135] Don't re-license jdbc/src/main/...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/zeppelin/pull/2036


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2052: [ZEPPELIN-2048] Can't run first paragraph when ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/zeppelin/pull/2052


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2056: ZEPPELIN-2151. Add integration test for livy ca...

[zjffdu]

GitHub user zjffdu reopened a pull request:

https://github.com/apache/zeppelin/pull/2056

ZEPPELIN-2151. Add integration test for livy cancel api

### What is this PR for?

Just add integration test for livy cancel api. Only do it for livy 0.3 as 
the cancel api is only available in livy 0.3


### What type of PR is it?
[ Improvement]

### Todos
* [ ] - Task

### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-2151

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-2151

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2056.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2056






---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2056: ZEPPELIN-2151. Add integration test for livy ca...

[zjffdu]

Github user zjffdu closed the pull request at:

https://github.com/apache/zeppelin/pull/2056


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (ZEPPELIN-2153) branch-0.7 not building - bower issue

[krish arunachalam thayappan (JIRA)]

krish arunachalam thayappan created ZEPPELIN-2153:
-

 Summary: branch-0.7 not building - bower issue  
 Key: ZEPPELIN-2153
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2153
 Project: Zeppelin
  Issue Type: Bug
  Components: build
Affects Versions: 0.7.0
 Environment: local
Reporter: krish arunachalam thayappan


I tried building the project on my local machine but I keep on running into 
this issue


[INFO] $ bower install --silent && grunt googlefonts
[ERROR] [{
[ERROR]   "id": "error",
[ERROR]   "level": "error",
[ERROR]   "data": {},
[ERROR]   "message": "this._config.registry.search.forEach is not a function",
[ERROR]   "stacktrace": "TypeError: this._config.registry.search.forEach is not 
a function\nat RegistryClient.initCache 
(/Users/pku700/Downloads/zeppelin-0.7.0/zeppelin-web/node_modules/bower/lib/node_modules/bower-registry-client/lib/lookup.js:149:34)\n
at RegistryClient._initCache 
(/Users/pku700/Downloads/zeppelin-0.7.0/zeppelin-web/node_modules/bower/lib/node_modules/bower-registry-client/Client.js:65:27)\n
at new RegistryClient 
(/Users/pku700/Downloads/zeppelin-0.7.0/zeppelin-web/node_modules/bower/lib/node_modules/bower-registry-client/Client.js:19:10)\n
at new PackageRepository 
(/Users/pku700/Downloads/zeppelin-0.7.0/zeppelin-web/node_modules/bower/lib/core/PackageRepository.js:19:28)\n
at new Manager 
(/Users/pku700/Downloads/zeppelin-0.7.0/zeppelin-web/node_modules/bower/lib/core/Manager.js:18:24)\n
at new Project 
(/Users/pku700/Downloads/zeppelin-0.7.0/zeppelin-web/node_modules/bower/lib/core/Project.js:21:21)\n
at install 
(/Users/pku700/Downloads/zeppelin-0.7.0/zeppelin-web/node_modules/bower/lib/commands/install.js:14:15)\n
at 
/Users/pku700/Downloads/zeppelin-0.7.0/zeppelin-web/node_modules/bower/lib/commands/index.js:33:28\n
at Promise.apply 
(/Users/pku700/Downloads/zeppelin-0.7.0/zeppelin-web/node_modules/bower/lib/node_modules/q/q.js:1165:26)\n
at Promise.promise.promiseDispatch 
(/Users/pku700/Downloads/zeppelin-0.7.0/zeppelin-web/node_modules/bower/lib/node_modules/q/q.js:788:41)"



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2056: ZEPPELIN-2151. Add integration test for livy cancel ap...

[felixcheung]

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/2056
  
looks good, hmm, but the livy 0.3 test is failing 
https://travis-ci.org/zjffdu/zeppelin/builds/204166190
and you are saying it's not related to this? shall we kick it off one more 
time to see?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2050: ZEPPELIN-2137 Changed "show line chart with focus" to ...

[felixcheung]

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/2050
  
great! thanks for the contribution.
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 and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (ZEPPELIN-2152) Binaries for a setup behind corp firewall and proxy

[Mathieu D (JIRA)]

Mathieu D created ZEPPELIN-2152:
---

 Summary: Binaries for a setup behind corp firewall and proxy
 Key: ZEPPELIN-2152
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2152
 Project: Zeppelin
  Issue Type: Wish
Affects Versions: 0.7.0
Reporter: Mathieu D


I'm currently deploying Zeppelin for a customer with corporate firewalls and 
proxies everywhere. 
Zeppelin fails at startup because of npm download.
It seems that proxy parameter at system level (http_proxy env variable) is not 
used when downloading npm.

Essentially, I would like to have a full standalone binary of zeppelin without 
any additional download at startup.

If this kind of additional download is unavoidable, Zeppelin startup script 
should at least follow the proxy setting.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2032: [ZEPPELIN-791] Build infra: move all RAT to root pom.x...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2032
  
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2051: [ZEPPELIN-1968] Added property to disable hive user im...

[gfalcone]

Github user gfalcone commented on the issue:

https://github.com/apache/zeppelin/pull/2051
  
@prabhjyotsingh right, didn't see 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 not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2037: [ZEPPELIN-2109][2110] Sortable Helium pkgs & Introduce...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2037
  
@Leemoonsoo Thanks for your feedback and sorry for my late response. I 
updated again as you said. 
 - overall looks

![record](https://cloud.githubusercontent.com/assets/10060731/23219544/aed35dc2-f962-11e6-869b-72dead09de96.gif)

 - buttons in header used to sort packages by type
https://cloud.githubusercontent.com/assets/10060731/23219552/b74a0bf4-f962-11e6-8b02-e23f5307c472.png;>




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2051: [ZEPPELIN-1968] Added property to disable hive user im...

[gfalcone]

Github user gfalcone commented on the issue:

https://github.com/apache/zeppelin/pull/2051
  
@prabhjyotsingh thank you for reviewing, just pushed the doc :) 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2050: ZEPPELIN-2137 Changed "show line chart with focus" to ...

[samthebest]

Github user samthebest commented on the issue:

https://github.com/apache/zeppelin/pull/2050
  
thanks @felixcheung  checks should be passing 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 and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2051: [ZEPPELIN-1968] Added property to disable hive user im...

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2051
  
This looks OK to me, can you add a line note on 
https://github.com/apache/zeppelin/blob/master/docs/interpreter/jdbc.md#apache-hive
 to update the documentation. 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2056: ZEPPELIN-2151. Add integration test for livy cancel ap...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2056
  
@felixcheung @prabhjyotsingh Please help review. CI failure is not relevant.

```
Failed tests: 
  NotebookTest.testPublicPrivateNewNote:1173 expected:<2C[A7GB62Y]> but 
was:<2C[8XKNFD4]>
  NotebookTest.testAuthorizationRoles:759 expected: but was:
```


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2056: ZEPPELIN-2151. Add integration test for livy ca...

[zjffdu]

GitHub user zjffdu opened a pull request:

https://github.com/apache/zeppelin/pull/2056

ZEPPELIN-2151. Add integration test for livy cancel api

### What is this PR for?

Just add integration test for livy cancel api. Only do it for livy 0.3 as 
the cancel api is only available in livy 0.3


### What type of PR is it?
[ Improvement]

### Todos
* [ ] - Task

### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-2151

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-2151

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2056.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2056


commit e8fc14987a3df9ba8c810997ae323be1f2aec1ff
Author: Jeff Zhang 
Date:   2017-02-22T11:59:47Z

ZEPPELIN-2151. Add integration test for livy cancel api




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (ZEPPELIN-2151) Add integration test for livy cancel api

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-2151:


 Summary: Add integration test for livy cancel api
 Key: ZEPPELIN-2151
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2151
 Project: Zeppelin
  Issue Type: Test
Affects Versions: 0.7.0
Reporter: Jeff Zhang
Assignee: Jeff Zhang
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2051: [ZEPPELIN-1968] Added property to disable hive user im...

[gfalcone]

Github user gfalcone commented on the issue:

https://github.com/apache/zeppelin/pull/2051
  
CI passed all the tests : https://travis-ci.org/gfalcone/zeppelin


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2055: [ZEPPELIN-1999] get interpreter property with r...

[tinkoff-dwh]

GitHub user tinkoff-dwh opened a pull request:

https://github.com/apache/zeppelin/pull/2055

[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, Float.class, Short.class,
Byte.class, Character.class, Boolean.class, Integer.class, Long.class, ) 
into property of interpreter.

### What type of PR is it?
Feature

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1999

### How should this be tested?
1. Add text with markers #{contextFieldNAme} (ex. #{noteId} or 
#{paragraphTitle}) to interpreter property value (or add new property of 
interpreter).
2. Get this property (getProperty(key)), markers should be replaced by 
context values

### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? yes


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tinkoff-dwh/zeppelin ZEPPELIN-1999

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2055.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2055


commit b5424b99988cc4e87bbb24252b383cb43268a756
Author: Tinkoff DWH 
Date:   2017-02-22T09:53:43Z

[ZEPPELIN-1999] get interpreter property with replaced context parameters




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2053: [ZEPPELIN-1964] Layout info is lost after refresh

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2053
  
Thanks @astroshim for fixing this!
Tested and it works well like below! LGTM :+1: 

![z_1964_a_check](https://cloud.githubusercontent.com/assets/8110458/23209270/f03b3acc-f93b-11e6-9b28-a4e375f6301e.gif)



---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Behaviour of Interpreter when it is restarted

[Jeff Zhang]

I think we can combine scenario 2 and 3 if user click yes button on the
popup window of whether you want to restart interpreter in scenario 3.

Regarding the restarting scenario of 1,2,3, IMHO I think we don't need to
differentiate them. Otherwise it might confuse users that restarting in
different places have different behavior. Zeppelin as a notebook should not
do too much assumption and do too much extra work implicitly for users, let
user to control what they want to do.

IMHO I think the behavior of restarting should be just restarting the
current user's interpreter and don't affect other users. If it's admin
perform the restarting operation in interpreter setting page, I also think
we should not restart all the users' interpreters by default. Because I
think the admin's intention of updating interpreter setting is just to
update the interpreter setting so that all the users can use the latest
interpreter setting (e.g. update SPARK_HOME in spark interpreter setting.
For now everyone share the same interpreter setting, but in the long term I
think everyone should has his own setting that extend from admin's setting.
But this is another story, not related to this thread ), admin doesn't want
to interrupt and close the current other users' active interpreters. Of
course, this is just my biased thinking, some customer may indeed want to
close all the interpreters when admin perform restarting operation. Then we
can provide one configuration in zeppelin-site to allow user to do that,
but by default I think we should not allow admin to close all users' active
interpreter.

Delete is a very special scenario among them, for now I think we can
terminate all the interpreter processes when interpreter is deleted.
Because after interpreter is deleted, there's no way to shutdown the
interpreter in zeppelin for now. If we don't close and shutdown them, then
that means resource leakage.

Besides these, another thing I want to mention is that there's no dedicated
component or concept in zeppelin to control lifecycle of interpreter. E.g.
for now if user don't restart interpreter, his interpreter will be alive
forever. This is almost unacceptable for enterprise usage.  I think we
should have some component to do that work to manage the lifecycle of
interpreter.




Prabhjyot Singh 于2017年2月22日周三 下午4:17写道：

> This is WRT the PR that I've created
> https://github.com/apache/zeppelin/pull/2034.
>
> The issue that I want to discuss over here is how should an Interpreter
> behave when it is;
>  - restarted from notebook
>  - restarted from Interpreter setting page
>  - edited from Interpreter setting page
>  - deleted from Interpreter setting page
>
>
> Assuming Zeppelin is being used in Enterprise world, where not all user may
> have access to Zeppelin's Interpreter setting page, say only restricted
> user say "admin-group" have access to this page. Now when a restart, edit
> or delete action is performed from Interpreter setting page; any of this
> operation should terminate all the processes of that particular
> Interpreter. On the other hand if it is restarted from the notebook page by
> any User, then only process of that logged-in User should get affected.
>
> How do you guys think of it?
>
> --
>
> Warm Regards,
>
> Prabhjyot Singh
>

[GitHub] zeppelin pull request #2028: [MINOR] Supported old note format in case of no...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/zeppelin/pull/2028


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2028: [MINOR] Supported old note format in case of not havin...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2028
  
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 if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #1794: [WIP][MINOR][ZEPPELIN-804] Remove static method...

[jongyoul]

GitHub user jongyoul reopened a pull request:

https://github.com/apache/zeppelin/pull/1794

[WIP][MINOR][ZEPPELIN-804] Remove static method for static initialization

### What is this PR for?
This is one of steps of ZEPPELIN-804 to change the way of registration of 
interpreter. This PR removes some static method and replace those code to use 
new mechanism


### What type of PR is it?
[Refactoring]

### Todos
* [ ] - Remove `public static void register(...)`

### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-804

### How should this be tested?
N/A

### Screenshots (if appropriate)
N/A

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jongyoul/zeppelin 
minor/remove-interpreter-register

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/1794.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1794


commit 71a2377cf2208137e55b3efbf26a12390d55a777
Author: Jongyoul Lee 
Date:   2016-12-22T18:05:42Z

Removed `public static void register(String name, String className)`

commit 67321c681f79c5b6052e3c62ce162ae5d5b5617f
Author: Jongyoul Lee 
Date:   2016-12-22T18:40:10Z

Remove commented code

commit 875e869015e7a1415d495f46c3e98faf1d83ad62
Author: Jongyoul Lee 
Date:   2016-12-22T18:54:51Z

Removed `register(String name, String group, String className, boolean 
defaultInterpreter)`
Removed `register(String name, String group, String className)`

commit 06147a7930c19b50d0c663f8fe40cac43f17eaf3
Author: Jongyoul Lee 
Date:   2016-12-24T18:35:33Z

Fixed interpreterOption to pass some tests

commit c505a78d5d724b466fe1e6f9652335470ecc5c5d
Author: Jongyoul Lee 
Date:   2017-01-20T16:22:00Z

Removed static logic from DevInterpreter in helium-dev

commit eb2c828f4469f6f87c6c56f184db389ebf573d90
Author: Jongyoul Lee 
Date:   2017-01-23T06:33:37Z

Removed static initialization code for all mock interpreters

commit e9dcf3ab8916e8174218e906d2256447782d8400
Author: Jongyoul Lee 
Date:   2017-01-23T06:34:05Z

Marked as deprecated in all Interpreter.register methods

commit cba3e02377280ed1cb727f2218296e3f1dbfd490
Author: Jongyoul Lee 
Date:   2017-01-23T11:20:00Z

Fixed test cases

commit d0ea3b3b24b107e9122fcb3de51ed486956b2244
Author: Jongyoul Lee 
Date:   2017-01-24T05:39:09Z

Fixed Test cases

commit 53abb6a0556e811defa8911218c2556da593ee9c
Author: Jongyoul Lee 
Date:   2017-02-22T07:04:33Z

Fixed some tests




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #1794: [WIP][MINOR][ZEPPELIN-804] Remove static method...

[jongyoul]

Github user jongyoul closed the pull request at:

https://github.com/apache/zeppelin/pull/1794


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2049: [ZEPPELIN-1586][MINOR] add new line char before "[urls...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2049
  
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1983: [ZEPPELIN-1808] disable shortcut key of window created...

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/1983
  
Hi @Leemoonsoo,
I opened two issue as your comment (#2045, #2054) so it would be nice if 
you could check some PRs. Furthermore this 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 and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2049: [ZEPPELIN-1586][MINOR] add new line char before "[urls...

[r-kamath]

Github user r-kamath commented on the issue:

https://github.com/apache/zeppelin/pull/2049
  
Good catch. 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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[DISCUSS] Behaviour of Interpreter when it is restarted

[Prabhjyot Singh]

This is WRT the PR that I've created
https://github.com/apache/zeppelin/pull/2034.

The issue that I want to discuss over here is how should an Interpreter
behave when it is;
 - restarted from notebook
 - restarted from Interpreter setting page
 - edited from Interpreter setting page
 - deleted from Interpreter setting page


Assuming Zeppelin is being used in Enterprise world, where not all user may
have access to Zeppelin's Interpreter setting page, say only restricted
user say "admin-group" have access to this page. Now when a restart, edit
or delete action is performed from Interpreter setting page; any of this
operation should terminate all the processes of that particular
Interpreter. On the other hand if it is restarted from the notebook page by
any User, then only process of that logged-in User should get affected.

How do you guys think of it?

-- 

Warm Regards,

Prabhjyot Singh

[GitHub] zeppelin issue #2043: [ZEPPELIN-2114] adding reload endpoint

[Remilito]

Github user Remilito commented on the issue:

https://github.com/apache/zeppelin/pull/2043
  
@AhyoungRyu: let me know if need me to enrich the new notebook-repositories 
doc. 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---