[jira] [Commented] (EAGLE-747) Add unit test for eagle-storage-base module
[ https://issues.apache.org/jira/browse/EAGLE-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650113#comment-15650113 ] ASF GitHub Bot commented on EAGLE-747: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/620 > Add unit test for eagle-storage-base module > --- > > Key: EAGLE-747 > URL: https://issues.apache.org/jira/browse/EAGLE-747 > Project: Eagle > Issue Type: Improvement >Reporter: Lingang Deng >Assignee: Lingang Deng > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #620: EAGLE-747 Add unit test for eagle-storage...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/620 --- 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-758) Add tuple log for spout & alert bolt
[ https://issues.apache.org/jira/browse/EAGLE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650058#comment-15650058 ] ASF GitHub Bot commented on EAGLE-758: -- Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/631 :-1: > Add tuple log for spout & alert bolt > > > Key: EAGLE-758 > URL: https://issues.apache.org/jira/browse/EAGLE-758 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > Without tuple log for spout & alert bolt, it is hard to troubleshoot event > missing issue, we don't know whether the spout/alert process issue or no > event come. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #631: EAGLE-758: Add tuple log for spout & alert bolt
Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/631 :-1: --- 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] (EAGLE-759) Policy detail support alert list
Jilin, Jiang created EAGLE-759: -- Summary: Policy detail support alert list Key: EAGLE-759 URL: https://issues.apache.org/jira/browse/EAGLE-759 Project: Eagle Issue Type: Improvement Reporter: Jilin, Jiang Assignee: Jilin, Jiang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-733) Add unit test for MetricSystem
[ https://issues.apache.org/jira/browse/EAGLE-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiJun Tang resolved EAGLE-733. -- Resolution: Fixed > Add unit test for MetricSystem > -- > > Key: EAGLE-733 > URL: https://issues.apache.org/jira/browse/EAGLE-733 > Project: Eagle > Issue Type: Sub-task >Reporter: JiJun Tang >Assignee: JiJun Tang >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-733) Add unit test for MetricSystem
[ https://issues.apache.org/jira/browse/EAGLE-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiJun Tang closed EAGLE-733. > Add unit test for MetricSystem > -- > > Key: EAGLE-733 > URL: https://issues.apache.org/jira/browse/EAGLE-733 > Project: Eagle > Issue Type: Sub-task >Reporter: JiJun Tang >Assignee: JiJun Tang >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-758) Add tuple log for spout & alert bolt
[ https://issues.apache.org/jira/browse/EAGLE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li resolved EAGLE-758. -- Resolution: Fixed > Add tuple log for spout & alert bolt > > > Key: EAGLE-758 > URL: https://issues.apache.org/jira/browse/EAGLE-758 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > Without tuple log for spout & alert bolt, it is hard to troubleshoot event > missing issue, we don't know whether the spout/alert process issue or no > event come. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-752) JPM statistic need remove jobType
[ https://issues.apache.org/jira/browse/EAGLE-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jilin, Jiang resolved EAGLE-752. Resolution: Fixed > JPM statistic need remove jobType > - > > Key: EAGLE-752 > URL: https://issues.apache.org/jira/browse/EAGLE-752 > Project: Eagle > Issue Type: Bug >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > > JPM statistic need remove jobType -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-733) Add unit test for MetricSystem
[ https://issues.apache.org/jira/browse/EAGLE-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650046#comment-15650046 ] ASF GitHub Bot commented on EAGLE-733: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/619 > Add unit test for MetricSystem > -- > > Key: EAGLE-733 > URL: https://issues.apache.org/jira/browse/EAGLE-733 > Project: Eagle > Issue Type: Sub-task >Reporter: JiJun Tang >Assignee: JiJun Tang >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #619: [EAGLE-733] Add unit test for MetricSyste...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/619 --- 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-758) Add tuple log for spout & alert bolt
[ https://issues.apache.org/jira/browse/EAGLE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650044#comment-15650044 ] ASF GitHub Bot commented on EAGLE-758: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/631 > Add tuple log for spout & alert bolt > > > Key: EAGLE-758 > URL: https://issues.apache.org/jira/browse/EAGLE-758 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > Without tuple log for spout & alert bolt, it is hard to troubleshoot event > missing issue, we don't know whether the spout/alert process issue or no > event come. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #631: EAGLE-758: Add tuple log for spout & aler...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/631 --- 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-758) Add tuple log for spout & alert bolt
[ https://issues.apache.org/jira/browse/EAGLE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650030#comment-15650030 ] ASF GitHub Bot commented on EAGLE-758: -- Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/631 For requirements "spout/alert process issue or no event come", please refer to storm metrics. > Add tuple log for spout & alert bolt > > > Key: EAGLE-758 > URL: https://issues.apache.org/jira/browse/EAGLE-758 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > Without tuple log for spout & alert bolt, it is hard to troubleshoot event > missing issue, we don't know whether the spout/alert process issue or no > event come. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #631: EAGLE-758: Add tuple log for spout & alert bolt
Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/631 For requirements "spout/alert process issue or no event come", please refer to storm metrics. --- 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 #631: EAGLE-758: Add tuple log for spout & alert bolt
Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/631 Overall, we really don't suggest to print `per-event` log anywhere for any big data application. --- 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-758) Add tuple log for spout & alert bolt
[ https://issues.apache.org/jira/browse/EAGLE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650022#comment-15650022 ] ASF GitHub Bot commented on EAGLE-758: -- Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/631 Overall, we really don't suggest to print `per-event` log anywhere for any big data application. > Add tuple log for spout & alert bolt > > > Key: EAGLE-758 > URL: https://issues.apache.org/jira/browse/EAGLE-758 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > Without tuple log for spout & alert bolt, it is hard to troubleshoot event > missing issue, we don't know whether the spout/alert process issue or no > event come. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-758) Add tuple log for spout & alert bolt
[
https://issues.apache.org/jira/browse/EAGLE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650017#comment-15650017
]
ASF GitHub Bot commented on EAGLE-758:
--
Github user haoch commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/631#discussion_r87141359
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/spout/SpoutOutputCollectorWrapper.java
---
@@ -103,7 +103,7 @@ public SpoutOutputCollectorWrapper(CorrelationSpout
spout,
*/
List convertedTuple = converter.convert(tuple);
if (convertedTuple == null) {
-LOG.warn("source data {} can't be converted to a stream,
ignore this message", tuple);
+LOG.debug("source data {} can't be converted to a stream,
ignore this message", tuple);
--- End diff --
For any `debug` logging, check with `if(LOG.isDebugEnabled())` before.
> Add tuple log for spout & alert bolt
>
>
> Key: EAGLE-758
> URL: https://issues.apache.org/jira/browse/EAGLE-758
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> Without tuple log for spout & alert bolt, it is hard to troubleshoot event
> missing issue, we don't know whether the spout/alert process issue or no
> event come.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle pull request #631: EAGLE-758: Add tuple log for spout & aler...
Github user haoch commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/631#discussion_r87141359
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/spout/SpoutOutputCollectorWrapper.java
---
@@ -103,7 +103,7 @@ public SpoutOutputCollectorWrapper(CorrelationSpout
spout,
*/
List convertedTuple = converter.convert(tuple);
if (convertedTuple == null) {
-LOG.warn("source data {} can't be converted to a stream,
ignore this message", tuple);
+LOG.debug("source data {} can't be converted to a stream,
ignore this message", tuple);
--- End diff --
For any `debug` logging, check with `if(LOG.isDebugEnabled())` before.
---
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-758) Add tuple log for spout & alert bolt
[ https://issues.apache.org/jira/browse/EAGLE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650004#comment-15650004 ] ASF GitHub Bot commented on EAGLE-758: -- GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/631 EAGLE-758: Add tuple log for spout & alert bolt Without tuple log for spout & alert bolt, it is hard to troubleshoot event missing issue, we don't know whether the spout/alert process issue or no event come. 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/631.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 #631 commit 6acf260e5ee44d2951987cb6dc1cca7f8213a6a4 Author: Xiancheng Li Date: 2016-11-09T06:54:30Z EAGLE-758: Add tuple log for spout & alert bolt > Add tuple log for spout & alert bolt > > > Key: EAGLE-758 > URL: https://issues.apache.org/jira/browse/EAGLE-758 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > Without tuple log for spout & alert bolt, it is hard to troubleshoot event > missing issue, we don't know whether the spout/alert process issue or no > event come. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #631: EAGLE-758: Add tuple log for spout & aler...
GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/631 EAGLE-758: Add tuple log for spout & alert bolt Without tuple log for spout & alert bolt, it is hard to troubleshoot event missing issue, we don't know whether the spout/alert process issue or no event come. 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/631.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 #631 commit 6acf260e5ee44d2951987cb6dc1cca7f8213a6a4 Author: Xiancheng Li Date: 2016-11-09T06:54:30Z EAGLE-758: Add tuple log for spout & alert bolt --- 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] (EAGLE-758) Add tuple log for spout & alert bolt
Garrett Li created EAGLE-758: Summary: Add tuple log for spout & alert bolt Key: EAGLE-758 URL: https://issues.apache.org/jira/browse/EAGLE-758 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Garrett Li Assignee: Garrett Li Fix For: v0.5.0 Without tuple log for spout & alert bolt, it is hard to troubleshoot event missing issue, we don't know whether the spout/alert process issue or no event come. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-757) fix alert JdbcDatabaseHandler connection issue
wujinhu created EAGLE-757: - Summary: fix alert JdbcDatabaseHandler connection issue Key: EAGLE-757 URL: https://issues.apache.org/jira/browse/EAGLE-757 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 1. fix JdbcDatabaseHandler connection, could not share one connection 2. remove code like e.printStackTrace(); use log instead -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-736) Fix eagle-data-process checkstyle warnings
[ https://issues.apache.org/jira/browse/EAGLE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luokun resolved EAGLE-736. -- Resolution: Fixed > Fix eagle-data-process checkstyle warnings > -- > > Key: EAGLE-736 > URL: https://issues.apache.org/jira/browse/EAGLE-736 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: luokun >Assignee: luokun > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Fix checkstyle problems on eagle-data-process -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-736) Fix eagle-data-process checkstyle warnings
[ https://issues.apache.org/jira/browse/EAGLE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649640#comment-15649640 ] ASF GitHub Bot commented on EAGLE-736: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/623 > Fix eagle-data-process checkstyle warnings > -- > > Key: EAGLE-736 > URL: https://issues.apache.org/jira/browse/EAGLE-736 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: luokun >Assignee: luokun > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Fix checkstyle problems on eagle-data-process -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #623: [EAGLE-736] Fix eagle-data-process checks...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/623 --- 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 #612: EAGLE-728 Application can't load applicat...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/612 --- 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-728) Application can't load application.properties when running local mode
[
https://issues.apache.org/jira/browse/EAGLE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649620#comment-15649620
]
ASF GitHub Bot commented on EAGLE-728:
--
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-eagle/pull/612
> Application can't load application.properties when running local mode
> -
>
> Key: EAGLE-728
> URL: https://issues.apache.org/jira/browse/EAGLE-728
> Project: Eagle
> Issue Type: Bug
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>
> When running local mode, jpm app can't get property
> "job.name.normalization.rules.key", then get exception
> {code}
> ERROR [2016-11-02 15:18:04,382]
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO: fail reading
> job history file
> ! java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.eagle.jpm.util.JobNameNormalization
> ! at
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.handleJob(JHFEventReaderBase.java:199)
> ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.handleJobSubmitted(JHFMRVer2EventReader.java:187)
> ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.handleEvent(JHFMRVer2EventReader.java:53)
> ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2Parser.parse(JHFMRVer2Parser.java:61)
> ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at
> org.apache.eagle.jpm.mr.history.crawler.DefaultJHFInputStreamCallback.onInputStream(DefaultJHFInputStreamCallback.java:58)
> ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO.readFileContent(AbstractJobHistoryDAO.java:123)
> ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at
> org.apache.eagle.jpm.mr.history.crawler.JHFCrawlerDriverImpl.crawl(JHFCrawlerDriverImpl.java:166)
> [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at
> org.apache.eagle.jpm.mr.history.storm.JobHistorySpout.nextTuple(JobHistorySpout.java:160)
> [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at
> backtype.storm.daemon.executor$fn__3373$fn__3388$fn__3417.invoke(executor.clj:565)
> [storm-core-0.9.3.jar:0.9.3]
> ! at backtype.storm.util$async_loop$fn__464.invoke(util.clj:463)
> [storm-core-0.9.3.jar:0.9.3]
> ! at clojure.lang.AFn.run(AFn.java:24)
> [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EAGLE-756) metadata change (with coordinator build) in publishment is not sent to runtime bolts
[ https://issues.apache.org/jira/browse/EAGLE-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649612#comment-15649612 ] ASF GitHub Bot commented on EAGLE-756: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/630 > metadata change (with coordinator build) in publishment is not sent to > runtime bolts > > > Key: EAGLE-756 > URL: https://issues.apache.org/jira/browse/EAGLE-756 > Project: Eagle > Issue Type: Bug >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > During test Alert Engine publisher, > it looks like when we have slack publishment, the metadata reload become > slow refreshed when use change the metadata and manually trigger the > coordinator schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #630: EAGLE-756: make sure publish change is se...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/630 --- 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-755) Publishment without streamIds update encountered NPE
[ https://issues.apache.org/jira/browse/EAGLE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649611#comment-15649611 ] ASF GitHub Bot commented on EAGLE-755: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/629 > Publishment without streamIds update encountered NPE > > > Key: EAGLE-755 > URL: https://issues.apache.org/jira/browse/EAGLE-755 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > 2016-11-08 22:24:05.924 o.a.c.f.r.c.NodeCache [ERROR] Calling listener > java.lang.NullPointerException > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.onPublishChange(AlertPublisherImpl.java:170) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.runner.AlertPublisherBolt.onAlertPublishSpecChange(AlertPublisherBolt.java:113) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifyAlertPublishBolt$3(AbstractMetadataChangeNot > at java.util.ArrayList.forEach(ArrayList.java:1249) > ~[?:1.8.0_92-internal] > at > org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifyAlertPublishBolt(AbstractMetadataChangeNotifyServic > at > org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:137) > ~[stormjar. > 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:?] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #629: EAGLE-755: Publishment without streamIds ...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/629 --- 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-752) JPM statistic need remove jobType
[ https://issues.apache.org/jira/browse/EAGLE-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649544#comment-15649544 ] ASF GitHub Bot commented on EAGLE-752: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/624 > JPM statistic need remove jobType > - > > Key: EAGLE-752 > URL: https://issues.apache.org/jira/browse/EAGLE-752 > Project: Eagle > Issue Type: Bug >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > > JPM statistic need remove jobType -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #624: EAGLE-752 JPM statistic need remove jobTy...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/624 --- 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-756) metadata change (with coordinator build) in publishment is not sent to runtime bolts
[ https://issues.apache.org/jira/browse/EAGLE-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649522#comment-15649522 ] ASF GitHub Bot commented on EAGLE-756: -- GitHub user mizeng opened a pull request: https://github.com/apache/incubator-eagle/pull/630 EAGLE-756: make sure publish change is sent to runtime bolts During test with Alert Engine publisher, it looks like when we have slack publishment, the metadata reload become slow refreshed when use change the metadata and manually trigger the coordinator schedule. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mizeng/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/630.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 #630 commit e514041d33868971bc9cc91b1a6ffa53cf7028bd Author: mizeng Date: 2016-11-08T23:37:39Z EAGLE-756: make sure publish change is sent to runtime bolts > metadata change (with coordinator build) in publishment is not sent to > runtime bolts > > > Key: EAGLE-756 > URL: https://issues.apache.org/jira/browse/EAGLE-756 > Project: Eagle > Issue Type: Bug >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > During test Alert Engine publisher, > it looks like when we have slack publishment, the metadata reload become > slow refreshed when use change the metadata and manually trigger the > coordinator schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #630: EAGLE-756: make sure publish change is se...
GitHub user mizeng opened a pull request: https://github.com/apache/incubator-eagle/pull/630 EAGLE-756: make sure publish change is sent to runtime bolts During test with Alert Engine publisher, it looks like when we have slack publishment, the metadata reload become slow refreshed when use change the metadata and manually trigger the coordinator schedule. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mizeng/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/630.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 #630 commit e514041d33868971bc9cc91b1a6ffa53cf7028bd Author: mizeng Date: 2016-11-08T23:37:39Z EAGLE-756: make sure publish change is sent to runtime bolts --- 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-752) JPM statistic need remove jobType
[ https://issues.apache.org/jira/browse/EAGLE-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649520#comment-15649520 ] ASF GitHub Bot commented on EAGLE-752: -- Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/624 LGTM > JPM statistic need remove jobType > - > > Key: EAGLE-752 > URL: https://issues.apache.org/jira/browse/EAGLE-752 > Project: Eagle > Issue Type: Bug >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > > JPM statistic need remove jobType -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #624: EAGLE-752 JPM statistic need remove jobType
Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/624 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. ---
[jira] [Created] (EAGLE-756) metadata change (with coordinator build) in publishment is not sent to runtime bolts
Zeng, Bryant created EAGLE-756: -- Summary: metadata change (with coordinator build) in publishment is not sent to runtime bolts Key: EAGLE-756 URL: https://issues.apache.org/jira/browse/EAGLE-756 Project: Eagle Issue Type: Bug Reporter: Zeng, Bryant Assignee: Zeng, Bryant During test Alert Engine publisher, it looks like when we have slack publishment, the metadata reload become slow refreshed when use change the metadata and manually trigger the coordinator schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-733) Add unit test for MetricSystem
[ https://issues.apache.org/jira/browse/EAGLE-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649483#comment-15649483 ] ASF GitHub Bot commented on EAGLE-733: -- Github user r7raul1984 commented on the issue: https://github.com/apache/incubator-eagle/pull/619 @baibaichen The module coverage is changed to 22%. > Add unit test for MetricSystem > -- > > Key: EAGLE-733 > URL: https://issues.apache.org/jira/browse/EAGLE-733 > Project: Eagle > Issue Type: Sub-task >Reporter: JiJun Tang >Assignee: JiJun Tang >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #619: [EAGLE-733] Add unit test for MetricSystem.
Github user r7raul1984 commented on the issue: https://github.com/apache/incubator-eagle/pull/619 @baibaichen The module coverage is changed to 22%. --- 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 #620: EAGLE-747 Add unit test for eagle-storage-base m...
Github user chitin commented on the issue: https://github.com/apache/incubator-eagle/pull/620 The module coverage is changed to 55%. --- 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-747) Add unit test for eagle-storage-base module
[ https://issues.apache.org/jira/browse/EAGLE-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649461#comment-15649461 ] ASF GitHub Bot commented on EAGLE-747: -- Github user chitin commented on the issue: https://github.com/apache/incubator-eagle/pull/620 The module coverage is changed to 55%. > Add unit test for eagle-storage-base module > --- > > Key: EAGLE-747 > URL: https://issues.apache.org/jira/browse/EAGLE-747 > Project: Eagle > Issue Type: Improvement >Reporter: Lingang Deng >Assignee: Lingang Deng > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-733) Add unit test for MetricSystem
[ https://issues.apache.org/jira/browse/EAGLE-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649448#comment-15649448 ] ASF GitHub Bot commented on EAGLE-733: -- Github user baibaichen commented on the issue: https://github.com/apache/incubator-eagle/pull/619 @r7raul1984 how code coverage is changed? > Add unit test for MetricSystem > -- > > Key: EAGLE-733 > URL: https://issues.apache.org/jira/browse/EAGLE-733 > Project: Eagle > Issue Type: Sub-task >Reporter: JiJun Tang >Assignee: JiJun Tang >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #620: EAGLE-747 Add unit test for eagle-storage-base m...
Github user baibaichen commented on the issue: https://github.com/apache/incubator-eagle/pull/620 @chitin how code coverage is 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] incubator-eagle issue #619: [EAGLE-733] Add unit test for MetricSystem.
Github user baibaichen commented on the issue: https://github.com/apache/incubator-eagle/pull/619 @r7raul1984 how code coverage is 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. ---
[jira] [Commented] (EAGLE-747) Add unit test for eagle-storage-base module
[ https://issues.apache.org/jira/browse/EAGLE-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649445#comment-15649445 ] ASF GitHub Bot commented on EAGLE-747: -- Github user baibaichen commented on the issue: https://github.com/apache/incubator-eagle/pull/620 @chitin how code coverage is changed? > Add unit test for eagle-storage-base module > --- > > Key: EAGLE-747 > URL: https://issues.apache.org/jira/browse/EAGLE-747 > Project: Eagle > Issue Type: Improvement >Reporter: Lingang Deng >Assignee: Lingang Deng > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-755) Publishment without streamIds update encountered NPE
[ https://issues.apache.org/jira/browse/EAGLE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649209#comment-15649209 ] ASF GitHub Bot commented on EAGLE-755: -- GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/629 EAGLE-755: Publishment without streamIds update encountered NPE fix NPE issue by use google Objects.equals method. 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/629.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 #629 commit 756cf42fb9ab8046d7057e6bf920bc18fffbba35 Author: Xiancheng Li Date: 2016-11-08T23:23:30Z EAGLE-755: Publishment without streamIds update encountered NPE > Publishment without streamIds update encountered NPE > > > Key: EAGLE-755 > URL: https://issues.apache.org/jira/browse/EAGLE-755 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > 2016-11-08 22:24:05.924 o.a.c.f.r.c.NodeCache [ERROR] Calling listener > java.lang.NullPointerException > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.onPublishChange(AlertPublisherImpl.java:170) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.runner.AlertPublisherBolt.onAlertPublishSpecChange(AlertPublisherBolt.java:113) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifyAlertPublishBolt$3(AbstractMetadataChangeNot > at java.util.ArrayList.forEach(ArrayList.java:1249) > ~[?:1.8.0_92-internal] > at > org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifyAlertPublishBolt(AbstractMetadataChangeNotifyServic > at > org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:137) > ~[stormjar. > 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:?] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #629: EAGLE-755: Publishment without streamIds ...
GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/629 EAGLE-755: Publishment without streamIds update encountered NPE fix NPE issue by use google Objects.equals method. 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/629.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 #629 commit 756cf42fb9ab8046d7057e6bf920bc18fffbba35 Author: Xiancheng Li Date: 2016-11-08T23:23:30Z EAGLE-755: Publishment without streamIds update encountered NPE --- 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] (EAGLE-755) Publishment without streamIds update encountered NPE
Garrett Li created EAGLE-755: Summary: Publishment without streamIds update encountered NPE Key: EAGLE-755 URL: https://issues.apache.org/jira/browse/EAGLE-755 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Garrett Li Assignee: Garrett Li Fix For: v0.5.0 2016-11-08 22:24:05.924 o.a.c.f.r.c.NodeCache [ERROR] Calling listener java.lang.NullPointerException at org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.onPublishChange(AlertPublisherImpl.java:170) ~[stormjar.jar:?] at org.apache.eagle.alert.engine.runner.AlertPublisherBolt.onAlertPublishSpecChange(AlertPublisherBolt.java:113) ~[stormjar.jar:?] at org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifyAlertPublishBolt$3(AbstractMetadataChangeNot at java.util.ArrayList.forEach(ArrayList.java:1249) ~[?:1.8.0_92-internal] at org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifyAlertPublishBolt(AbstractMetadataChangeNotifyServic at org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:137) ~[stormjar. 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:?] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #628: [EAGLE-754] Refactor - move ignored test ...
GitHub user baibaichen opened a pull request: https://github.com/apache/incubator-eagle/pull/628 [EAGLE-754] Refactor - move ignored test class to corresponding module With this commit, improving code coverage of eagle-entity-base to 51%, code coverage of eagle-query-base to 54% You can merge this pull request into a Git repository by running: $ git pull https://github.com/baibaichen/incubator-eagle feature/UT Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/628.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 #628 commit fc7f43046c43249ea0ccc71a50be3db9892c2bdf Author: chang chen Date: 2016-11-08T08:39:50Z [EAGLE-754] Refactor - move ignored test class to corresponding module --- 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-754) Refactor - move ignored test class to corresponding module
[ https://issues.apache.org/jira/browse/EAGLE-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647871#comment-15647871 ] ASF GitHub Bot commented on EAGLE-754: -- GitHub user baibaichen opened a pull request: https://github.com/apache/incubator-eagle/pull/628 [EAGLE-754] Refactor - move ignored test class to corresponding module With this commit, improving code coverage of eagle-entity-base to 51%, code coverage of eagle-query-base to 54% You can merge this pull request into a Git repository by running: $ git pull https://github.com/baibaichen/incubator-eagle feature/UT Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/628.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 #628 commit fc7f43046c43249ea0ccc71a50be3db9892c2bdf Author: chang chen Date: 2016-11-08T08:39:50Z [EAGLE-754] Refactor - move ignored test class to corresponding module > Refactor - move ignored test class to corresponding module > --- > > Key: EAGLE-754 > URL: https://issues.apache.org/jira/browse/EAGLE-754 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen >Priority: Minor > Labels: unit-test > Fix For: v0.5.0 > > > We already fixed HBase UT in > [Eagle-411|https://issues.apache.org/jira/browse/Eagle-411], so we can run > previous ignored hbase test of eagle-service-base. However TestHBaseLogRead2 > and TestListQueryCompile actually test ListQueryCompile, move them to > eagle-query-base -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #627: [EAGLE-754] Refactor - move ignored test ...
Github user baibaichen closed the pull request at: https://github.com/apache/incubator-eagle/pull/627 --- 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-754) Refactor - move ignored test class to corresponding module
[ https://issues.apache.org/jira/browse/EAGLE-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647826#comment-15647826 ] ASF GitHub Bot commented on EAGLE-754: -- Github user baibaichen closed the pull request at: https://github.com/apache/incubator-eagle/pull/627 > Refactor - move ignored test class to corresponding module > --- > > Key: EAGLE-754 > URL: https://issues.apache.org/jira/browse/EAGLE-754 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen >Priority: Minor > Labels: unit-test > Fix For: v0.5.0 > > > We already fixed HBase UT in > [Eagle-411|https://issues.apache.org/jira/browse/Eagle-411], so we can run > previous ignored hbase test of eagle-service-base. However TestHBaseLogRead2 > and TestListQueryCompile actually test ListQueryCompile, move them to > eagle-query-base -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-754) Refactor - move ignored test class to corresponding module
[ https://issues.apache.org/jira/browse/EAGLE-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647825#comment-15647825 ] ASF GitHub Bot commented on EAGLE-754: -- Github user baibaichen commented on the issue: https://github.com/apache/incubator-eagle/pull/627 missing remove ignore of TestHBaseLogReader2 > Refactor - move ignored test class to corresponding module > --- > > Key: EAGLE-754 > URL: https://issues.apache.org/jira/browse/EAGLE-754 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen >Priority: Minor > Labels: unit-test > Fix For: v0.5.0 > > > We already fixed HBase UT in > [Eagle-411|https://issues.apache.org/jira/browse/Eagle-411], so we can run > previous ignored hbase test of eagle-service-base. However TestHBaseLogRead2 > and TestListQueryCompile actually test ListQueryCompile, move them to > eagle-query-base -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #627: [EAGLE-754] Refactor - move ignored test class t...
Github user baibaichen commented on the issue: https://github.com/apache/incubator-eagle/pull/627 missing remove ignore of TestHBaseLogReader2 --- 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-754) Refactor - move ignored test class to corresponding module
[ https://issues.apache.org/jira/browse/EAGLE-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647739#comment-15647739 ] ASF GitHub Bot commented on EAGLE-754: -- GitHub user baibaichen opened a pull request: https://github.com/apache/incubator-eagle/pull/627 [EAGLE-754] Refactor - move ignored test class to corresponding module With this commit, improve code coverage of eagle-entity-base to 51%, code coverage of eagle-query-base to 54% You can merge this pull request into a Git repository by running: $ git pull https://github.com/baibaichen/incubator-eagle feature/UT Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/627.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 #627 commit 07247691a0d05de705966b0243ef5f5a83f3ec62 Author: chang chen Date: 2016-11-08T08:39:50Z [EAGLE-754] Refactor - move ignored test class to corresponding module > Refactor - move ignored test class to corresponding module > --- > > Key: EAGLE-754 > URL: https://issues.apache.org/jira/browse/EAGLE-754 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen >Priority: Minor > Labels: unit-test > Fix For: v0.5.0 > > > We already fixed HBase UT in > [Eagle-411|https://issues.apache.org/jira/browse/Eagle-411], so we can run > previous ignored hbase test of eagle-service-base. However TestHBaseLogRead2 > and TestListQueryCompile actually test ListQueryCompile, move them to > eagle-query-base -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-754) Refactor - move ignored test class to corresponding module
[ https://issues.apache.org/jira/browse/EAGLE-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen updated EAGLE-754: - Labels: unit-test (was: ) > Refactor - move ignored test class to corresponding module > --- > > Key: EAGLE-754 > URL: https://issues.apache.org/jira/browse/EAGLE-754 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen >Priority: Minor > Labels: unit-test > Fix For: v0.5.0 > > > We already fixed HBase UT in > [Eagle-411|https://issues.apache.org/jira/browse/Eagle-411], so we can run > previous ignored hbase test of eagle-service-base. However TestHBaseLogRead2 > and TestListQueryCompile actually test ListQueryCompile, move them to > eagle-query-base -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-754) Refactor - move ignored test class to corresponding module
[ https://issues.apache.org/jira/browse/EAGLE-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen updated EAGLE-754: - Description: We already fixed HBase UT in [Eagle-411|https://issues.apache.org/jira/browse/Eagle-411], so we can run previous ignored hbase test of eagle-service-base. However TestHBaseLogRead2 and TestListQueryCompile actually test ListQueryCompile, move them to eagle-query-base (was: We already fixed HBase UT in [Eagle-411|https://issues.apache.org/jira/browse/Eagle-411], so we can run previous ignored hbase test inf eagle-service-base. However TestHBaseLogRead2 and TestListQueryCompile actually test ListQueryCompile, move them to eagle-query-base) > Refactor - move ignored test class to corresponding module > --- > > Key: EAGLE-754 > URL: https://issues.apache.org/jira/browse/EAGLE-754 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen >Priority: Minor > Labels: unit-test > Fix For: v0.5.0 > > > We already fixed HBase UT in > [Eagle-411|https://issues.apache.org/jira/browse/Eagle-411], so we can run > previous ignored hbase test of eagle-service-base. However TestHBaseLogRead2 > and TestListQueryCompile actually test ListQueryCompile, move them to > eagle-query-base -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #627: [EAGLE-754] Refactor - move ignored test ...
GitHub user baibaichen opened a pull request: https://github.com/apache/incubator-eagle/pull/627 [EAGLE-754] Refactor - move ignored test class to corresponding module With this commit, improve code coverage of eagle-entity-base to 51%, code coverage of eagle-query-base to 54% You can merge this pull request into a Git repository by running: $ git pull https://github.com/baibaichen/incubator-eagle feature/UT Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/627.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 #627 commit 07247691a0d05de705966b0243ef5f5a83f3ec62 Author: chang chen Date: 2016-11-08T08:39:50Z [EAGLE-754] Refactor - move ignored test class to corresponding module --- 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] [Updated] (EAGLE-753) Improve code coverage of eagle-service-base
[ https://issues.apache.org/jira/browse/EAGLE-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen updated EAGLE-753: - Labels: unit-test (was: ) > Improve code coverage of eagle-service-base > --- > > Key: EAGLE-753 > URL: https://issues.apache.org/jira/browse/EAGLE-753 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen >Priority: Minor > Labels: unit-test > Fix For: v0.5.0 > > > Current code coverage of eagle-service-base is 0% , this is caused by all > tests are ignored -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-754) Refactor - move ignored test class to corresponding module
[ https://issues.apache.org/jira/browse/EAGLE-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen updated EAGLE-754: - Description: We already fixed HBase UT in [Eagle-411|https://issues.apache.org/jira/browse/Eagle-411], so we can run previous ignored hbase test inf eagle-service-base. However TestHBaseLogRead2 and TestListQueryCompile actually test ListQueryCompile, move them to eagle-query-base (was: We already fixed HBase UT in Eagle-411, so we can run previous ignored hbase test inf eagle-service-base. However TestHBaseLogRead2 and TestListQueryCompile actually test ListQueryCompile, move them to eagle-query-base) > Refactor - move ignored test class to corresponding module > --- > > Key: EAGLE-754 > URL: https://issues.apache.org/jira/browse/EAGLE-754 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen >Priority: Minor > Fix For: v0.5.0 > > > We already fixed HBase UT in > [Eagle-411|https://issues.apache.org/jira/browse/Eagle-411], so we can run > previous ignored hbase test inf eagle-service-base. However > TestHBaseLogRead2 and TestListQueryCompile actually test ListQueryCompile, > move them to eagle-query-base -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-754) Refactor - move ignored test class to corresponding module
Chang chen created EAGLE-754: Summary: Refactor - move ignored test class to corresponding module Key: EAGLE-754 URL: https://issues.apache.org/jira/browse/EAGLE-754 Project: Eagle Issue Type: Sub-task Affects Versions: v0.5.0 Reporter: Chang chen Assignee: Chang chen Priority: Minor Fix For: v0.5.0 We already fixed HBase UT in Eagle-411, so we can run previous ignored hbase test inf eagle-service-base. However TestHBaseLogRead2 and TestListQueryCompile actually test ListQueryCompile, move them to eagle-query-base -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-753) Improve code coverage of eagle-service-base
Chang chen created EAGLE-753: Summary: Improve code coverage of eagle-service-base Key: EAGLE-753 URL: https://issues.apache.org/jira/browse/EAGLE-753 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Chang chen Assignee: Chang chen Priority: Minor Fix For: v0.5.0 Current code coverage of eagle-service-base is 0% , this is caused by all tests are ignored -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #622: EAGLE-751: update policyDefinition#equal
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/622 --- 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-751) Two policyDefinitions with different status are equal
[ https://issues.apache.org/jira/browse/EAGLE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647538#comment-15647538 ] ASF GitHub Bot commented on EAGLE-751: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/622 > Two policyDefinitions with different status are equal > -- > > Key: EAGLE-751 > URL: https://issues.apache.org/jira/browse/EAGLE-751 > Project: Eagle > Issue Type: Bug >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > In equal() of PolicyDefinition, field policyStatus is missed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-675) AlertEngine: don't host long-live curator framework for schedule
[ https://issues.apache.org/jira/browse/EAGLE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Ralph resolved EAGLE-675. Resolution: Fixed > AlertEngine: don't host long-live curator framework for schedule > > > Key: EAGLE-675 > URL: https://issues.apache.org/jira/browse/EAGLE-675 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: v0.5.0 > > > In Coordinator, the config bus producer is hold as member. This is try to > reuse connection for continous operation. But this is buggy, since when zk > server in network issue, curator framework would generate a lot of logs that > flood the log file. > Same for ExclusiveExecutor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-675) AlertEngine: don't host long-live curator framework for schedule
[ https://issues.apache.org/jira/browse/EAGLE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647535#comment-15647535 ] ASF GitHub Bot commented on EAGLE-675: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/626 > AlertEngine: don't host long-live curator framework for schedule > > > Key: EAGLE-675 > URL: https://issues.apache.org/jira/browse/EAGLE-675 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: v0.5.0 > > > In Coordinator, the config bus producer is hold as member. This is try to > reuse connection for continous operation. But this is buggy, since when zk > server in network issue, curator framework would generate a lot of logs that > flood the log file. > Same for ExclusiveExecutor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #626: EAGLE-675 : AlertEngine: don't host long-...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/626 --- 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-675) AlertEngine: don't host long-live curator framework for schedule
[ https://issues.apache.org/jira/browse/EAGLE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647451#comment-15647451 ] ASF GitHub Bot commented on EAGLE-675: -- GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/626 EAGLE-675 : AlertEngine: don't host long-live curator framework for s… …chedule Author: 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/626.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 #626 commit 715a8f7a5f02fc7fb59af3816f1711a65b2150ab Author: Ralph, Su Date: 2016-11-08T12:31:57Z EAGLE-675 : AlertEngine: don't host long-live curator framework for schedule Author: ralphsu > AlertEngine: don't host long-live curator framework for schedule > > > Key: EAGLE-675 > URL: https://issues.apache.org/jira/browse/EAGLE-675 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: v0.5.0 > > > In Coordinator, the config bus producer is hold as member. This is try to > reuse connection for continous operation. But this is buggy, since when zk > server in network issue, curator framework would generate a lot of logs that > flood the log file. > Same for ExclusiveExecutor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #626: EAGLE-675 : AlertEngine: don't host long-...
GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/626 EAGLE-675 : AlertEngine: don't host long-live curator framework for s⦠â¦chedule Author: 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/626.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 #626 commit 715a8f7a5f02fc7fb59af3816f1711a65b2150ab Author: Ralph, Su Date: 2016-11-08T12:31:57Z EAGLE-675 : AlertEngine: don't host long-live curator framework for schedule Author: 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] [Closed] (EAGLE-411) Improve code coverage of eagle-storage-hbase
[ https://issues.apache.org/jira/browse/EAGLE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen closed EAGLE-411. Resolution: Fixed > Improve code coverage of eagle-storage-hbase > > > Key: EAGLE-411 > URL: https://issues.apache.org/jira/browse/EAGLE-411 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.3.0, v0.4.0 >Reporter: Hao Chen >Assignee: Chang chen > Labels: unit-test > Fix For: v0.5.0 > > > Current implementation is really not stable which cause unit test like > TestHBaseLogReader2 unable to pass in meanful time, we need a better version. > https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-embed/eagle-embed-hbase/src/main/java/org/apache/eagle/service/hbase/EmbeddedHbase.java > http://blog.cloudera.com/blog/2013/09/how-to-test-hbase-applications-using-popular-tools/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-746) PolicyValidation is insufficient, and will cause blocking for extended handler
[ https://issues.apache.org/jira/browse/EAGLE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Ralph resolved EAGLE-746. Resolution: Fixed > PolicyValidation is insufficient, and will cause blocking for extended handler > -- > > Key: EAGLE-746 > URL: https://issues.apache.org/jira/browse/EAGLE-746 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: v0.5.0 > > > Policy validation is hard code to siddhi ql without checking the policy type. > Also for complex query, we need to make sure leftjoin query things also works -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-732) Exclude coverage instrumentation of generated class
[ https://issues.apache.org/jira/browse/EAGLE-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen closed EAGLE-732. > Exclude coverage instrumentation of generated class > --- > > Key: EAGLE-732 > URL: https://issues.apache.org/jira/browse/EAGLE-732 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen >Priority: Trivial > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-727) Fix TestGroupAggregateTimeSeriesClient and TestGroupAggregateClient
[ https://issues.apache.org/jira/browse/EAGLE-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen closed EAGLE-727. > Fix TestGroupAggregateTimeSeriesClient and TestGroupAggregateClient > --- > > Key: EAGLE-727 > URL: https://issues.apache.org/jira/browse/EAGLE-727 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen > Fix For: v0.5.0 > > > TestGroupAggregateTimeSeriesClient and TestGroupAggregateClient can't run > correctly due to without setting hbase.coprocessor.region.classes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-717) Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly
[ https://issues.apache.org/jira/browse/EAGLE-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen closed EAGLE-717. > Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly > > > Key: EAGLE-717 > URL: https://issues.apache.org/jira/browse/EAGLE-717 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen > Labels: unit-test > Fix For: v0.5.0 > > > Eagle UT need load siddhi string extension dynamically, but the current > maven-surefire-plugin is too old (2.6), and can't work correctly in always > forkMode which is needed for HBase UT. See [Class Loading and Forking in > Maven > Surefire|http://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html] > to understand how maven-surefire-plugin sets *java.class.path* and why. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-730) Add UnitTest for HBaseStorage
[ https://issues.apache.org/jira/browse/EAGLE-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen closed EAGLE-730. > Add UnitTest for HBaseStorage > - > > Key: EAGLE-730 > URL: https://issues.apache.org/jira/browse/EAGLE-730 > Project: Eagle > Issue Type: Sub-task >Reporter: Chang chen >Assignee: Chang chen > Fix For: v0.5.0 > > > Currently , there is only one test (TestHBaseStorageLoader) to verify > creating HBaseStorage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-727) Fix TestGroupAggregateTimeSeriesClient and TestGroupAggregateClient
[ https://issues.apache.org/jira/browse/EAGLE-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen resolved EAGLE-727. -- Resolution: Fixed https://github.com/apache/incubator-eagle/pull/608 > Fix TestGroupAggregateTimeSeriesClient and TestGroupAggregateClient > --- > > Key: EAGLE-727 > URL: https://issues.apache.org/jira/browse/EAGLE-727 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen > Fix For: v0.5.0 > > > TestGroupAggregateTimeSeriesClient and TestGroupAggregateClient can't run > correctly due to without setting hbase.coprocessor.region.classes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-730) Add UnitTest for HBaseStorage
[ https://issues.apache.org/jira/browse/EAGLE-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen resolved EAGLE-730. -- Resolution: Fixed https://github.com/apache/incubator-eagle/pull/608 > Add UnitTest for HBaseStorage > - > > Key: EAGLE-730 > URL: https://issues.apache.org/jira/browse/EAGLE-730 > Project: Eagle > Issue Type: Sub-task >Reporter: Chang chen >Assignee: Chang chen > Fix For: v0.5.0 > > > Currently , there is only one test (TestHBaseStorageLoader) to verify > creating HBaseStorage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-732) Exclude coverage instrumentation of generated class
[ https://issues.apache.org/jira/browse/EAGLE-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen resolved EAGLE-732. -- Resolution: Fixed https://github.com/apache/incubator-eagle/pull/608 > Exclude coverage instrumentation of generated class > --- > > Key: EAGLE-732 > URL: https://issues.apache.org/jira/browse/EAGLE-732 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen >Priority: Trivial > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-731) HBaseStorage doesn't set affected size after create and delete operation
[ https://issues.apache.org/jira/browse/EAGLE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen resolved EAGLE-731. -- Resolution: Fixed https://github.com/apache/incubator-eagle/pull/608 > HBaseStorage doesn't set affected size after create and delete operation > -- > > Key: EAGLE-731 > URL: https://issues.apache.org/jira/browse/EAGLE-731 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Chang chen > Fix For: v0.5.0 > > > Refer to JdbcStroage implementation, HBaseStorage doesn't set affected size > of create and delete operation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-746) PolicyValidation is insufficient, and will cause blocking for extended handler
[ https://issues.apache.org/jira/browse/EAGLE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647380#comment-15647380 ] ASF GitHub Bot commented on EAGLE-746: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/625 > PolicyValidation is insufficient, and will cause blocking for extended handler > -- > > Key: EAGLE-746 > URL: https://issues.apache.org/jira/browse/EAGLE-746 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: v0.5.0 > > > Policy validation is hard code to siddhi ql without checking the policy type. > Also for complex query, we need to make sure leftjoin query things also works -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #625: EAGLE-746 : PolicyValidation is insuffici...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/625 --- 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-746) PolicyValidation is insufficient, and will cause blocking for extended handler
[ https://issues.apache.org/jira/browse/EAGLE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647358#comment-15647358 ] ASF GitHub Bot commented on EAGLE-746: -- GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/625 EAGLE-746 : PolicyValidation is insufficient, and will cause blocking… … for extended handler Author: 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/625.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 #625 commit 34c69a9314ebecd9f71def46c6f72774e1084f84 Author: Ralph, Su Date: 2016-11-08T11:45:49Z EAGLE-746 : PolicyValidation is insufficient, and will cause blocking for extended handler Author: ralphsu > PolicyValidation is insufficient, and will cause blocking for extended handler > -- > > Key: EAGLE-746 > URL: https://issues.apache.org/jira/browse/EAGLE-746 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: v0.5.0 > > > Policy validation is hard code to siddhi ql without checking the policy type. > Also for complex query, we need to make sure leftjoin query things also works -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #625: EAGLE-746 : PolicyValidation is insuffici...
GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/625 EAGLE-746 : PolicyValidation is insufficient, and will cause blocking⦠⦠for extended handler Author: 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/625.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 #625 commit 34c69a9314ebecd9f71def46c6f72774e1084f84 Author: Ralph, Su Date: 2016-11-08T11:45:49Z EAGLE-746 : PolicyValidation is insufficient, and will cause blocking for extended handler Author: 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-752) JPM statistic need remove jobType
[ https://issues.apache.org/jira/browse/EAGLE-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647186#comment-15647186 ] ASF GitHub Bot commented on EAGLE-752: -- GitHub user zombieJ opened a pull request: https://github.com/apache/incubator-eagle/pull/624 EAGLE-752 JPM statistic need remove jobType JPM statistic need remove jobType You can merge this pull request into a Git repository by running: $ git pull https://github.com/zombieJ/incubator-eagle EAGLE-752 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/624.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 #624 commit ebce94d5386d0ea0a90a66d3aa81b93528cdcc1f Author: zombieJ Date: 2016-11-08T10:37:42Z JPM statistic need remove jobType > JPM statistic need remove jobType > - > > Key: EAGLE-752 > URL: https://issues.apache.org/jira/browse/EAGLE-752 > Project: Eagle > Issue Type: Bug >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > > JPM statistic need remove jobType -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-752) JPM statistic need remove jobType
[ https://issues.apache.org/jira/browse/EAGLE-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-752: --- Description: JPM statistic need remove jobType > JPM statistic need remove jobType > - > > Key: EAGLE-752 > URL: https://issues.apache.org/jira/browse/EAGLE-752 > Project: Eagle > Issue Type: Bug >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > > JPM statistic need remove jobType -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #624: EAGLE-752 JPM statistic need remove jobTy...
GitHub user zombieJ opened a pull request: https://github.com/apache/incubator-eagle/pull/624 EAGLE-752 JPM statistic need remove jobType JPM statistic need remove jobType You can merge this pull request into a Git repository by running: $ git pull https://github.com/zombieJ/incubator-eagle EAGLE-752 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/624.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 #624 commit ebce94d5386d0ea0a90a66d3aa81b93528cdcc1f Author: zombieJ Date: 2016-11-08T10:37:42Z JPM statistic need remove jobType --- 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] (EAGLE-752) JPM statistic need remove jobType
Jilin, Jiang created EAGLE-752: -- Summary: JPM statistic need remove jobType Key: EAGLE-752 URL: https://issues.apache.org/jira/browse/EAGLE-752 Project: Eagle Issue Type: Bug Reporter: Jilin, Jiang Assignee: Jilin, Jiang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-736) Fix eagle-data-process checkstyle warnings
[ https://issues.apache.org/jira/browse/EAGLE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647038#comment-15647038 ] ASF GitHub Bot commented on EAGLE-736: -- Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/623 LGTM. > Fix eagle-data-process checkstyle warnings > -- > > Key: EAGLE-736 > URL: https://issues.apache.org/jira/browse/EAGLE-736 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: luokun >Assignee: luokun > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Fix checkstyle problems on eagle-data-process -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #623: [EAGLE-736] Fix eagle-data-process checkstyle wa...
Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/623 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. ---
[jira] [Resolved] (EAGLE-748) Streams UI display dataSource describe
[ https://issues.apache.org/jira/browse/EAGLE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jilin, Jiang resolved EAGLE-748. Resolution: Fixed > Streams UI display dataSource describe > -- > > Key: EAGLE-748 > URL: https://issues.apache.org/jira/browse/EAGLE-748 > Project: Eagle > Issue Type: Task >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (EAGLE-750) Improve coordinator schedule strategy to reuse alert work slot
[ https://issues.apache.org/jira/browse/EAGLE-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Ralph reassigned EAGLE-750: -- Assignee: Garrett Li (was: Su Ralph) > Improve coordinator schedule strategy to reuse alert work slot > -- > > Key: EAGLE-750 > URL: https://issues.apache.org/jira/browse/EAGLE-750 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Garrett Li > Fix For: v0.5.0 > > > We catch with some critical problem about alert engine policy schedule > strategy: > For example for an alert topology with 20 alert bolts , and after boarding 4 > policies and each assigning 5 slots, then the current alert coordinator will > treat the work slots as used up and be unable to schedule any more new > policies. > But in fact some typical eagle deployment will have at least 20+ streams with > lots of different partition requirements, which means we could just define > very few policies under such scheduling strategy and may waste slot resources > of eagle’s deployment infrastructure. > In original design, we should have designed to reused slot queue among > in-conflict monitored stream (stream-partition-sort), then eagle could try to > reuse alert slots if possible to improve resource utilization, and it should > be time to implement it now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-736) Fix eagle-data-process checkstyle warnings
[ https://issues.apache.org/jira/browse/EAGLE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646845#comment-15646845 ] ASF GitHub Bot commented on EAGLE-736: -- GitHub user koone opened a pull request: https://github.com/apache/incubator-eagle/pull/623 [EAGLE-736] Fix eagle-data-process checkstyle warnings https://issues.apache.org/jira/browse/EAGLE-736 --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/koone/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/623.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 #623 commit d089b85305b34cfc3dd1c258d1bd22f8 Author: koone Date: 2016-11-08T07:59:09Z [EAGLE-736] Fix eagle-data-process checkstyle warnings > Fix eagle-data-process checkstyle warnings > -- > > Key: EAGLE-736 > URL: https://issues.apache.org/jira/browse/EAGLE-736 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: luokun >Assignee: luokun > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Fix checkstyle problems on eagle-data-process -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #623: [EAGLE-736] Fix eagle-data-process checks...
GitHub user koone opened a pull request: https://github.com/apache/incubator-eagle/pull/623 [EAGLE-736] Fix eagle-data-process checkstyle warnings https://issues.apache.org/jira/browse/EAGLE-736 --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/koone/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/623.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 #623 commit d089b85305b34cfc3dd1c258d1bd22f8 Author: koone Date: 2016-11-08T07:59:09Z [EAGLE-736] Fix eagle-data-process checkstyle warnings --- 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. ---
