date:20161021

[GitHub] incubator-eagle pull request #541: EAGLE-648: Stream router does not work pr...

2016-10-21 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/541


---
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] [Commented] (EAGLE-648) Stream router does not work properly sometimes

2016-10-21 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/EAGLE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594346#comment-15594346
 ] 

ASF GitHub Bot commented on EAGLE-648:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/541


> Stream router does not work properly sometimes
> --
>
> Key: EAGLE-648
> URL: https://issues.apache.org/jira/browse/EAGLE-648
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> Stream router does not work properly when multiple policies use the same 
> input stream with the same partition definition. It is because stream router 
> bolt output maintains a map of the route specs, but the key of the map is 
> streamId + partition information. The monitor stream may override each other 
> if the streamId and partition are the same.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-660) Stream delete mongo implementation is not working

2016-10-21 Thread Garrett Li (JIRA)

Garrett Li created EAGLE-660:


 Summary: Stream delete mongo implementation is not working
 Key: EAGLE-660
 URL: https://issues.apache.org/jira/browse/EAGLE-660
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Garrett Li
Assignee: Garrett Li
 Fix For: v0.5.0


we are using name rather than streamId to delete stream, it is incorrect



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #547: EAGLE-660: Stream delete mongo implementa...

2016-10-21 Thread garrettlish

GitHub user garrettlish opened a pull request:

https://github.com/apache/incubator-eagle/pull/547

EAGLE-660: Stream delete mongo implementation is not working

we are using name rather than streamId to delete stream, it is incorrect, 
change it to use streamId

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

$ git pull https://github.com/garrettlish/incubator-eagle master

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

https://github.com/apache/incubator-eagle/pull/547.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 #547


commit a12613daddf74ebe0b4912bfd99cd2fef17f666c
Author: Xiancheng Li 
Date:   2016-10-21T08:04:50Z

EAGLE-660: Stream delete mongo implementation is not working




---
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] [Commented] (EAGLE-660) Stream delete mongo implementation is not working

2016-10-21 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/EAGLE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594424#comment-15594424
 ] 

ASF GitHub Bot commented on EAGLE-660:
--

GitHub user garrettlish opened a pull request:

https://github.com/apache/incubator-eagle/pull/547

EAGLE-660: Stream delete mongo implementation is not working

we are using name rather than streamId to delete stream, it is incorrect, 
change it to use streamId

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

$ git pull https://github.com/garrettlish/incubator-eagle master

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

https://github.com/apache/incubator-eagle/pull/547.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 #547


commit a12613daddf74ebe0b4912bfd99cd2fef17f666c
Author: Xiancheng Li 
Date:   2016-10-21T08:04:50Z

EAGLE-660: Stream delete mongo implementation is not working




> Stream delete mongo implementation is not working
> -
>
> Key: EAGLE-660
> URL: https://issues.apache.org/jira/browse/EAGLE-660
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> we are using name rather than streamId to delete stream, it is incorrect



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #547: EAGLE-660: Stream delete mongo implementa...

2016-10-21 Thread garrettlish

Github user garrettlish closed the pull request at:

https://github.com/apache/incubator-eagle/pull/547


---
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] incubator-eagle issue #547: EAGLE-660: Stream delete mongo implementation is...

2016-10-21 Thread RalphSu

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/547
  
close this one, will create another pr for 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.
---

[jira] [Commented] (EAGLE-660) Stream delete mongo implementation is not working

2016-10-21 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/EAGLE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594551#comment-15594551
 ] 

ASF GitHub Bot commented on EAGLE-660:
--

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/547
  
close this one, will create another pr for this.


> Stream delete mongo implementation is not working
> -
>
> Key: EAGLE-660
> URL: https://issues.apache.org/jira/browse/EAGLE-660
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> we are using name rather than streamId to delete stream, it is incorrect



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-660) Stream delete mongo implementation is not working

2016-10-21 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/EAGLE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594550#comment-15594550
 ] 

ASF GitHub Bot commented on EAGLE-660:
--

Github user garrettlish closed the pull request at:

https://github.com/apache/incubator-eagle/pull/547


> Stream delete mongo implementation is not working
> -
>
> Key: EAGLE-660
> URL: https://issues.apache.org/jira/browse/EAGLE-660
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> we are using name rather than streamId to delete stream, it is incorrect



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #548: EAGLE-660 : Stream delete mongo implement...

2016-10-21 Thread RalphSu

GitHub user RalphSu opened a pull request:

https://github.com/apache/incubator-eagle/pull/548

EAGLE-660 : Stream delete mongo implementation is not working


The streamDefiniton use streamId instead of name, while the delete stream 
use "name" to find and delete, this cause the delete stream failed.

Add and update stream is ok.

Reporter: Li, Garrett
Author: Li, Garrett
Reviewer: ralphsu

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

$ git pull https://github.com/RalphSu/incubator-eagle master

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

https://github.com/apache/incubator-eagle/pull/548.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 #548


commit fd3966d0405cb96ae356301d121dc6f0810f1e5b
Author: Ralph, Su 
Date:   2016-10-21T09:04:59Z

EAGLE-660 : Stream delete mongo implementation is not working

Reporter: Li, Garrett
Author: Li, Garrett
Reviewer: ralphsu




---
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] [Commented] (EAGLE-660) Stream delete mongo implementation is not working

2016-10-21 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/EAGLE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594553#comment-15594553
 ] 

ASF GitHub Bot commented on EAGLE-660:
--

GitHub user RalphSu opened a pull request:

https://github.com/apache/incubator-eagle/pull/548

EAGLE-660 : Stream delete mongo implementation is not working


The streamDefiniton use streamId instead of name, while the delete stream 
use "name" to find and delete, this cause the delete stream failed.

Add and update stream is ok.

Reporter: Li, Garrett
Author: Li, Garrett
Reviewer: ralphsu

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

$ git pull https://github.com/RalphSu/incubator-eagle master

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

https://github.com/apache/incubator-eagle/pull/548.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 #548


commit fd3966d0405cb96ae356301d121dc6f0810f1e5b
Author: Ralph, Su 
Date:   2016-10-21T09:04:59Z

EAGLE-660 : Stream delete mongo implementation is not working

Reporter: Li, Garrett
Author: Li, Garrett
Reviewer: ralphsu




> Stream delete mongo implementation is not working
> -
>
> Key: EAGLE-660
> URL: https://issues.apache.org/jira/browse/EAGLE-660
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> we are using name rather than streamId to delete stream, it is incorrect



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #548: EAGLE-660 : Stream delete mongo implement...

2016-10-21 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/548


---
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] incubator-eagle issue #547: EAGLE-660: Stream delete mongo implementation is...

2016-10-21 Thread RalphSu

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/547
  
See https://github.com/apache/incubator-eagle/pull/548


---
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] [Commented] (EAGLE-660) Stream delete mongo implementation is not working

2016-10-21 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/EAGLE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594561#comment-15594561
 ] 

ASF GitHub Bot commented on EAGLE-660:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/548


> Stream delete mongo implementation is not working
> -
>
> Key: EAGLE-660
> URL: https://issues.apache.org/jira/browse/EAGLE-660
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> we are using name rather than streamId to delete stream, it is incorrect



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-660) Stream delete mongo implementation is not working

2016-10-21 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/EAGLE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594571#comment-15594571
 ] 

ASF GitHub Bot commented on EAGLE-660:
--

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/547
  
See https://github.com/apache/incubator-eagle/pull/548


> Stream delete mongo implementation is not working
> -
>
> Key: EAGLE-660
> URL: https://issues.apache.org/jira/browse/EAGLE-660
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> we are using name rather than streamId to delete stream, it is incorrect



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-661) Status is wrongly shown as "INITIALIZED" when updating installed app's configuration

2016-10-21 Thread Hao Chen (JIRA)

Hao Chen created EAGLE-661:
--

 Summary: Status is wrongly shown as "INITIALIZED" when updating 
installed app's configuration
 Key: EAGLE-661
 URL: https://issues.apache.org/jira/browse/EAGLE-661
 Project: Eagle
  Issue Type: Bug
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


Status is wrongly shown as "INITIALIZED" when updating installed app's 
configuration



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-661) Status is wrongly shown as "INITIALIZED" when updating installed app's configuration

2016-10-21 Thread Hao Chen (JIRA)


 [ 
https://issues.apache.org/jira/browse/EAGLE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-661:
---
Assignee: Jilin, Jiang  (was: Hao Chen)

> Status is wrongly shown as "INITIALIZED" when updating installed app's 
> configuration
> 
>
> Key: EAGLE-661
> URL: https://issues.apache.org/jira/browse/EAGLE-661
> Project: Eagle
>  Issue Type: Bug
>Reporter: Hao Chen
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
>
> * Status is wrongly shown as "INITIALIZED" when updating installed app's 
> configuration
> * Should use "Save" instead of "Install" button when updating installed app's 
> configuration



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-661) Status is wrongly shown as "INITIALIZED" when updating installed app's configuration

2016-10-21 Thread Hao Chen (JIRA)


 [ 
https://issues.apache.org/jira/browse/EAGLE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-661:
---
Description: 
* Status is wrongly shown as "INITIALIZED" when updating installed app's 
configuration
* Should use "Save" instead of "Install" button when updating installed app's 
configuration

  was:Status is wrongly shown as "INITIALIZED" when updating installed app's 
configuration


> Status is wrongly shown as "INITIALIZED" when updating installed app's 
> configuration
> 
>
> Key: EAGLE-661
> URL: https://issues.apache.org/jira/browse/EAGLE-661
> Project: Eagle
>  Issue Type: Bug
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> * Status is wrongly shown as "INITIALIZED" when updating installed app's 
> configuration
> * Should use "Save" instead of "Install" button when updating installed app's 
> configuration



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-660) Stream delete mongo implementation is not working

2016-10-21 Thread Garrett Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/EAGLE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Garrett Li resolved EAGLE-660.
--
Resolution: Fixed

> Stream delete mongo implementation is not working
> -
>
> Key: EAGLE-660
> URL: https://issues.apache.org/jira/browse/EAGLE-660
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> we are using name rather than streamId to delete stream, it is incorrect



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-648) Stream router does not work properly sometimes

2016-10-21 Thread Garrett Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/EAGLE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Garrett Li resolved EAGLE-648.
--
Resolution: Fixed

> Stream router does not work properly sometimes
> --
>
> Key: EAGLE-648
> URL: https://issues.apache.org/jira/browse/EAGLE-648
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> Stream router does not work properly when multiple policies use the same 
> input stream with the same partition definition. It is because stream router 
> bolt output maintains a map of the route specs, but the key of the map is 
> streamId + partition information. The monitor stream may override each other 
> if the streamId and partition are the same.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-640) Publishment reload may introduce NPE

2016-10-21 Thread Garrett Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/EAGLE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Garrett Li resolved EAGLE-640.
--
Resolution: Fixed

> Publishment reload may introduce NPE
> 
>
> Key: EAGLE-640
> URL: https://issues.apache.org/jira/browse/EAGLE-640
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
>
> 2016-10-18 23:59:12.128 o.a.c.f.r.c.NodeCache [ERROR] Calling listener
> java.lang.NullPointerException
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertKafkaPublisher.update(AlertKafkaPublisher.java:78)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.onPublishChange(AlertPublisherImpl.java:164)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.runner.AlertPublisherBolt.onAlertPublishSpecChange(AlertPublisherBolt.java:109)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifyAlertPublishBolt$3(AbstractMetadataChangeNotifyService.java:102)
>  ~[stormjar.jar:?]
>   at java.util.ArrayList.forEach(ArrayList.java:1249) 
> ~[?:1.8.0_92-internal]
>   at 
> org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifyAlertPublishBolt(AbstractMetadataChangeNotifyService.java:102)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:132)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.config.ConfigBusConsumer.lambda$new$0(ConfigBusConsumer.java:44)
>  ~[stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:293)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:287)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92)
>  [stormjar.jar:?]
>   at 
> com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache.setNewData(NodeCache.java:284)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache.processBackgroundResult(NodeCache.java:252)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache.access$300(NodeCache.java:53)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache$3.processResult(NodeCache.java:111)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:730)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:516)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl$3.processResult(GetDataBuilderImpl.java:254)
>  [stormjar.jar:?]
>   at 
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561) 
> [stormjar.jar:?]
>   at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) 
> [stormjar.jar:?]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #549: Minor: Expose several async producer conf...

2016-10-21 Thread qingwen220

GitHub user qingwen220 opened a pull request:

https://github.com/apache/incubator-eagle/pull/549

Minor: Expose several async producer config



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

$ git pull https://github.com/qingwen220/incubator-eagle kafkaProducer

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

https://github.com/apache/incubator-eagle/pull/549.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 #549


commit 726154683e9b97f54cb088d46f946bcfc17e56dd
Author: Zhao, Qingwen 
Date:   2016-10-21T12:14:13Z

expose several async producer config




---
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] incubator-eagle pull request #549: Minor: Expose several async producer conf...

2016-10-21 Thread haoch

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/549#discussion_r84475410
  
--- Diff: 
eagle-security/eagle-security-hdfs-auditlog/src/main/resources/META-INF/providers/org.apache.eagle.security.auditlog.HdfsAuditLogAppProvider.xml
 ---
@@ -149,6 +149,31 @@
 serializer class Kafka message key
 
 
+
+dataSinkConfig.producerType
+dataSinkConfig.keySerializerClass
--- End diff --

Wrongly spelled `dataSinkConfig.producerType`


---
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] incubator-eagle pull request #549: Minor: Expose several async producer conf...

2016-10-21 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/549


---
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.
---

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #237

2016-10-21 Thread Apache Jenkins Server

The Apache Jenkins build system has built incubator-eagle-main (build #237) 
Status: Failure Check console output at 
https://builds.apache.org/job/incubator-eagle-main/237/ to view the 
results. Test Report is at: Test Result

[jira] [Created] (EAGLE-662) remove jarPath/mode from entity context

2016-10-21 Thread wujinhu (JIRA)

wujinhu created EAGLE-662:
-

 Summary: remove jarPath/mode from entity context
 Key: EAGLE-662
 URL: https://issues.apache.org/jira/browse/EAGLE-662
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


remove jarPath/mode from application entity context, because they may be 
changed by user after application is installed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #550: [EAGLE-662] remove jarPath/mode from enti...

2016-10-21 Thread wujinhu

GitHub user wujinhu opened a pull request:

https://github.com/apache/incubator-eagle/pull/550

[EAGLE-662] remove jarPath/mode from entity context



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

$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-662

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

https://github.com/apache/incubator-eagle/pull/550.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 #550


commit b0b610ad98665236ebe3467ace9cd98fdde30f12
Author: wujinhu 
Date:   2016-10-22T04:33:05Z

remove jarPath/mode from entity context




---
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] [Commented] (EAGLE-662) remove jarPath/mode from entity context

2016-10-21 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/EAGLE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15597136#comment-15597136
 ] 

ASF GitHub Bot commented on EAGLE-662:
--

GitHub user wujinhu opened a pull request:

https://github.com/apache/incubator-eagle/pull/550

[EAGLE-662] remove jarPath/mode from entity context



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

$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-662

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

https://github.com/apache/incubator-eagle/pull/550.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 #550


commit b0b610ad98665236ebe3467ace9cd98fdde30f12
Author: wujinhu 
Date:   2016-10-22T04:33:05Z

remove jarPath/mode from entity context




> remove jarPath/mode from entity context
> ---
>
> Key: EAGLE-662
> URL: https://issues.apache.org/jira/browse/EAGLE-662
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> remove jarPath/mode from application entity context, because they may be 
> changed by user after application is installed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #550: [EAGLE-662] remove jarPath/mode from enti...

2016-10-21 Thread haoch

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/550#discussion_r84570146
  
--- Diff: 
eagle-core/eagle-app/eagle-app-base/src/main/java/org/apache/eagle/app/service/ApplicationAction.java
 ---
@@ -70,13 +71,16 @@ public ApplicationAction(Application application, 
ApplicationEntity metadata, Co
 this.application = application;
 this.metadata = metadata;
 this.runtime = 
ExecutionRuntimeManager.getInstance().getRuntime(application.getEnvironmentType(),
 serverConfig);
-Map executionConfig = metadata.getConfiguration();
+Map executionConfig = new 
HashMap<>(metadata.getConfiguration());
 if (executionConfig == null) {
 executionConfig = Collections.emptyMap();
 }
 if (serverConfig.hasPath(MetricConfigs.METRIC_PREFIX_CONF)) {
 LOG.warn("Ignored sever config {} = {}", 
MetricConfigs.METRIC_PREFIX_CONF, 
serverConfig.getString(MetricConfigs.METRIC_PREFIX_CONF));
 }
+
+executionConfig.put("jarPath", metadata.getJarPath());
+executionConfig.put("mode", metadata.getMode().name());
--- End diff --

It may cause the jarPath added into configuration when installating, I 
think you should add only in `start` action.


---
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] [Commented] (EAGLE-662) remove jarPath/mode from entity context

2016-10-21 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/EAGLE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15597150#comment-15597150
 ] 

ASF GitHub Bot commented on EAGLE-662:
--

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/550#discussion_r84570146
  
--- Diff: 
eagle-core/eagle-app/eagle-app-base/src/main/java/org/apache/eagle/app/service/ApplicationAction.java
 ---
@@ -70,13 +71,16 @@ public ApplicationAction(Application application, 
ApplicationEntity metadata, Co
 this.application = application;
 this.metadata = metadata;
 this.runtime = 
ExecutionRuntimeManager.getInstance().getRuntime(application.getEnvironmentType(),
 serverConfig);
-Map executionConfig = metadata.getConfiguration();
+Map executionConfig = new 
HashMap<>(metadata.getConfiguration());
 if (executionConfig == null) {
 executionConfig = Collections.emptyMap();
 }
 if (serverConfig.hasPath(MetricConfigs.METRIC_PREFIX_CONF)) {
 LOG.warn("Ignored sever config {} = {}", 
MetricConfigs.METRIC_PREFIX_CONF, 
serverConfig.getString(MetricConfigs.METRIC_PREFIX_CONF));
 }
+
+executionConfig.put("jarPath", metadata.getJarPath());
+executionConfig.put("mode", metadata.getMode().name());
--- End diff --

It may cause the jarPath added into configuration when installating, I 
think you should add only in `start` action.


> remove jarPath/mode from entity context
> ---
>
> Key: EAGLE-662
> URL: https://issues.apache.org/jira/browse/EAGLE-662
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> remove jarPath/mode from application entity context, because they may be 
> changed by user after application is installed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #550: [EAGLE-662] remove jarPath/mode from enti...

2016-10-21 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/550


---
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] [Commented] (EAGLE-662) remove jarPath/mode from entity context

2016-10-21 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/EAGLE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15597260#comment-15597260
 ] 

ASF GitHub Bot commented on EAGLE-662:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/550


> remove jarPath/mode from entity context
> ---
>
> Key: EAGLE-662
> URL: https://issues.apache.org/jira/browse/EAGLE-662
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> remove jarPath/mode from application entity context, because they may be 
> changed by user after application is installed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-662) remove jarPath/mode from entity context

2016-10-21 Thread wujinhu (JIRA)


 [ 
https://issues.apache.org/jira/browse/EAGLE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

wujinhu closed EAGLE-662.
-
Resolution: Fixed

> remove jarPath/mode from entity context
> ---
>
> Key: EAGLE-662
> URL: https://issues.apache.org/jira/browse/EAGLE-662
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> remove jarPath/mode from application entity context, because they may be 
> changed by user after application is installed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #238

2016-10-21 Thread Apache Jenkins Server

The Apache Jenkins build system has built incubator-eagle-main (build #238) 
Status: Still Failing Check console output at 
https://builds.apache.org/job/incubator-eagle-main/238/ to view the 
results. Test Report is at: Test Result

[jira] [Created] (EAGLE-663) Build git head COMMITID into eagle package and display in web page aside eagle version

2016-10-21 Thread Hao Chen (JIRA)

Hao Chen created EAGLE-663:
--

 Summary: Build git head COMMITID into eagle package and display in 
web page aside eagle version
 Key: EAGLE-663
 URL: https://issues.apache.org/jira/browse/EAGLE-663
 Project: Eagle
  Issue Type: Bug
Reporter: Hao Chen
Assignee: Hao Chen


{code}
# Get git-head commit ID
COMMITID=`git rev-parse HEAD`
# Get current maven version
VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}' 
--non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
DATE=`date`

# Generate 
classes/assets/build-version.json
# Access as static resource
/build-version.json

{
version: "$VERSION"
commit: "$COMMITID"
date: "$DATE"
}
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-663) Build git head COMMITID into eagle package and display in web page aside eagle version

2016-10-21 Thread Hao Chen (JIRA)


 [ 
https://issues.apache.org/jira/browse/EAGLE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-663:
---
Description: 
{code}
# Get git-head commit ID
COMMITID=`git rev-parse HEAD`
# Get current maven version
VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}' 
--non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
DATE=`date`

# Generate 
classes/assets/build-version.json
# Access as static resource
/build-version.json

{
version: "$VERSION"
commit: "$COMMITID"
compiled: "$DATE, MacOSX, 1.8.0_74-b02"
}
{code}

  was:
{code}
# Get git-head commit ID
COMMITID=`git rev-parse HEAD`
# Get current maven version
VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}' 
--non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
DATE=`date`

# Generate 
classes/assets/build-version.json
# Access as static resource
/build-version.json

{
version: "$VERSION"
commit: "$COMMITID"
date: "$DATE"
}
{code}


> Build git head COMMITID into eagle package and display in web page aside 
> eagle version
> --
>
> Key: EAGLE-663
> URL: https://issues.apache.org/jira/browse/EAGLE-663
> Project: Eagle
>  Issue Type: Bug
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> {code}
> # Get git-head commit ID
> COMMITID=`git rev-parse HEAD`
> # Get current maven version
> VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}' 
> --non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
> DATE=`date`
> # Generate 
> classes/assets/build-version.json
> # Access as static resource
> /build-version.json
> {
> version: "$VERSION"
> commit: "$COMMITID"
> compiled: "$DATE, MacOSX, 1.8.0_74-b02"
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-663) Build git head COMMITID into eagle package and display in web page aside eagle version

2016-10-21 Thread Hao Chen (JIRA)


 [ 
https://issues.apache.org/jira/browse/EAGLE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-663:
---
Description: 
{code}
# Get git-head commit ID
COMMITID=`git rev-parse HEAD`

# Get current maven version
VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}' 
--non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
DATE=`date`

# Generate 
classes/assets/build-version.json
# Access as static resource
/build-version.json

{
version: "$VERSION"
commit: "$COMMITID"
built: "$, MacOSX, 1.8.0_74-b02"
}
{code}

  was:
{code}
# Get git-head commit ID
COMMITID=`git rev-parse HEAD`

# Get current maven version
VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}' 
--non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
DATE=`date`

# Generate 
classes/assets/build-version.json
# Access as static resource
/build-version.json

{
version: "$VERSION"
commit: "$COMMITID"
compiled: "$DATE, MacOSX, 1.8.0_74-b02"
}
{code}


> Build git head COMMITID into eagle package and display in web page aside 
> eagle version
> --
>
> Key: EAGLE-663
> URL: https://issues.apache.org/jira/browse/EAGLE-663
> Project: Eagle
>  Issue Type: Bug
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> {code}
> # Get git-head commit ID
> COMMITID=`git rev-parse HEAD`
> # Get current maven version
> VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}' 
> --non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
> DATE=`date`
> # Generate 
> classes/assets/build-version.json
> # Access as static resource
> /build-version.json
> {
> version: "$VERSION"
> commit: "$COMMITID"
> built: "$, MacOSX, 1.8.0_74-b02"
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-663) Build git head COMMITID into eagle package and display in web page aside eagle version

2016-10-21 Thread Hao Chen (JIRA)


 [ 
https://issues.apache.org/jira/browse/EAGLE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-663:
---
Description: 
{code}
# Get git-head commit ID
COMMITID=`git rev-parse HEAD`

# Get current maven version
VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}' 
--non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
DATE=`date`

# Generate 
classes/assets/build-version.json
# Access as static resource
/build-version.json

{
version: "$VERSION"
commit: "$COMMITID"
compiled: "$DATE, MacOSX, 1.8.0_74-b02"
}
{code}

  was:
{code}
# Get git-head commit ID
COMMITID=`git rev-parse HEAD`
# Get current maven version
VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}' 
--non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
DATE=`date`

# Generate 
classes/assets/build-version.json
# Access as static resource
/build-version.json

{
version: "$VERSION"
commit: "$COMMITID"
compiled: "$DATE, MacOSX, 1.8.0_74-b02"
}
{code}


> Build git head COMMITID into eagle package and display in web page aside 
> eagle version
> --
>
> Key: EAGLE-663
> URL: https://issues.apache.org/jira/browse/EAGLE-663
> Project: Eagle
>  Issue Type: Bug
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> {code}
> # Get git-head commit ID
> COMMITID=`git rev-parse HEAD`
> # Get current maven version
> VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}' 
> --non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
> DATE=`date`
> # Generate 
> classes/assets/build-version.json
> # Access as static resource
> /build-version.json
> {
> version: "$VERSION"
> commit: "$COMMITID"
> compiled: "$DATE, MacOSX, 1.8.0_74-b02"
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-663) Build git head COMMITID into eagle package and display in web page aside eagle version

2016-10-21 Thread Hao Chen (JIRA)


 [ 
https://issues.apache.org/jira/browse/EAGLE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-663:
---
Affects Version/s: v0.5.0
Fix Version/s: v0.5.0

> Build git head COMMITID into eagle package and display in web page aside 
> eagle version
> --
>
> Key: EAGLE-663
> URL: https://issues.apache.org/jira/browse/EAGLE-663
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> {code}
> # Get git-head commit ID
> COMMITID=`git rev-parse HEAD`
> # Get current maven version
> VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}' 
> --non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
> DATE=`date`
> # Generate 
> classes/assets/build-version.json
> # Access as static resource
> /build-version.json
> {
> version: "$VERSION"
> commit: "$COMMITID"
> built: "$, MacOSX, 1.8.0_74-b02"
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

39 matches

Mail list logo