[GitHub] zeppelin issue #2268: [ZEPPELIN-2403] interpreter property widgets

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2268
  
If i list all combinations of widget-type in this PR,

| widget  | type |
| - | - |
| input  | **string**  |
| input | **number**  |
| **textarea** | string |
| **password** | password |
| **checkbox** | boolean |
| input | **url** |

As we can see, each combination can be uniquely identified by either widget 
or type. (bold font)
Unless there's big plan in the future add a lot of combinations of those, i 
think just keeping one field 'type' is enough to identify all possible 
combinations.



---
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 #2268: [ZEPPELIN-2403] interpreter property widgets

[tinkoff-dwh]

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2268
  
@Leemoonsoo 
first three comments

...
I think it's not complicated. IMO, it's the part we should design carefully 
since it's hard to change (backward compatibility)
...
widget means UI, and type defines their actual value types. Sometime they 
might be mixed together, but usually not.


---
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 #2322: [ZEPPELIN-2502] RemoteInterpreterServer hang forever d...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2322
  
Merge to master and branch-0.7 if no further comment


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this 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 #2268: [ZEPPELIN-2403] interpreter property widgets

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2268
  
> the separation discussed above in the comments

maybe i missed, @tinkoff-dwh could you point out the 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.
---

[GitHub] zeppelin issue #2227: [ZEPPELIN-2359] Support Spell as Display

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2227
  
Hi @echarles. Sorry for late comment. 

I agree it's quite hard to implement. Since `InterpreterOutput` class is 
widely used.

1. We need to add a variable to `RemoteInterpreterContext` which is a 
thrift generated class to pass   currently available spell magics so that 
interpreter can use it for their `InterpreterOutput`

2. Since InterpreterOutput usage depends on interpreter type, we might use 
static, synchronized variable in `InterpreterOutput` both sides in 
`ZeppelinServer` and `Interpreter`.

This is what i am thinking about.


---
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 #2349: [ZEPPELIN-2214] Set npm installer default npm registry

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2349
  
@necosta Thanks for quick updating! 

I have one more question.  **Is there a proxy option for npm packages? (not 
npm itself)**
Since if we an enable helium package, it will download specified (required) 
npm packages. 


---
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-2573) Improve Navbar

[Hoon Park (JIRA)]

Hoon Park created ZEPPELIN-2573:
---

 Summary: Improve Navbar
 Key: ZEPPELIN-2573
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2573
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Hoon Park


Navbar has too thick fonts and has small height relatively.



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

[GitHub] zeppelin issue #2352: [ZEPPELIN-2570] fix: indistinguishable directory icon ...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2352
  
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 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 #2352: [ZEPPELIN-2570] fix: indistinguishable directory icon ...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2352
  
appveyor failed. but irrelevant.


---
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 #2323: [ZEPPELIN-2411] Improve Table

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2323
  
GTM. Thanks @1ambda for great improvement.

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 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 #2347: [Bug Fix][ZEPPELIN-2554] sql parser fix (backslash)

[felixcheung]

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/2347
  
hmm, I see, 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 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 #2352: [ZEPPELIN-2570] fix: indistinguishable directory icon ...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2352
  
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 #2125: [ZEPPELIN-2222] Add Network Visualization

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2125
  
@conker84 Hi, I have a question. I'm not sure but classes under 
org.apache.zeppelin.interpreter.graph is used only for testing it. Can you 
verify it? If it does, can you move these classes under test?


---
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 #2347: [Bug Fix][ZEPPELIN-2554] sql parser fix (backslash)

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2347
  
@felixcheung  +1 for defaulting to the single query.

And for all of your questions answer is yes.

![1845](https://cloud.githubusercontent.com/assets/674497/21741685/1cbfb62e-d504-11e6-92c5-0e5a52436ae5.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.
---

[GitHub] zeppelin issue #2125: [ZEPPELIN-2222] Add Network Visualization

[conker84]

Github user conker84 commented on the issue:

https://github.com/apache/zeppelin/pull/2125
  
No news?


---
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 #2351: [ZEPPELIN-2544] clean task doesn't work in zeppelin-we...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2351
  
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 #2347: [Bug Fix][ZEPPELIN-2554] sql parser fix (backslash)

[felixcheung]

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/2347
  
Perhaps multiple queries was the reason we tried to parse the text (we 
really need to document these things better) - though I'm not sure how it would 
work exactly? Do you get multiple table in result if there are multiple queries 
in one paragraph? Does it even handle the multiple results correctly since that 
was added after JDBC interpreter is implemented?

In any case I do think it is much cleaner not to mess with the content.

Perhaps default to single query with a switch to fallback to old code and 
see if we get any feedback on this.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your 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 #932: Replace CXF with Jersey2 [ZEPPELIN-903]

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/932
  
@sohaibiftikhar Sure, I didn't test it yet as I had a talk in ApacheCon 
last Wednesday. I'll handle it soon.


---
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 #2341: ZEPPELIN-2543: Add ability to change the log level at ...

[karuppayya]

Github user karuppayya commented on the issue:

https://github.com/apache/zeppelin/pull/2341
  
I renamed my repo from incubator-zeppelin to zeppelin, and  force pushed a 
commit.
Then Jenkins started running the build.(Not sure if it was the rename that 
made it work)
One of the build 
[job](https://s3.amazonaws.com/archive.travis-ci.org/jobs/233987208/log.txt?X-Amz-Expires=30=20170519T142353Z=AWS4-HMAC-SHA256=AKIAJRYRXRSVGNKPKO5A/20170519/us-east-1/s3/aws4_request=host=7771d2f7d106140e0734a766653da48db3fd1be63e5cb88543c16e9fcace9e66)
 failed(timed out). Seems not relevant to my change.




---
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 #2326: [ZEPPELIN-2519] Disable watchers not in viewport

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2326
  
Your travis job failed at 

```
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 125.713 sec 
- in org.apache.zeppelin.integration.AuthenticationIT

Results :

Tests in error: 
  InterpreterIT.testShowDescriptionOnInterpreterCreate:69 » 
ElementNotVisible El...

Tests run: 23, Failures: 0, Errors: 1, Skipped: 0
```

- 
https://s3.amazonaws.com/archive.travis-ci.org/jobs/233893650/log.txt?X-Amz-Expires=30=20170519T140437Z=AWS4-HMAC-SHA256=AKIAJRYRXRSVGNKPKO5A/20170519/us-east-1/s3/aws4_request=host=528cbb815c291c20ab8f4a2418e762fee0d63d63af8cbf652a1262ce8dd2ef9a


---
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 #2354: Allow group/role based authentication using LdapRealm ...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2354
  
\cc @khalidhuseynov 


---
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 #2354: Allow group/role based authentication using Lda...

[sohaibiftikhar]

GitHub user sohaibiftikhar opened a pull request:

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

Allow group/role based authentication using LdapRealm [ZEPPELIN-2539]

### What is this PR for?
Currently allowing authentication for selected roles/groups of an LDAP 
realm is not possible. The LDAPRealm allows for mapping of roles to groups but 
only allows authorization on URLs with respect to groups. No group based checks 
are carried out during authentication. This PR allows for group based 
authentication using LdapRealm.

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

### Todos
* [ ] - Merge #932 - This PR also merges changes from 932 so that needs to 
be merged first.

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

### How should this be tested?
Build and configure `shiro.ini` to use the LdapRealm and verify that the 
realm works as before along with the added functionality of allowing only 
certain user groups for authentication if the `allowedRolesForAuthentication` 
config is set in the init. If this configuration is absent authentication 
should work as before without verifying roles. A sample shiro.ini is pasted 
here for testing purposes.

```
[main]
ldapRealm = org.apache.zeppelin.realm.LdapRealm
ldapRealm.userDnTemplate = uid={0},ou=people,dc=my-company,dc=net
ldapRealm.searchBase = dc=my-company,dc=net
ldapRealm.userSearchBase = ou=people,dc=my-company,dc=net
ldapRealm.groupSearchBase = ou=groups,dc=my-company,dc=net
ldapRealm.contextFactory.url = ldaps://auth.my-company.net:636
ldapRealm.contextFactory.authenticationMechanism = simple
ldapRealm.userObjectClass = posixAccount
ldapRealm.groupObjectClass = posixGroup
ldapRealm.authorizationEnabled = true
ldapRealm.memberAttribute = memberUid

ldapRealm.memberAttributeValueTemplate=uid={0},ou=people,dc=my-company,dc=net
ldapRealm.rolesByGroup = GLOBAL_ADMINS:admin,HKG_USERS:user
ldapRealm.allowedRolesForAuthentication = admin,user
ldapRealm.userSearchAttributeName = uid
sessionManager = org.apache.shiro.web.session.mgt.DefaultWebSessionManager
shiro.loginUrl = /api/login
securityManager.sessionManager = $sessionManager
securityManager.sessionManager.globalSessionTimeout = 8640
securityManager.realms = $ldapRealm

[urls]
/api/version = anon
/api/login = authc
/api/login/logout = authc
/** = authc, roles[admin,user]
```

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? Y (documentation updated in PR)


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

$ git pull https://github.com/sohaibiftikhar/zeppelin ldaprealm

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

https://github.com/apache/zeppelin/pull/2354.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 #2354


commit 9eef80cb71bd7f456145830eca59a635b4627b83
Author: Eric Charles 
Date:   2016-05-30T15:50:51Z

Replace CXF with Jersey2

commit dbac7d9cafc9d8496455b382949106fd94b9fc65
Author: Eric Charles 
Date:   2016-05-30T15:55:37Z

Fix code style

commit d149a728eba1cbc2fd7ae2ee016cb71510286279
Author: Eric Charles 
Date:   2016-05-30T16:13:53Z

Ensure dependency convergence

commit 99e45025b3a829b91b4532ea5dbba68ad7aa77b5
Author: Eric Charles 
Date:   2016-06-02T09:21:39Z

Merge branch 'master' into jersey2

commit a7b7a871c9627721e3ddfa6469aa670f08f87bc0
Author: Eric Charles 
Date:   2016-06-02T11:27:41Z

Remove remaining jersey1 dep

commit f25b695b2c9ee1343a9e59a2a65584ac95c79a6f
Author: Eric Charles 
Date:   2016-06-14T09:47:56Z

Merge branch 'master' into jersey2

commit 326819d0bbf89d30b1fcf9cdd2dd20c1e11e7769
Author: Eric Charles 
Date:   2016-08-02T05:53:35Z

Merge branch 'master' into jersey2

Conflicts:

zeppelin-server/src/main/java/org/apache/zeppelin/server/ZeppelinServer.java

commit 82d98672f2dc230e60b1dc2effbb6bfe83183f21
Author: Eric Charles 
Date:   2016-08-02T11:39:40Z

merge with master

commit 587d3660a8857c169b7df411c43b2988ef21de8b
Author: Eric Charles 
Date:   2016-08-02T11:56:34Z

Document jersey 2 license

commit 7dafe84131d50659bdbd1b79efc622132644b574
Author: Eric Charles 
Date:   2016-08-05T12:49:32Z

Merge branch 'master' into jersey2

Conflicts:

zeppelin-server/src/test/java/org/apache/zeppelin/socket/TestHttpServletRequest.java

commit 0634977a896ea63b3b3a0d48716fa74761aa61bd
Author: Eric 

[GitHub] zeppelin issue #932: Replace CXF with Jersey2 [ZEPPELIN-903]

[sohaibiftikhar]

Github user sohaibiftikhar commented on the issue:

https://github.com/apache/zeppelin/pull/932
  
@jongyoul I wish to open a dependent pull request for review. Is it 
possible to merge this branch if everything is working fine.


---
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 #2353: missing try catch

[cloverhearts]

GitHub user cloverhearts opened a pull request:

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

missing try catch

### What is this PR for?
Currently we can not build on branch-0.7
The cause is a missed try catch.
So, I fixed this part.

### What type of PR is it?
Hot Fix

### 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/cloverhearts/zeppelin missing-try-catch

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

https://github.com/apache/zeppelin/pull/2353.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 #2353


commit 8a9ea5ce79cca0a7909fd2b6b6242fd3a0b272d4
Author: CloverHearts 
Date:   2017-05-19T10:24:31Z

missing try catch




---
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-2572) Select multiple paragraphs for running, deleting, moving, etc

[Lucas Partridge (JIRA)]

Lucas Partridge created ZEPPELIN-2572:
-

 Summary: Select multiple paragraphs for running, deleting, moving, 
etc
 Key: ZEPPELIN-2572
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2572
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Lucas Partridge
Priority: Minor


If each paragraph had a checkbox the user could select several paragraphs by 
ticking their checkboxes. Then group actions could be applied to the selected 
paragraphs, such as:
delete all
run all
clone all to a new notebook, 
move all to top (or bottom) of the current notebook
etc.



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

[jira] [Created] (ZEPPELIN-2571) Add a "Run to here" option on paragraphs

[Lucas Partridge (JIRA)]

Lucas Partridge created ZEPPELIN-2571:
-

 Summary: Add a "Run to here" option on paragraphs
 Key: ZEPPELIN-2571
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2571
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Lucas Partridge
Priority: Minor


Please can we add to a paragraph's settings menu the ability to 'Run to this 
paragraph'? This would then cause all paragraphs in the notebook to be executed 
in order up to and including the current paragraph.

Motivation:
When I'm prototyping I often end up with lots of paragraphs at the top of the 
notebook that I want to keep, then a block of empty paragraphs to provide some 
visual separation, and finally a set of paragraphs with temporary stuff for 
testing which I may or may not want to keep.

I don't expect the paragraphs in this last block to work so the 'Run all 
paragraphs' is pretty useless to me. I just want to run to the end of the last 
paragraph in the block of paragraphs I want to keep. At the moment I'm forced 
to run all the 'good' paragraphs manually one by one, which is pretty tedious 
and also error-prone because it's easy to skip a paragraph by mistake.



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

[GitHub] zeppelin pull request #2326: [ZEPPELIN-2519] Disable watchers not in viewpor...

[vipul1409]

GitHub user vipul1409 reopened a pull request:

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

[ZEPPELIN-2519] Disable watchers not in viewport

### What is this PR for?
Currently all the watchers are enabled by default. I came across this 
github project https://github.com/wix/angular-viewport-watch to disable 
watchers not in viewport. This reduces number of watchers in notebooks with 
large number of paragraphs.


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

### Todos


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

### How should this be tested?
Outline the steps to test the PR here.

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update?
Not sure of this part. This is under MIT license. [Project 
link](https://github.com/wix/angular-viewport-watch)

* 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/vipul1409/zeppelin ZEPPELIN-2519

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

https://github.com/apache/zeppelin/pull/2326.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 #2326


commit 329e33a27b28b494f739c0d569bb4ea752e9044a
Author: vipulm 
Date:   2017-05-09T15:29:21Z

Disable watchers not in viewport

commit 71425782202f57a41b41f743f6e2c0c3b1b526e8
Author: vipulm 
Date:   2017-05-09T17:16:17Z

Trigger notification

commit d698d066d186b9c3c2b0b469632c4cadf5360320
Author: vipulm 
Date:   2017-05-10T06:18:34Z

Add license file

commit 99b19a5ee018d47bc7d076f6688ef102918debc6
Author: vipulm 
Date:   2017-05-11T05:51:00Z

Move pacakg to npm

commit 175dd1768c554e97d646ed08ccdc52eba8395b06
Author: vipulm 
Date:   2017-05-16T05:44:10Z

Merge master

commit b982db4915176b718f561838c3a7163831367408
Author: vipulm 
Date:   2017-05-19T05:44:48Z

Trigger build




---
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 #2326: [ZEPPELIN-2519] Disable watchers not in viewpor...

[vipul1409]

Github user vipul1409 closed the pull request at:

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


---
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 #2348: ZEPPELIN-2555: Run all paragraphs API does not run all...

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2348
  
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.
---