[GitHub] incubator-eagle pull request #728: [MINOR] add sortSpec to pattern match if ...

2016-12-08 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #728: [MINOR] add sortSpec to pattern match if ...

2016-12-08 Thread wujinhu
Github user wujinhu closed the pull request at:

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


---
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 #728: [MINOR] add sortSpec to pattern match if ...

2016-12-08 Thread wujinhu
GitHub user wujinhu reopened a pull request:

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

[MINOR] add sortSpec to pattern match if exists corresponding  
StreamPartition



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

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

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

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


commit 4c83f8bea18fdbc35593bf4f331c88b24547aee6
Author: wujinhu 
Date:   2016-12-09T02:22:40Z

Use sort spec of the stream with same Type & Columns if its sort spec is 
null

commit 77df16deaa581603e0fae7d0afe7e10690e924d2
Author: wujinhu 
Date:   2016-12-09T02:51:21Z

Use sort spec of the stream with same Type & Columns if its sort spec is 
null

commit 556266acc28389959c7d69155e11582f4cedac4f
Author: wujinhu 
Date:   2016-12-09T03:01:53Z

Use sort spec of the stream with same Type & Columns if its sort spec is 
null

commit 8303118fa776c87309bdbddc129d89bf39900702
Author: wujinhu 
Date:   2016-12-09T03:43:29Z

change default health check

commit 81b3e133cf51046366800e676c7237d4b4b1a465
Author: wujinhu 
Date:   2016-12-09T03:46:10Z

change default health check




---
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 #728: [MINOR] add sortSpec to pattern match if ...

2016-12-08 Thread wujinhu
GitHub user wujinhu opened a pull request:

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

[MINOR] add sortSpec to pattern match if exists corresponding  
StreamPartition



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

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

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

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


commit 4c83f8bea18fdbc35593bf4f331c88b24547aee6
Author: wujinhu 
Date:   2016-12-09T02:22:40Z

Use sort spec of the stream with same Type & Columns if its sort spec is 
null

commit 77df16deaa581603e0fae7d0afe7e10690e924d2
Author: wujinhu 
Date:   2016-12-09T02:51:21Z

Use sort spec of the stream with same Type & Columns if its sort spec is 
null




---
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 #727: [MINOR] fix StreamPartitions only with di...

2016-12-08 Thread wujinhu
Github user wujinhu closed the pull request at:

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


---
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 #726: [MINOR] Use larger sortSpec of the existi...

2016-12-08 Thread wujinhu
Github user wujinhu closed the pull request at:

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


---
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 #726: [MINOR] Use sortSpec of the stream with s...

2016-12-08 Thread wujinhu
GitHub user wujinhu reopened a pull request:

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

[MINOR] Use sortSpec of the stream with same StreamId & Type & Columns if 
sortSpec null



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

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

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

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


commit 4c83f8bea18fdbc35593bf4f331c88b24547aee6
Author: wujinhu 
Date:   2016-12-09T02:22:40Z

Use sort spec of the stream with same Type & Columns if its sort spec is 
null




---
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 #726: [MINOR] Use sortSpec of the stream with s...

2016-12-08 Thread wujinhu
Github user wujinhu closed the pull request at:

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


---
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 #726: [MINOR] Use sort spec of the stream with ...

2016-12-08 Thread wujinhu
GitHub user wujinhu opened a pull request:

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

[MINOR] Use sort spec of the stream with same StreamId & Type & Columns if 
its sort spec…



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

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

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

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


commit 4c83f8bea18fdbc35593bf4f331c88b24547aee6
Author: wujinhu 
Date:   2016-12-09T02:22:40Z

Use sort spec of the stream with same Type & Columns if its sort spec is 
null




---
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-798) Add a new alert publisher to store alerts into hbase

2016-12-08 Thread Zhao, Qingwen (JIRA)

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

Zhao, Qingwen closed EAGLE-798.
---
Resolution: Fixed

> Add a new alert publisher to store alerts into hbase
> 
>
> Key: EAGLE-798
> URL: https://issues.apache.org/jira/browse/EAGLE-798
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>Priority: Minor
> Fix For: v0.5.0
>
>
> currently, eagle stores alerts with metadata into jdbc database, which has 
> performance risks under large volume of data
> POST  http://localhost:9090/rest/entities?serviceName=AlertService
> {code}
> {
> "prefix": "alert_detail",
> "timestamp": 1480056123654,
> "tags": {
> "alertId": "xdfdksflsfjkslfslkdjfslkfsljkf",
> "policyId": "test_all",
> "siteId": "sandbox"
> },
> "exp": null,
> "encodedRowkey": "hiCMlG8vvsd___6nZcfO-SCZKe27qlR0",
> "serializeAlias": null,
> "serializeVerbose": true,
> "appIds": [
> "HDFS_AUDIT_LOG_MONITOR_APP_SANDBOX"
> ],
> "policyValue": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX 
> select * insert into hdfs_audit_log_enriched_stream_out",
> "alertData": {
> "allowed": true,
> "cmd": "delete",
> "dst": null,
> "host": "10.249.66.185",
> "securityZone": "NA",
> "sensitivityType": "NA",
> "src": "/tmp/hive/hive/caf2438a-87fe-4889-96ac-0c1f0b5dd4e0",
> "timestamp": 1480056117845,
> "user": "hive"
> }
> },
> {code}
> GET   
> http://localhost:9090/rest/entities?query=AlertService[@siteId="sandbox"]{*}=100=2016-11-22%2001:10:00=2017-12-22%2003:10:00



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


[jira] [Closed] (EAGLE-803) Just save latest N schedule_state in eagle database.

2016-12-08 Thread Zhao, Qingwen (JIRA)

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

Zhao, Qingwen closed EAGLE-803.
---
Resolution: Fixed

> Just save latest N schedule_state in eagle database.
> 
>
> Key: EAGLE-803
> URL: https://issues.apache.org/jira/browse/EAGLE-803
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> schedule_state table increases with the metadata updates. In this way, quite 
> a lot of old state occupy the space of database. For eagle, it is enough to 
> just save latest N schedule_state in eagle database.



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


[jira] [Closed] (EAGLE-808) Hide SMTP server configuration from end user and read from server config instead of metadata config

2016-12-08 Thread Zhao, Qingwen (JIRA)

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

Zhao, Qingwen closed EAGLE-808.
---
Resolution: Fixed

> Hide SMTP server configuration from end user and read from server config 
> instead of metadata config
> ---
>
> Key: EAGLE-808
> URL: https://issues.apache.org/jira/browse/EAGLE-808
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> Move smtp server config from publishment to the server config file, like
> {code}
>   "metadataService": {
> "context": "/api",
> "host": "localhost",
> "port": 8080,
> mailSmtpServer = "localhost",
> mailSmtpPort = 5025,
> mailSmtpAuth = "false"
> //mailSmtpConn = "plaintext",
> //mailSmtpUsername = ""
> //mailSmtpPassword = ""
> //mailSmtpDebug = false
>   },
> {code}
> Usage example: AlertEmailPublisherTest



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


[jira] [Closed] (EAGLE-819) Data from topology health check are inaccurate

2016-12-08 Thread Zhao, Qingwen (JIRA)

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

Zhao, Qingwen closed EAGLE-819.
---
Resolution: Fixed

> Data from topology health check are inaccurate 
> ---
>
> Key: EAGLE-819
> URL: https://issues.apache.org/jira/browse/EAGLE-819
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> 1. data overflow 
> 2. data generated by yarn crawler are inaccurate



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


[jira] [Closed] (EAGLE-829) Refactor PublishmentType model to align with PolicyDefinition

2016-12-08 Thread Zhao, Qingwen (JIRA)

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

Zhao, Qingwen closed EAGLE-829.
---
Resolution: Fixed

> Refactor PublishmentType model to align with PolicyDefinition
> -
>
> Key: EAGLE-829
> URL: https://issues.apache.org/jira/browse/EAGLE-829
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>Priority: Minor
> Fix For: v0.5.0
>
>
> rename fields:  className -> name 



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


[jira] [Commented] (EAGLE-833) Add MetricSchemaGenerator and MetricSchemaService

2016-12-08 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on EAGLE-833:
--

GitHub user haoch opened a pull request:

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

[EAGLE-833] Add MetricSchemaGenerator and MetricSchemaService

* Add MetricSchemaService to store metric schema aside GenericMetric
* Add MetricSchemaGenerator to automatically generate metric schema based 
on metric stream and metric definition.


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

$ git pull https://github.com/haoch/incubator-eagle AddMetricSchemaService

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

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


commit 9b7a33d02cbc8ec7a9c6baf2166296ac787bc2dc
Author: Hao Chen 
Date:   2016-12-08T14:42:58Z

Add

commit e9d4e3ad09fd460a14524cf5e7671f067b712ace
Author: Hao Chen 
Date:   2016-12-08T14:46:10Z

Merge branch 'master' of https://github.com/apache/incubator-eagle into 
AddMetricSchemaService

commit 6c71b68702c0dbc1d51d0a9a0998eba13e13ad19
Author: Hao Chen 
Date:   2016-12-08T16:08:52Z

Implement MetricSchemaGenerator

commit 5bd9840e160315dd879407c1fc1f1ecb7a5c6125
Author: Hao Chen 
Date:   2016-12-08T16:24:26Z

Simplify metric schema tag names




> Add MetricSchemaGenerator and MetricSchemaService
> -
>
> Key: EAGLE-833
> URL: https://issues.apache.org/jira/browse/EAGLE-833
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> * Add MetricSchemaService to store metric schema aside GenericMetric 
> *Add MetricSchemaGenerator to automatically generate metric schema based on 
> metric stream and metric definition.
>  



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


[GitHub] incubator-eagle pull request #725: [EAGLE-833] Add MetricSchemaGenerator and...

2016-12-08 Thread haoch
GitHub user haoch opened a pull request:

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

[EAGLE-833] Add MetricSchemaGenerator and MetricSchemaService

* Add MetricSchemaService to store metric schema aside GenericMetric
* Add MetricSchemaGenerator to automatically generate metric schema based 
on metric stream and metric definition.


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

$ git pull https://github.com/haoch/incubator-eagle AddMetricSchemaService

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

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


commit 9b7a33d02cbc8ec7a9c6baf2166296ac787bc2dc
Author: Hao Chen 
Date:   2016-12-08T14:42:58Z

Add

commit e9d4e3ad09fd460a14524cf5e7671f067b712ace
Author: Hao Chen 
Date:   2016-12-08T14:46:10Z

Merge branch 'master' of https://github.com/apache/incubator-eagle into 
AddMetricSchemaService

commit 6c71b68702c0dbc1d51d0a9a0998eba13e13ad19
Author: Hao Chen 
Date:   2016-12-08T16:08:52Z

Implement MetricSchemaGenerator

commit 5bd9840e160315dd879407c1fc1f1ecb7a5c6125
Author: Hao Chen 
Date:   2016-12-08T16:24:26Z

Simplify metric schema tag names




---
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-833) Add MetricSchemaGenerator and MetricSchemaService

2016-12-08 Thread Hao Chen (JIRA)
Hao Chen created EAGLE-833:
--

 Summary: Add MetricSchemaGenerator and MetricSchemaService
 Key: EAGLE-833
 URL: https://issues.apache.org/jira/browse/EAGLE-833
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


* Add MetricSchemaService to store metric schema aside GenericMetric 
*Add MetricSchemaGenerator to automatically generate metric schema based on 
metric stream and metric definition.
 



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


[jira] [Resolved] (EAGLE-832) Support to define granularity for MetricDefinition to avoid metric duplicate

2016-12-08 Thread Hao Chen (JIRA)

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

Hao Chen resolved EAGLE-832.

Resolution: Fixed

> Support to define granularity for MetricDefinition to avoid metric duplicate
> 
>
> Key: EAGLE-832
> URL: https://issues.apache.org/jira/browse/EAGLE-832
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Support to define granularity for MetricDefinition to avoid metric duplicate



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


[GitHub] incubator-eagle pull request #724: [EAGLE-832] Support to define granularity...

2016-12-08 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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-832) Support to define granularity for MetricDefinition to avoid metric duplicate

2016-12-08 Thread Hao Chen (JIRA)
Hao Chen created EAGLE-832:
--

 Summary: Support to define granularity for MetricDefinition to 
avoid metric duplicate
 Key: EAGLE-832
 URL: https://issues.apache.org/jira/browse/EAGLE-832
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


Support to define granularity for MetricDefinition to avoid metric duplicate



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


[jira] [Commented] (EAGLE-832) Support to define granularity for MetricDefinition to avoid metric duplicate

2016-12-08 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on EAGLE-832:
--

GitHub user haoch opened a pull request:

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

[EAGLE-832] Support to define granularity for MetricDefinition to avoid 
metric duplicate

Support to define granularity for MetricDefinition to avoid metric duplicate

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

$ git pull https://github.com/haoch/incubator-eagle SupportGranularity

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

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


commit e1c7fc7513e31b0a889a87fd2b7a71c402cf8e91
Author: Hao Chen 
Date:   2016-12-08T13:53:25Z

Support metric granularity




> Support to define granularity for MetricDefinition to avoid metric duplicate
> 
>
> Key: EAGLE-832
> URL: https://issues.apache.org/jira/browse/EAGLE-832
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Support to define granularity for MetricDefinition to avoid metric duplicate



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


[jira] [Commented] (EAGLE-831) UI alert support time range select

2016-12-08 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on EAGLE-831:
--

Github user asfgit closed the pull request at:

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


> UI alert support time range select
> --
>
> Key: EAGLE-831
> URL: https://issues.apache.org/jira/browse/EAGLE-831
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
>
> alert list support time range
> policy detail page display alert template



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


[GitHub] incubator-eagle pull request #723: EAGLE-831 UI alert support time range sel...

2016-12-08 Thread asfgit
Github user asfgit closed the pull request at:

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


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