date:20160809

[jira] [Commented] (EAGLE-283) Convert fid,uid in MapR's audit log to FIle/folder name, user name

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


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

ASF GitHub Bot commented on EAGLE-283:
--

GitHub user DadanielZ opened a pull request:

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

EAGLE-283: Convert fid,uid in MapR's audit log to FIle/folder name, user 
name

1. Added resolver for user's input of "volume", "file/folder", "Status"
- These resolver provide drop down list for user to select

2. Added NameConvertor to convert user's input to corresponding id and 
saved it in policy
- volume value will be used to call MapR's REST API to get volume id
- status code will be resolved to status id
- file/folder name will be passed to MapR's command line class to get 
its id.

3. Modified UI js file
- As soon as user input a value for "volume", "file", "status", it will 
fetch user's input and call rest service to get corresponding id
- Save ids as a new match criteria in the policy

4. Added maprfs resource resolver to provide drop down list for user

PS:how the id converter works: user select "== '/test'" in field "dst", a 
new match criteria "== 234.567.890" will appear automatically under it, and the 
policy will end up as:
  dst == 'test' or dst == '234.567.890'
Same thing will happen for volume and status input.
In this way, the policy is human readable and can be used to match the ids 
in maprfsAuditLog.

5. Added missing dependency on "commons-lang3" for module "eagle-jpm-util"


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

$ git pull https://github.com/DadanielZ/incubator-eagle EG-283

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

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


commit 936fc5a4eff3cd5bea11c1d15935b124b58b3780
Author: Daniel 
Date:   2016-08-09T22:39:31Z

EAGLE-283: Convert fid,uid in MapR's audit log to FIle/folder name, user 
name

1. Added resolver for user's input of "volume", "file/folder", "Status"
- These resolver provide drop down list for user to select

2. Added NameConvertor to convert user's input to corresponding id and 
saved it in policy
- volume value will be used to call MapR's REST API to get volume id
- status code will be resolved to status id
- file/folder name will be passed to MapR's command line class to get 
its id.

3. Modified UI js file
- As soon as user input a value for "volume", "file", "status", it will 
fetch user's input and call rest service to get corresponding id
- Save ids as a new match criteria in the policy

4. Added maprfs resource resolver to provide drop down list for user

PS:how the id converter works: user select "== '/test'" in field "dst", a 
new match criteria "== 234.567.890" will appear automatically under it, and the 
policy will end up as:
  dst == 'test' or dst == '234.567.890'
Same thing will happen for volume and status input.
In this way, the policy is human readable and can be used to match the ids 
in maprfsAuditLog.

commit 1731469effde0aa88693e7d64f100f3a089b90ac
Author: Daniel 
Date:   2016-08-10T04:03:55Z

Merge pull request #21 from apache/develop

update from Eagle-develop

commit 5cb1a682718835c10135003328bd959004e36cf9
Author: Daniel 
Date:   2016-08-10T04:05:11Z

Merge remote-tracking branch 'origin/EG-283' into EG-283

commit e2c5717a616f668c8db2c31b12d77120e9a4fff7
Author: Daniel 
Date:   2016-08-10T04:38:33Z

Added dependency on "commons-lang3" for module eagle-jpm-util
- mapr build will fail without this dependency

commit f812c4d3b2b9235840c141beb19a3b33743c9720
Author: Daniel 
Date:   2016-08-10T04:46:04Z

replaced ip address with map sandbox host name




> Convert fid,uid in MapR's audit log to FIle/folder name, user name
> --
>
> Key: EAGLE-283
> URL: https://issues.apache.org/jira/browse/EAGLE-283
> Project: Eagle
>  Issue Type: New Feature
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> FIle/folder, user's names are not saved in MapR's audit log file, instead, 
> the audit log file keeps FID, UID. 
> Need a converter to resolve the relationship between ids and their actual 
> names.



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

[GitHub] incubator-eagle pull request #321: EAGLE-283: Convert fid,uid in MapR's audi...

2016-08-09 Thread DadanielZ

GitHub user DadanielZ opened a pull request:

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

EAGLE-283: Convert fid,uid in MapR's audit log to FIle/folder name, user 
name

1. Added resolver for user's input of "volume", "file/folder", "Status"
- These resolver provide drop down list for user to select

2. Added NameConvertor to convert user's input to corresponding id and 
saved it in policy
- volume value will be used to call MapR's REST API to get volume id
- status code will be resolved to status id
- file/folder name will be passed to MapR's command line class to get 
its id.

3. Modified UI js file
- As soon as user input a value for "volume", "file", "status", it will 
fetch user's input and call rest service to get corresponding id
- Save ids as a new match criteria in the policy

4. Added maprfs resource resolver to provide drop down list for user

PS:how the id converter works: user select "== '/test'" in field "dst", a 
new match criteria "== 234.567.890" will appear automatically under it, and the 
policy will end up as:
  dst == 'test' or dst == '234.567.890'
Same thing will happen for volume and status input.
In this way, the policy is human readable and can be used to match the ids 
in maprfsAuditLog.

5. Added missing dependency on "commons-lang3" for module "eagle-jpm-util"


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

$ git pull https://github.com/DadanielZ/incubator-eagle EG-283

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

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


commit 936fc5a4eff3cd5bea11c1d15935b124b58b3780
Author: Daniel 
Date:   2016-08-09T22:39:31Z

EAGLE-283: Convert fid,uid in MapR's audit log to FIle/folder name, user 
name

1. Added resolver for user's input of "volume", "file/folder", "Status"
- These resolver provide drop down list for user to select

2. Added NameConvertor to convert user's input to corresponding id and 
saved it in policy
- volume value will be used to call MapR's REST API to get volume id
- status code will be resolved to status id
- file/folder name will be passed to MapR's command line class to get 
its id.

3. Modified UI js file
- As soon as user input a value for "volume", "file", "status", it will 
fetch user's input and call rest service to get corresponding id
- Save ids as a new match criteria in the policy

4. Added maprfs resource resolver to provide drop down list for user

PS:how the id converter works: user select "== '/test'" in field "dst", a 
new match criteria "== 234.567.890" will appear automatically under it, and the 
policy will end up as:
  dst == 'test' or dst == '234.567.890'
Same thing will happen for volume and status input.
In this way, the policy is human readable and can be used to match the ids 
in maprfsAuditLog.

commit 1731469effde0aa88693e7d64f100f3a089b90ac
Author: Daniel 
Date:   2016-08-10T04:03:55Z

Merge pull request #21 from apache/develop

update from Eagle-develop

commit 5cb1a682718835c10135003328bd959004e36cf9
Author: Daniel 
Date:   2016-08-10T04:05:11Z

Merge remote-tracking branch 'origin/EG-283' into EG-283

commit e2c5717a616f668c8db2c31b12d77120e9a4fff7
Author: Daniel 
Date:   2016-08-10T04:38:33Z

Added dependency on "commons-lang3" for module eagle-jpm-util
- mapr build will fail without this dependency

commit f812c4d3b2b9235840c141beb19a3b33743c9720
Author: Daniel 
Date:   2016-08-10T04:46:04Z

replaced ip address with map sandbox host name




---
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-442) Support to extend metastore DAO modules in SPI

2016-08-09 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-442:
---
Labels: app-framework extensibility  (was: app-framework)

> Support to extend metastore DAO modules in SPI
> --
>
> Key: EAGLE-442
> URL: https://issues.apache.org/jira/browse/EAGLE-442
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: app-framework, extensibility
> Fix For: v0.5.0
>
>




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

[jira] [Updated] (EAGLE-442) Support to extend metastore DAO modules in SPI

2016-08-09 Thread Hao Chen (JIRA)


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

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

> Support to extend metastore DAO modules in SPI
> --
>
> Key: EAGLE-442
> URL: https://issues.apache.org/jira/browse/EAGLE-442
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: app-framework
> Fix For: v0.5.0
>
>




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

[jira] [Created] (EAGLE-442) Support to extend metastore DAO modules in SPI

2016-08-09 Thread Hao Chen (JIRA)

Hao Chen created EAGLE-442:
--

 Summary: Support to extend metastore DAO modules in SPI
 Key: EAGLE-442
 URL: https://issues.apache.org/jira/browse/EAGLE-442
 Project: Eagle
  Issue Type: Sub-task
Reporter: Hao Chen
Assignee: Hao Chen






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

[jira] [Updated] (EAGLE-442) Support to extend metastore DAO modules in SPI

2016-08-09 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-442:
---
Labels: app-framework  (was: )

> Support to extend metastore DAO modules in SPI
> --
>
> Key: EAGLE-442
> URL: https://issues.apache.org/jira/browse/EAGLE-442
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: app-framework
> Fix For: v0.5.0
>
>




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

[jira] [Commented] (EAGLE-441) Combine environment configuration into application configuration for execution

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


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

ASF GitHub Bot commented on EAGLE-441:
--

Github user haoch closed the pull request at:

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


> Combine environment configuration into application configuration for execution
> --
>
> Key: EAGLE-441
> URL: https://issues.apache.org/jira/browse/EAGLE-441
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: app-framework
> Fix For: v0.5.0
>
>




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

[jira] [Updated] (EAGLE-441) Combine environment configuration into application configuration for execution

2016-08-09 Thread Hao Chen (JIRA)


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

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

> Combine environment configuration into application configuration for execution
> --
>
> Key: EAGLE-441
> URL: https://issues.apache.org/jira/browse/EAGLE-441
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: app-framework
> Fix For: v0.5.0
>
>




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

[GitHub] incubator-eagle pull request #320: EAGLE-441 AppConfig will override EnvConf...

2016-08-09 Thread haoch

GitHub user haoch opened a pull request:

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

EAGLE-441 AppConfig will override EnvConfig and EnvConfig is default config

https://issues.apache.org/jira/browse/EAGLE-441

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

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

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

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


commit 1de1e91cff6ec0bb224a9f0506e3b8b593e84877
Author: Hao Chen 
Date:   2016-08-10T03:31:26Z

EAGLE-441 appConfig will override envConfig, envConfig is used as default 
config




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-441) Combine environment configuration into application configuration for execution

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


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

ASF GitHub Bot commented on EAGLE-441:
--

GitHub user haoch opened a pull request:

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

EAGLE-441 AppConfig will override EnvConfig and EnvConfig is default config

https://issues.apache.org/jira/browse/EAGLE-441

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

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

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

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


commit 1de1e91cff6ec0bb224a9f0506e3b8b593e84877
Author: Hao Chen 
Date:   2016-08-10T03:31:26Z

EAGLE-441 appConfig will override envConfig, envConfig is used as default 
config




> Combine environment configuration into application configuration for execution
> --
>
> Key: EAGLE-441
> URL: https://issues.apache.org/jira/browse/EAGLE-441
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: app-framework
> Fix For: v0.5.0
>
>




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

[jira] [Updated] (EAGLE-441) Combine environment configuration into application configuration for execution

2016-08-09 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-441:
---
Labels: app-framework  (was: )

> Combine environment configuration into application configuration for execution
> --
>
> Key: EAGLE-441
> URL: https://issues.apache.org/jira/browse/EAGLE-441
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: app-framework
> Fix For: v0.5.0
>
>




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

[GitHub] incubator-eagle pull request #314: EAGLE-436 Decouple Application Class-base...

2016-08-09 Thread haoch

Github user haoch closed the pull request at:

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


---
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-436) Decouple Application Class-based Configuration

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


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

ASF GitHub Bot commented on EAGLE-436:
--

Github user haoch closed the pull request at:

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


> Decouple Application Class-based Configuration
> --
>
> Key: EAGLE-436
> URL: https://issues.apache.org/jira/browse/EAGLE-436
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>




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

[jira] [Commented] (EAGLE-439) Introduce policy enable/disable support

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


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

ASF GitHub Bot commented on EAGLE-439:
--

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/319
  
merged, pls help to close


> Introduce policy enable/disable support
> ---
>
> Key: EAGLE-439
> URL: https://issues.apache.org/jira/browse/EAGLE-439
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Garrett Li
>Assignee: Garrett Li
>




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

[jira] [Commented] (EAGLE-439) Introduce policy enable/disable support

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


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

ASF GitHub Bot commented on EAGLE-439:
--

Github user asfgit closed the pull request at:

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


> Introduce policy enable/disable support
> ---
>
> Key: EAGLE-439
> URL: https://issues.apache.org/jira/browse/EAGLE-439
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Garrett Li
>Assignee: Garrett Li
>




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

[GitHub] incubator-eagle pull request #319: [EAGLE-439] Introduce policy enable/disab...

2016-08-09 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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-435) Coordiantor schedule operation must be exclusive in distributed deployment

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


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

ASF GitHub Bot commented on EAGLE-435:
--

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/317
  
Looks only fix the listener wise. The intension is to guarantee all the 
schedule.build(), not only the listener.


> Coordiantor schedule operation must be exclusive in distributed deployment
> --
>
> Key: EAGLE-435
> URL: https://issues.apache.org/jira/browse/EAGLE-435
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
>  Labels: alert_engine
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>




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

[jira] [Commented] (EAGLE-435) Coordiantor schedule operation must be exclusive in distributed deployment

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


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

ASF GitHub Bot commented on EAGLE-435:
--

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/317
  
Looks only fix the listener wise. The intension is to guarantee all the 
schedule.build(), not only the listener.


> Coordiantor schedule operation must be exclusive in distributed deployment
> --
>
> Key: EAGLE-435
> URL: https://issues.apache.org/jira/browse/EAGLE-435
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
>  Labels: alert_engine
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>




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

[GitHub] incubator-eagle issue #317: [EAGLE-435] make coordiantor schedule operation ...

2016-08-09 Thread RalphSu

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/317
  
Looks only fix the listener wise. The intension is to guarantee all the 
schedule.build(), not only the listener.


---
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 #317: [EAGLE-435] make coordiantor schedule operation ...

2016-08-09 Thread RalphSu

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/317
  
Looks only fix the listener wise. The intension is to guarantee all the 
schedule.build(), not only the listener.


---
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-440) Alert mongodb storage refine

2016-08-09 Thread ZengMing (JIRA)

ZengMing created EAGLE-440:
--

 Summary: Alert mongodb storage refine
 Key: EAGLE-440
 URL: https://issues.apache.org/jira/browse/EAGLE-440
 Project: Eagle
  Issue Type: Improvement
Reporter: ZengMing
Assignee: ZengMing


Currently, some Alert Mongo Collection is too large. Consider future increase, 
need to split large collection to some small collections.

To back compatible, need to keep the interface as the same as before. 



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

[jira] [Commented] (EAGLE-439) Introduce policy enable/disable support

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


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

ASF GitHub Bot commented on EAGLE-439:
--

GitHub user garrettlish opened a pull request:

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

[EAGLE-439] Introduce policy enable/disable support



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

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

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

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


commit 17670acae1ad64ca378e8a60676f027845528dd8
Author: Xiancheng Li 
Date:   2016-08-08T10:00:43Z

[EAGLE-439] Introduce policy enable/disable support




> Introduce policy enable/disable support
> ---
>
> Key: EAGLE-439
> URL: https://issues.apache.org/jira/browse/EAGLE-439
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Garrett Li
>Assignee: Garrett Li
>




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

[GitHub] incubator-eagle pull request #319: [EAGLE-439] Introduce policy enable/disab...

2016-08-09 Thread garrettlish

GitHub user garrettlish opened a pull request:

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

[EAGLE-439] Introduce policy enable/disable support



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

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

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

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


commit 17670acae1ad64ca378e8a60676f027845528dd8
Author: Xiancheng Li 
Date:   2016-08-08T10:00:43Z

[EAGLE-439] Introduce policy enable/disable support




---
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 #318: [EAGLE-439] Introduce policy enable/disab...

2016-08-09 Thread garrettlish

Github user garrettlish closed the pull request at:

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


---
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-439) Introduce policy enable/disable support

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


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

ASF GitHub Bot commented on EAGLE-439:
--

Github user garrettlish closed the pull request at:

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


> Introduce policy enable/disable support
> ---
>
> Key: EAGLE-439
> URL: https://issues.apache.org/jira/browse/EAGLE-439
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Garrett Li
>Assignee: Garrett Li
>




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

[jira] [Commented] (EAGLE-439) Introduce policy enable/disable support

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


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

ASF GitHub Bot commented on EAGLE-439:
--

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

https://github.com/apache/incubator-eagle/pull/318#discussion_r74170914
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/main/java/org/apache/eagle/alert/engine/coordinator/PolicyDefinition.java
 ---
@@ -191,6 +200,10 @@ public String toString() {
 return String.format("{type=\"%s\",value=\"%s\"",type,value);
 }
 }
+
+public static enum PolicyStatus {
+   enabled, disabled
--- End diff --

captilized enum values to follow the code style


> Introduce policy enable/disable support
> ---
>
> Key: EAGLE-439
> URL: https://issues.apache.org/jira/browse/EAGLE-439
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Garrett Li
>Assignee: Garrett Li
>




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

[GitHub] incubator-eagle pull request #318: [EAGLE-439] Introduce policy enable/disab...

2016-08-09 Thread RalphSu

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

https://github.com/apache/incubator-eagle/pull/318#discussion_r74170914
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/main/java/org/apache/eagle/alert/engine/coordinator/PolicyDefinition.java
 ---
@@ -191,6 +200,10 @@ public String toString() {
 return String.format("{type=\"%s\",value=\"%s\"",type,value);
 }
 }
+
+public static enum PolicyStatus {
+   enabled, disabled
--- End diff --

captilized enum values to follow the code style


---
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 #313: [EAGLE-434] fix policy change listener da...

2016-08-09 Thread garrettlish

Github user garrettlish closed the pull request at:

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


---
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-434) BUG: periodically trigger schedule in service mode

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


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

ASF GitHub Bot commented on EAGLE-434:
--

Github user garrettlish closed the pull request at:

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


> BUG: periodically trigger schedule in service mode
> --
>
> Key: EAGLE-434
> URL: https://issues.apache.org/jira/browse/EAGLE-434
> Project: Eagle
>  Issue Type: Bug
>Reporter: Garrett Li
>Assignee: Garrett Li
>  Labels: alert_engine
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> the periodical trigger schedule is not started



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

[jira] [Commented] (EAGLE-439) Introduce policy enable/disable support

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


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

ASF GitHub Bot commented on EAGLE-439:
--

GitHub user garrettlish opened a pull request:

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

[EAGLE-439] Introduce policy enable/disable support



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

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

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

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


commit ccd0d0aea37e7eac0b50c6d46b6db3309b05cc37
Author: Xiancheng Li 
Date:   2016-08-08T10:00:43Z

[EAGLE-439] Introduce policy enable/disable support




> Introduce policy enable/disable support
> ---
>
> Key: EAGLE-439
> URL: https://issues.apache.org/jira/browse/EAGLE-439
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Garrett Li
>Assignee: Garrett Li
>




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

[GitHub] incubator-eagle pull request #318: [EAGLE-439] Introduce policy enable/disab...

2016-08-09 Thread garrettlish

GitHub user garrettlish opened a pull request:

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

[EAGLE-439] Introduce policy enable/disable support



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

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

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

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


commit ccd0d0aea37e7eac0b50c6d46b6db3309b05cc37
Author: Xiancheng Li 
Date:   2016-08-08T10:00:43Z

[EAGLE-439] Introduce policy enable/disable support




---
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-439) Introduce policy enable/disable support

2016-08-09 Thread Garrett Li (JIRA)

Garrett Li created EAGLE-439:


 Summary: Introduce policy enable/disable support
 Key: EAGLE-439
 URL: https://issues.apache.org/jira/browse/EAGLE-439
 Project: Eagle
  Issue Type: Improvement
Reporter: Garrett Li
Assignee: Garrett Li






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

[jira] [Commented] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

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


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

ASF GitHub Bot commented on EAGLE-438:
--

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/316
  
otherwise, looks good to me.
+1


> Multiple Inputs for Hadoop JMX Collector Python Script
> --
>
> Key: EAGLE-438
> URL: https://issues.apache.org/jira/browse/EAGLE-438
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Peter Kim
>Priority: Trivial
>  Labels: features
>
> It would be very useful for the hadoop jmx collector to be able to collect 
> jmx metrics for multiple components at once. So here, I wish to extend the 
> default python script that collects Hadoop JMX Metrics to support multiple 
> inputs as oppose to only one. So, with this, one can collect all jmx metrics 
> for multiple components such as namenode, datanode, resource manager, 
> hmaster, etc. all at once. 



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

[GitHub] incubator-eagle issue #316: [EAGLE-438] Multiple Inputs for Hadoop JMX Colle...

2016-08-09 Thread RalphSu

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/316
  
otherwise, looks good to me.
+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] [Commented] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

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


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

ASF GitHub Bot commented on EAGLE-438:
--

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

https://github.com/apache/incubator-eagle/pull/316#discussion_r74164639
  
--- Diff: eagle-external/hadoop_jmx_collector/config-sample.json ---
@@ -12,18 +12,35 @@
"https":false
  }
},
-   "input": {
-"component": "namenode",
-"port": "50070",
-"https": false
-   },
+   "inputs": [
+  {
+"component": "namenode",
+"host": "127.0.0.1",
+"port": "50070",
+"https": false,
+"kafka_topic": "nn_jmx_metric_sandbox"
+  },
+  {
+"component": "resourcemanager",
+"host": "127.0.0.1",
+"port": "8088",
+"https": false,
+"kafka_topic": "rm_jmx_metric_sandbox"
+  },
+  {
+"component": "datanode",
+"host": "127.0.0.1",
--- End diff --

let's use place holder like what we do in PR312, use 
server.eagle.apache.org. So that developer could simply use /etc/resolv.conf 
when there is different endpoint he want to change (etc, hdp sandbox)


> Multiple Inputs for Hadoop JMX Collector Python Script
> --
>
> Key: EAGLE-438
> URL: https://issues.apache.org/jira/browse/EAGLE-438
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Peter Kim
>Priority: Trivial
>  Labels: features
>
> It would be very useful for the hadoop jmx collector to be able to collect 
> jmx metrics for multiple components at once. So here, I wish to extend the 
> default python script that collects Hadoop JMX Metrics to support multiple 
> inputs as oppose to only one. So, with this, one can collect all jmx metrics 
> for multiple components such as namenode, datanode, resource manager, 
> hmaster, etc. all at once. 



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

[GitHub] incubator-eagle pull request #316: [EAGLE-438] Multiple Inputs for Hadoop JM...

2016-08-09 Thread RalphSu

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

https://github.com/apache/incubator-eagle/pull/316#discussion_r74164639
  
--- Diff: eagle-external/hadoop_jmx_collector/config-sample.json ---
@@ -12,18 +12,35 @@
"https":false
  }
},
-   "input": {
-"component": "namenode",
-"port": "50070",
-"https": false
-   },
+   "inputs": [
+  {
+"component": "namenode",
+"host": "127.0.0.1",
+"port": "50070",
+"https": false,
+"kafka_topic": "nn_jmx_metric_sandbox"
+  },
+  {
+"component": "resourcemanager",
+"host": "127.0.0.1",
+"port": "8088",
+"https": false,
+"kafka_topic": "rm_jmx_metric_sandbox"
+  },
+  {
+"component": "datanode",
+"host": "127.0.0.1",
--- End diff --

let's use place holder like what we do in PR312, use 
server.eagle.apache.org. So that developer could simply use /etc/resolv.conf 
when there is different endpoint he want to change (etc, hdp sandbox)


---
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 #316: [EAGLE-438] Multiple Inputs for Hadoop JM...

2016-08-09 Thread peterkim95

GitHub user peterkim95 opened a pull request:

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

[EAGLE-438] Multiple Inputs for Hadoop JMX Collector Python Script

https://issues.apache.org/jira/browse/EAGLE-438

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

$ git pull https://github.com/peterkim95/incubator-eagle jmx

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

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


commit 8db6fa2705f7890091951f357aff888061ede1d6
Author: Peter Kim 
Date:   2016-08-09T22:57:39Z

add support for multiple jmx inputs and kafka topics




---
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-438) Multiple Inputs for Hadoop JMX Collector Python Script

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


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

ASF GitHub Bot commented on EAGLE-438:
--

GitHub user peterkim95 opened a pull request:

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

[EAGLE-438] Multiple Inputs for Hadoop JMX Collector Python Script

https://issues.apache.org/jira/browse/EAGLE-438

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

$ git pull https://github.com/peterkim95/incubator-eagle jmx

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

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


commit 8db6fa2705f7890091951f357aff888061ede1d6
Author: Peter Kim 
Date:   2016-08-09T22:57:39Z

add support for multiple jmx inputs and kafka topics




> Multiple Inputs for Hadoop JMX Collector Python Script
> --
>
> Key: EAGLE-438
> URL: https://issues.apache.org/jira/browse/EAGLE-438
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Peter Kim
>Priority: Trivial
>  Labels: features
>
> It would be very useful for the hadoop jmx collector to be able to collect 
> jmx metrics for multiple components at once. So here, I wish to extend the 
> default python script that collects Hadoop JMX Metrics to support multiple 
> inputs as oppose to only one. So, with this, one can collect all jmx metrics 
> for multiple components such as namenode, datanode, resource manager, 
> hmaster, etc. all at once. 



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

[jira] [Comment Edited] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

2016-08-09 Thread Peter Kim (JIRA)


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

Peter Kim edited comment on EAGLE-438 at 8/9/16 10:02 PM:
--

Yes, in the config.json file that the script uses, the inputs will be an array 
of components as such

"inputs": [
  {
"component": "namenode",
"host": "127.0.0.1",
"port": "50070",
"https": false
  },
  {
"component": "resourcemanager",
"host": "127.0.0.1",
"port": "8088",
"https": false
  },
  {
"component": "datanode",
"host": "127.0.0.1",
"port": "50075",
"https": false
  }
   ]

For your other question, I could also make it so that different components can 
send it to different kafka topics. So make the kafka output area in the json 
file into an array as well


was (Author: petkim):
Yes, in the config.json file that the script uses, the inputs will be an array 
of components as such

"inputs": [
  {
"component": "namenode",
"host": "127.0.0.1",
"port": "50070",
"https": false
  },
  {
"component": "resourcemanager",
"host": "127.0.0.1",
"port": "8088",
"https": false
  },
  {
"component": "datanode",
"host": "127.0.0.1",
"port": "50075",
"https": false
  }
   ]

For your other question, I could also make it so that different components can 
send it to different kafka topics. So make the kafka output area in the json 
file into an array

> Multiple Inputs for Hadoop JMX Collector Python Script
> --
>
> Key: EAGLE-438
> URL: https://issues.apache.org/jira/browse/EAGLE-438
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Peter Kim
>Priority: Trivial
>  Labels: features
>
> It would be very useful for the hadoop jmx collector to be able to collect 
> jmx metrics for multiple components at once. So here, I wish to extend the 
> default python script that collects Hadoop JMX Metrics to support multiple 
> inputs as oppose to only one. So, with this, one can collect all jmx metrics 
> for multiple components such as namenode, datanode, resource manager, 
> hmaster, etc. all at once. 



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

[jira] [Commented] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

2016-08-09 Thread Peter Kim (JIRA)


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

Peter Kim commented on EAGLE-438:
-

Yes, in the config.json file that the script uses, the inputs will be an array 
of components as such

"inputs": [
  {
"component": "namenode",
"host": "127.0.0.1",
"port": "50070",
"https": false
  },
  {
"component": "resourcemanager",
"host": "127.0.0.1",
"port": "8088",
"https": false
  },
  {
"component": "datanode",
"host": "127.0.0.1",
"port": "50075",
"https": false
  }
   ]

For your other question, I could also make it so that different components can 
send it to different kafka topics. So make the kafka output area in the json 
file into an array

> Multiple Inputs for Hadoop JMX Collector Python Script
> --
>
> Key: EAGLE-438
> URL: https://issues.apache.org/jira/browse/EAGLE-438
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Peter Kim
>Priority: Trivial
>  Labels: features
>
> It would be very useful for the hadoop jmx collector to be able to collect 
> jmx metrics for multiple components at once. So here, I wish to extend the 
> default python script that collects Hadoop JMX Metrics to support multiple 
> inputs as oppose to only one. So, with this, one can collect all jmx metrics 
> for multiple components such as namenode, datanode, resource manager, 
> hmaster, etc. all at once. 



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

[jira] [Commented] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

2016-08-09 Thread Edward Zhang (JIRA)


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

Edward Zhang commented on EAGLE-438:


[~senthilec566] I think we already have resource manager related script?
[~petkim] are you going to have all components share the same script? but they 
are using different topic right?

> Multiple Inputs for Hadoop JMX Collector Python Script
> --
>
> Key: EAGLE-438
> URL: https://issues.apache.org/jira/browse/EAGLE-438
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Peter Kim
>Priority: Trivial
>  Labels: features
>
> It would be very useful for the hadoop jmx collector to be able to collect 
> jmx metrics for multiple components at once. So here, I wish to extend the 
> default python script that collects Hadoop JMX Metrics to support multiple 
> inputs as oppose to only one. So, with this, one can collect all jmx metrics 
> for multiple components such as namenode, datanode, resource manager, 
> hmaster, etc. all at once. 



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

[jira] [Created] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

2016-08-09 Thread Peter Kim (JIRA)

Peter Kim created EAGLE-438:
---

 Summary: Multiple Inputs for Hadoop JMX Collector Python Script
 Key: EAGLE-438
 URL: https://issues.apache.org/jira/browse/EAGLE-438
 Project: Eagle
  Issue Type: New Feature
Reporter: Peter Kim
Priority: Trivial


It would be very useful for the hadoop jmx collector to be able to collect jmx 
metrics for multiple components at once. So here, I wish to extend the default 
python script that collects Hadoop JMX Metrics to support multiple inputs as 
oppose to only one. So, with this, one can collect all jmx metrics for multiple 
components such as namenode, datanode, resource manager, hmaster, etc. all at 
once. 



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

[jira] [Created] (EAGLE-437) create workable fat jar for starting application remotely

2016-08-09 Thread Edward Zhang (JIRA)

Edward Zhang created EAGLE-437:
--

 Summary: create workable fat jar for starting application remotely
 Key: EAGLE-437
 URL: https://issues.apache.org/jira/browse/EAGLE-437
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


Explore ways to package fat jar for starting applications
1) package all topology jars together into one single fat jar. Need fix
   a. metadata.xml should be differentiated by different directory, for example 
metadata.xml is under directory of /META-INF/apps//metadata.xml
   b. SPI configuration file should be removed and ApplicationProviderSPILoader 
should be redesign to get all providers

2) package fat jar on demand.
No far jar after packaging.
Need remember all dependent jars and write code to package fat jar on demand



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

[jira] [Commented] (EAGLE-430) explore new packaging method for eagle using new app framework

2016-08-09 Thread Edward Zhang (JIRA)


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

Edward Zhang commented on EAGLE-430:


We should think about fat jar packaging process.
When we package, metadata.xml and SPI file are overridden with each other.
One solution is to build fat jar on-demand when we start an application in 
remote.
When we do package on-demand, we should know all names of dependent jars and 
try to package them together.
This is not scope for this ticket, will have another ticket for this problem

> explore new packaging method for eagle using new app framework
> --
>
> Key: EAGLE-430
> URL: https://issues.apache.org/jira/browse/EAGLE-430
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> New app framework will manage application jars in central place, while 
> application jars include topology jars and web jars. 
> We need figure out Eagle 0.5 binary layout.
> The goal is with only Eagle 0.5 server we can start any topology remotely.
> /eagle-server
> /conf  (application.conf)
> /bin(add class path)
> /lib
>/eagle-server.jar
>/apps
> app1.jar
> app1-web.jar
> app2.jar
> /web
> index.html
> /js



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

[jira] [Commented] (EAGLE-430) explore new packaging method for eagle using new app framework

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


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

ASF GitHub Bot commented on EAGLE-430:
--

GitHub user yonzhang opened a pull request:

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

explore new packaging method for eagle using new app framework

https://issues.apache.org/jira/browse/EAGLE-430

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

$ git pull https://github.com/yonzhang/incubator-eagle develop

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

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


commit e8de594c2420108ba26e70cf6151356eb4abf788
Author: yonzhang 
Date:   2016-08-09T01:04:57Z

Hbase monitoring metadata browse API in new app framework

commit c57242bc76931dfc73d7806a66d1ebeffdb0d4f2
Author: yonzhang 
Date:   2016-08-09T20:00:44Z

first version of eagle server assembly

commit 8fdf4626d15b54a3490504614ef0a02231f6a814
Author: yonzhang 
Date:   2016-08-09T20:34:35Z

Merge remote-tracking branch 'upstream/develop' into develop




> explore new packaging method for eagle using new app framework
> --
>
> Key: EAGLE-430
> URL: https://issues.apache.org/jira/browse/EAGLE-430
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> New app framework will manage application jars in central place, while 
> application jars include topology jars and web jars. 
> We need figure out Eagle 0.5 binary layout.
> The goal is with only Eagle 0.5 server we can start any topology remotely.
> /eagle-server
> /conf  (application.conf)
> /bin(add class path)
> /lib
>/eagle-server.jar
>/apps
> app1.jar
> app1-web.jar
> app2.jar
> /web
> index.html
> /js



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

[GitHub] incubator-eagle pull request #315: explore new packaging method for eagle us...

2016-08-09 Thread yonzhang

GitHub user yonzhang opened a pull request:

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

explore new packaging method for eagle using new app framework

https://issues.apache.org/jira/browse/EAGLE-430

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

$ git pull https://github.com/yonzhang/incubator-eagle develop

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

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


commit e8de594c2420108ba26e70cf6151356eb4abf788
Author: yonzhang 
Date:   2016-08-09T01:04:57Z

Hbase monitoring metadata browse API in new app framework

commit c57242bc76931dfc73d7806a66d1ebeffdb0d4f2
Author: yonzhang 
Date:   2016-08-09T20:00:44Z

first version of eagle server assembly

commit 8fdf4626d15b54a3490504614ef0a02231f6a814
Author: yonzhang 
Date:   2016-08-09T20:34:35Z

Merge remote-tracking branch 'upstream/develop' into develop




---
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-436) Decouple Application Class-based Configuration

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


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

ASF GitHub Bot commented on EAGLE-436:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/314
  
Good refinement, good to go


> Decouple Application Class-based Configuration
> --
>
> Key: EAGLE-436
> URL: https://issues.apache.org/jira/browse/EAGLE-436
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>




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

[jira] [Commented] (EAGLE-428) Hbase monitoring's metadata browse API in new app framework

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


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

ASF GitHub Bot commented on EAGLE-428:
--

Github user yonzhang closed the pull request at:

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


> Hbase monitoring's metadata browse API in new app framework
> ---
>
> Key: EAGLE-428
> URL: https://issues.apache.org/jira/browse/EAGLE-428
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> Hbase monitoring's metadata browse API is used for retrieve hbase's table, 
> column etc, and check against sensitivity type.
> We should use the configuration from ApplicationEntity to manage metadata 
> query



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

[GitHub] incubator-eagle pull request #312: Hbase monitoring metadata browse API in n...

2016-08-09 Thread yonzhang

Github user yonzhang closed the pull request at:

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


---
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 #314: EAGLE-436 Decouple Application Class-based Confi...

2016-08-09 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/314
  
Good refinement, good to go


---
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 #312: Hbase monitoring metadata browse API in new app ...

2016-08-09 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/312
  
That is obvious. Again this is to make first use case to work, I will leave 
this change to app framework refine.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[EAGLE BUILD FAILED] incubator-eagle-develop failed on build #11

2016-08-09 Thread Apache Jenkins Server

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

[GitHub] incubator-eagle pull request #312: Hbase monitoring metadata browse API in n...

2016-08-09 Thread haoch

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

https://github.com/apache/incubator-eagle/pull/312#discussion_r74025706
  
--- Diff: eagle-server/src/main/resources/application.conf ---
@@ -42,6 +42,7 @@
"metadata":{
"store": 
"org.apache.eagle.metadata.service.memory.MemoryMetadataStore"
},
+   "connection":"jdbc:mysql://server.eagle.apache.org:3306/eagle",
--- End diff --

Yes, I meant

```
metadata{
   connection: "jdbc:mysql://server.eagle.apache.org:3306/eagle"
}
```


---
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 #314: EAGLE-436 Decouple Application Class-base...

2016-08-09 Thread haoch

GitHub user haoch opened a pull request:

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

EAGLE-436 Decouple Application Class-based Configuration

https://issues.apache.org/jira/browse/EAGLE-436

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

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

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

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


commit 5b7cf17335e8472a317ecfb8c9de0d2d50ece196
Author: Hao Chen 
Date:   2016-08-09T09:20:25Z

EAGLE-436 Decouple Application Class-based Configuration A




---
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-436) Decouple Application Class-based Configuration

2016-08-09 Thread Hao Chen (JIRA)

Hao Chen created EAGLE-436:
--

 Summary: Decouple Application Class-based Configuration
 Key: EAGLE-436
 URL: https://issues.apache.org/jira/browse/EAGLE-436
 Project: Eagle
  Issue Type: New Feature
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0






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

[GitHub] incubator-eagle pull request #312: Hbase monitoring metadata browse API in n...

2016-08-09 Thread RalphSu

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

https://github.com/apache/incubator-eagle/pull/312#discussion_r74022788
  
--- Diff: eagle-server/src/main/resources/application.conf ---
@@ -42,6 +42,7 @@
"metadata":{
"store": 
"org.apache.eagle.metadata.service.memory.MemoryMetadataStore"
},
+   "connection":"jdbc:mysql://server.eagle.apache.org:3306/eagle",
--- End diff --

Suggest use nest {}


---
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 #312: Hbase monitoring metadata browse API in n...

2016-08-09 Thread haoch

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

https://github.com/apache/incubator-eagle/pull/312#discussion_r74021223
  
--- Diff: eagle-server/src/main/resources/application.conf ---
@@ -42,6 +42,7 @@
"metadata":{
"store": 
"org.apache.eagle.metadata.service.memory.MemoryMetadataStore"
},
+   "connection":"jdbc:mysql://server.eagle.apache.org:3306/eagle",
--- End diff --

Could we move the `connection` into `metadata.connection`?


---
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 #312: Hbase monitoring metadata browse API in new app ...

2016-08-09 Thread haoch

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/312
  
LGTM, except:

1. MetadataDaoFactory, but we could refactor this later
2. Prefer to rename configuration key "connection" as "metadata.connection"

If we want to use json-style configuration, we should well org 
configuration by `{}` object group.


---
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] [Assigned] (EAGLE-434) BUG: periodically trigger schedule in service mode

2016-08-09 Thread Garrett Li (JIRA)


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

Garrett Li reassigned EAGLE-434:


Assignee: Garrett Li

> BUG: periodically trigger schedule in service mode
> --
>
> Key: EAGLE-434
> URL: https://issues.apache.org/jira/browse/EAGLE-434
> Project: Eagle
>  Issue Type: Bug
>Reporter: Garrett Li
>Assignee: Garrett Li
>  Labels: alert_engine
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> the periodical trigger schedule is not started



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

[jira] [Commented] (EAGLE-434) BUG: periodically trigger schedule in service mode

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


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

ASF GitHub Bot commented on EAGLE-434:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/313
  
LGTM.


> BUG: periodically trigger schedule in service mode
> --
>
> Key: EAGLE-434
> URL: https://issues.apache.org/jira/browse/EAGLE-434
> Project: Eagle
>  Issue Type: Bug
>Reporter: Garrett Li
>  Labels: alert_engine
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> the periodical trigger schedule is not started



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

[jira] [Updated] (EAGLE-435) Coordiantor schedule operation must be exclusive in distributed deployment

2016-08-09 Thread Hao Chen (JIRA)


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

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

> Coordiantor schedule operation must be exclusive in distributed deployment
> --
>
> Key: EAGLE-435
> URL: https://issues.apache.org/jira/browse/EAGLE-435
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
>  Labels: alert_engine
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>




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

[GitHub] incubator-eagle issue #313: [EAGLE-434] fix policy change listener daemon no...

2016-08-09 Thread haoch

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/313
  
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] [Updated] (EAGLE-435) Coordiantor schedule operation must be exclusive in distributed deployment

2016-08-09 Thread Hao Chen (JIRA)


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

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

> Coordiantor schedule operation must be exclusive in distributed deployment
> --
>
> Key: EAGLE-435
> URL: https://issues.apache.org/jira/browse/EAGLE-435
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
>  Labels: alert_engine
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>




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

[jira] [Updated] (EAGLE-435) Coordiantor schedule operation must be exclusive in distributed deployment

2016-08-09 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-435:
---
Assignee: Garrett Li

> Coordiantor schedule operation must be exclusive in distributed deployment
> --
>
> Key: EAGLE-435
> URL: https://issues.apache.org/jira/browse/EAGLE-435
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Garrett Li
>Assignee: Garrett Li
>  Labels: alert_engine
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>




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

Re: Request EAGLE JIRA assignee permission

2016-08-09 Thread Hao Chen

Garrett, it's done, pls. have a try.

- Hao

On Tue, Aug 9, 2016 at 4:07 PM, Garrett Li  wrote:

> Hi all,
>
>
> This is Garrett Li, I am going to work on UMP alerting part, I would like
> to request EAGLE JIRA assignee permission, my account in issues.apache.org
> is garrettlish (garrettl...@163.com). Thanks a lot!
>
>
> Thanks,
> Garrett

Request EAGLE JIRA assignee permission

2016-08-09 Thread Garrett Li

Hi all,


This is Garrett Li, I am going to work on UMP alerting part, I would like to 
request EAGLE JIRA assignee permission, my account in issues.apache.org is 
garrettlish (garrettl...@163.com). Thanks a lot!


Thanks,
Garrett

[jira] [Updated] (EAGLE-435) Coordiantor schedule operation must be exclusive in distributed deployment

2016-08-09 Thread Garrett Li (JIRA)


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

Garrett Li updated EAGLE-435:
-
Issue Type: Improvement  (was: Bug)
   Summary: Coordiantor schedule operation must be exclusive in distributed 
deployment  (was: Enhancement: coordiantor schedule operation must be exclusive 
in distributed deployment)

> Coordiantor schedule operation must be exclusive in distributed deployment
> --
>
> Key: EAGLE-435
> URL: https://issues.apache.org/jira/browse/EAGLE-435
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Garrett Li
>  Labels: alert_engine
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>




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

[jira] [Created] (EAGLE-435) Enhancement: coordiantor schedule operation must be exclusive in distributed deployment

2016-08-09 Thread Garrett Li (JIRA)

Garrett Li created EAGLE-435:


 Summary: Enhancement: coordiantor schedule operation must be 
exclusive in distributed deployment
 Key: EAGLE-435
 URL: https://issues.apache.org/jira/browse/EAGLE-435
 Project: Eagle
  Issue Type: Bug
Reporter: Garrett Li






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

[jira] [Commented] (EAGLE-434) BUG: periodically trigger schedule in service mode

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


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

ASF GitHub Bot commented on EAGLE-434:
--

GitHub user garrettlish opened a pull request:

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

[EAGLE-434] fix policy change listener daemon not working issue



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

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

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

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


commit 475f19afef034ec4bc9bbf2240b50c1999a600b0
Author: Xiancheng Li 
Date:   2016-08-04T03:04:36Z

[EAGLE-434] fix policy change listener daemon not working issue




> BUG: periodically trigger schedule in service mode
> --
>
> Key: EAGLE-434
> URL: https://issues.apache.org/jira/browse/EAGLE-434
> Project: Eagle
>  Issue Type: Bug
>Reporter: Garrett Li
>  Labels: alert_engine
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> the periodical trigger schedule is not started



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

[GitHub] incubator-eagle pull request #313: [EAGLE-434] fix policy change listener da...

2016-08-09 Thread garrettlish

GitHub user garrettlish opened a pull request:

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

[EAGLE-434] fix policy change listener daemon not working issue



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

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

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

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


commit 475f19afef034ec4bc9bbf2240b50c1999a600b0
Author: Xiancheng Li 
Date:   2016-08-04T03:04:36Z

[EAGLE-434] fix policy change listener daemon not working issue




---
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-434) BUG: periodically trigger schedule in service mode

2016-08-09 Thread Garrett Li (JIRA)


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

Garrett Li updated EAGLE-434:
-
Labels: alert_engine  (was: )

> BUG: periodically trigger schedule in service mode
> --
>
> Key: EAGLE-434
> URL: https://issues.apache.org/jira/browse/EAGLE-434
> Project: Eagle
>  Issue Type: Bug
>Reporter: Garrett Li
>  Labels: alert_engine
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> the periodical trigger schedule is not started



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

[jira] [Commented] (EAGLE-411) Refactor hbase related unit test cases with mockito and mini-hbase

2016-08-09 Thread Chang chen (JIRA)


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

Chang chen commented on EAGLE-411:
--

[~haoch] Sure

> Refactor hbase related unit test cases with mockito and mini-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] [Updated] (EAGLE-427) Query startTime & endTime should support timestamp

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


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

Zhao, Qingwen updated EAGLE-427:

Summary: Query startTime & endTime should support timestamp   (was: Query 
startTime & endTime should support long )

> Query startTime & endTime should support timestamp 
> ---
>
> Key: EAGLE-427
> URL: https://issues.apache.org/jira/browse/EAGLE-427
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> For TimeSeries metrics/entities query, users are required to provide the 
> startTime string and endTime string with the format "-mm-dd hh:MM:ss"
> e.g.  startTime=2016-07-25 06:00:00=2017-08-25 23:59:59
> Eagle should support long timestamp. For example:
> startTime=12423223232343 & endTime=12322435439888



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

[jira] [Updated] (EAGLE-433) DropWizard Service Security Integration with Basic Auth & LDAP

2016-08-09 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-433:
---
Labels: contributers-welcome  (was: )

> DropWizard Service Security Integration with Basic Auth & LDAP
> --
>
> Key: EAGLE-433
> URL: https://issues.apache.org/jira/browse/EAGLE-433
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: contributers-welcome
> Fix For: v0.5.0
>
>
> Eagle Authentication should support Basic Auth and integrate with: 
> * Configure file based username-password setting
> * LDAP: https://github.com/yammer/dropwizard-auth-ldap



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

[jira] [Commented] (EAGLE-411) Refactor hbase related unit test cases with mockito and mini-hbase

2016-08-09 Thread Hao Chen (JIRA)


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

Hao Chen commented on EAGLE-411:


[~baibaichen] could you please let your team start with this ticket about unit 
test cases?

> Refactor hbase related unit test cases with mockito and mini-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] [Updated] (EAGLE-411) Refactor hbase related unit test cases with mockito and mini-hbase

2016-08-09 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-411:
---
Assignee: Chang chen  (was: JiJun Tang)

> Refactor hbase related unit test cases with mockito and mini-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] [Updated] (EAGLE-433) DropWizard Service Security Integration with Basic Auth & LDAP

2016-08-09 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-433:
---
Description: 
Eagle Authentication should support Basic Auth and integrate with: 
* Configure file based username-password setting
* LDAP: https://github.com/yammer/dropwizard-auth-ldap

  was:https://github.com/yammer/dropwizard-auth-ldap


> DropWizard Service Security Integration with Basic Auth & LDAP
> --
>
> Key: EAGLE-433
> URL: https://issues.apache.org/jira/browse/EAGLE-433
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Eagle Authentication should support Basic Auth and integrate with: 
> * Configure file based username-password setting
> * LDAP: https://github.com/yammer/dropwizard-auth-ldap



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

[jira] [Updated] (EAGLE-433) DropWizard Service Security Integration with Basic Auth & LDAP

2016-08-09 Thread Hao Chen (JIRA)


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

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

> DropWizard Service Security Integration with Basic Auth & LDAP
> --
>
> Key: EAGLE-433
> URL: https://issues.apache.org/jira/browse/EAGLE-433
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> https://github.com/yammer/dropwizard-auth-ldap



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

[jira] [Updated] (EAGLE-433) DropWizard Service Security Integration with Basic Auth & LDAP

2016-08-09 Thread Hao Chen (JIRA)


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

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

> DropWizard Service Security Integration with Basic Auth & LDAP
> --
>
> Key: EAGLE-433
> URL: https://issues.apache.org/jira/browse/EAGLE-433
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> https://github.com/yammer/dropwizard-auth-ldap



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

79 matches

Mail list logo