[GitHub] incubator-eagle issue #299: fix policy change listener daemon not working is...

[RalphSu]

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/299
  
 Looks this PR contains commits not merged well. Could we use another pr?


---
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 #287: EAGLE-404: Updating configuration format check a...

[yonzhang]

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/287
  
ok, thanks, please merge it soon


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

[jira] [Commented] (EAGLE-404) Updating configuration format check at the front end

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-404:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/287
  
ok, thanks, please merge it soon


> Updating configuration format check at the front end
> 
>
> Key: EAGLE-404
> URL: https://issues.apache.org/jira/browse/EAGLE-404
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.4.0
>
>
> Since Eagle 0.4.0, we change the configuration format of applications from 
> json format to java properties. 
> For example: 
> key1=value1
> key2=value2
> ...
> During the format checking, eagle allows key string consisting of letter, 
> digits, and dot. This does not work for some properties containing '-'. For 
> example, namenode host may be 'host1.domain-1'



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

[jira] [Created] (EAGLE-409) Automatically recognized eagle service url with http://

[Huizhi Lu (JIRA)]

Huizhi Lu created EAGLE-409:
---

 Summary: Automatically recognized eagle service url with http://
 Key: EAGLE-409
 URL: https://issues.apache.org/jira/browse/EAGLE-409
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Huizhi Lu
Assignee: Huizhi Lu


When setting eagle service to http://host.domain.com instead of 
host.domain.com, eagle can not recognize the link which would be 
http://http://host.domain.com.

This should be automatically recognized.



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

[jira] [Updated] (EAGLE-409) Automatically recognized eagle service url with http://

[Huizhi Lu (JIRA)]

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

Huizhi Lu updated EAGLE-409:

Description: 
When setting eagle service to http://host.domain.com instead of 
host.domain.com, eagle can not recognize the link which would be 
http://http://host.domain.com.
If port is set to 443, "https://"; should be added to the url.

This should be automatically recognized.

  was:
When setting eagle service to http://host.domain.com instead of 
host.domain.com, eagle can not recognize the link which would be 
http://http://host.domain.com.

This should be automatically recognized.


> Automatically recognized eagle service url with http://
> ---
>
> Key: EAGLE-409
> URL: https://issues.apache.org/jira/browse/EAGLE-409
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Huizhi Lu
>Assignee: Huizhi Lu
>
> When setting eagle service to http://host.domain.com instead of 
> host.domain.com, eagle can not recognize the link which would be 
> http://http://host.domain.com.
> If port is set to 443, "https://"; should be added to the url.
> This should be automatically recognized.



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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

GitHub user DadanielZ opened a pull request:

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

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

Eg: after 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 for volume and status input.
In this way, the policy is human readable and can be used to match the 
ids in maprfsAuditLog for monitoring.

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

5. Added license for 
"/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java"
 to pass rat check.

For user id conversion I haven't come up with a perfect solution, this is 
because:
- As user id is more OS standard staff, user might need to make OS calls to 
get the user ids.
- If user use LDAP, it will make it easier as we can query that directly.

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

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

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

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


commit c6d10261e5ba32bf22c1fcee07c8c0ebf6f43a68
Author: Daniel 
Date:   2016-07-05T18:11:12Z

Merge pull request #12 from apache/develop

EAGLE-276 eagle support for mr & spark history job monitoring

commit 92d7a14a529b17608f018fb624039bb9115b9dff
Author: Daniel 
Date:   2016-07-21T05:18:22Z

Merge pull request #13 from apache/develop

update from Eagle develop

commit 2d97d281ec10eb24dca76f64557733d412ce6a19
Author: Daniel 
Date:   2016-07-28T17:56:52Z

Merge pull request #14 from apache/develop

update from eagle-develop

commit 1e2e6a98569d2000f3561c420067e2f926fa2a75
Author: Daniel 
Date:   2016-07-29T19:38:01Z

Merge pull request #15 from apache/develop

update from apache-eagle develop branch

commit 55b6e1d8279be9b72b3958c52fc36bbe72a2ceb0
Author: Daniel 
Date:   2016-08-04T05:10:29Z

Merge pull request #16 from apache/develop

update from eagle-develop

commit 7340451cbb0621bfc1eebae1deeed730349ee8a6
Author: Daniel 
Date:   2016-08-04T21:19:37Z

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

Eg: 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 for volume and status input.
In this way, the policy is human readable and can be used to match the 
ids in maprfsAuditLog.

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

5. Added license for 
"/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java"
 to pass rat check.




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

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

[DadanielZ]

GitHub user DadanielZ opened a pull request:

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

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

Eg: after 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 for volume and status input.
In this way, the policy is human readable and can be used to match the 
ids in maprfsAuditLog for monitoring.

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

5. Added license for 
"/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java"
 to pass rat check.

For user id conversion I haven't come up with a perfect solution, this is 
because:
- As user id is more OS standard staff, user might need to make OS calls to 
get the user ids.
- If user use LDAP, it will make it easier as we can query that directly.

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

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

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

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


commit c6d10261e5ba32bf22c1fcee07c8c0ebf6f43a68
Author: Daniel 
Date:   2016-07-05T18:11:12Z

Merge pull request #12 from apache/develop

EAGLE-276 eagle support for mr & spark history job monitoring

commit 92d7a14a529b17608f018fb624039bb9115b9dff
Author: Daniel 
Date:   2016-07-21T05:18:22Z

Merge pull request #13 from apache/develop

update from Eagle develop

commit 2d97d281ec10eb24dca76f64557733d412ce6a19
Author: Daniel 
Date:   2016-07-28T17:56:52Z

Merge pull request #14 from apache/develop

update from eagle-develop

commit 1e2e6a98569d2000f3561c420067e2f926fa2a75
Author: Daniel 
Date:   2016-07-29T19:38:01Z

Merge pull request #15 from apache/develop

update from apache-eagle develop branch

commit 55b6e1d8279be9b72b3958c52fc36bbe72a2ceb0
Author: Daniel 
Date:   2016-08-04T05:10:29Z

Merge pull request #16 from apache/develop

update from eagle-develop

commit 7340451cbb0621bfc1eebae1deeed730349ee8a6
Author: Daniel 
Date:   2016-08-04T21:19:37Z

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

Eg: 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 for volume and status input.
In this way, the policy is human readable and can be used to match the 
ids in maprfsAuditLog.

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

5. Added license for 
"/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java"
 to pass rat 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 issue #300: EAGLE-283 Convert fid,uid in MapR's audit log to...

[DadanielZ]

Github user DadanielZ commented on the issue:

https://github.com/apache/incubator-eagle/pull/300
  
As I mentioned, user id conversion is a little bit tricky, it will be great 
if someone can give me a hint on user id conversion issue. 

Thanks and regards,
Da


---
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-283) Convert fid,uid in MapR's audit log to FIle/folder name, user name

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

Github user DadanielZ commented on the issue:

https://github.com/apache/incubator-eagle/pull/300
  
As I mentioned, user id conversion is a little bit tricky, it will be great 
if someone can give me a hint on user id conversion issue. 

Thanks and regards,
Da


> 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 issue #300: EAGLE-283 Convert fid,uid in MapR's audit log to...

[DadanielZ]

Github user DadanielZ commented on the issue:

https://github.com/apache/incubator-eagle/pull/300
  
By the way, "id converter" will make http request to mapr host.
As mapr use https connection,  " javax.net.ssl.SSLHandshakeException Error" 
will occur if user didn't add the  certificate to JVM's trust store.

Will update this on related doc later.

Regards,
Da


---
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-283) Convert fid,uid in MapR's audit log to FIle/folder name, user name

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

Github user DadanielZ commented on the issue:

https://github.com/apache/incubator-eagle/pull/300
  
By the way, "id converter" will make http request to mapr host.
As mapr use https connection,  " javax.net.ssl.SSLHandshakeException Error" 
will occur if user didn't add the  certificate to JVM's trust store.

Will update this on related doc later.

Regards,
Da


> 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 #301: Stream tumbling aggregator library

[yonzhang]

GitHub user yonzhang opened a pull request:

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

Stream tumbling aggregator library

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

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/301.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 #301


commit d94d27715cfe7bcafedc891539a3977d1a556bee
Author: yonzhang 
Date:   2016-08-03T23:41:42Z

convert hbase audit monitoring to app

commit ff7fa43e63a118ade30c026e1da8eafba6c20696
Author: yonzhang 
Date:   2016-08-03T23:42:44Z

test namenode fail 3 times

commit 5556ed0b959b76de56f18ba43038fc394d922aa6
Author: yonzhang 
Date:   2016-08-04T17:45:47Z

aggregation using siddhi lib

commit d75c0ebc7b94f3b4db96091df6da6725e2303a0c
Author: yonzhang 
Date:   2016-08-04T17:47:44Z

merge with latest upstream/develop

commit efece0d5346694caba042f35d8450707fd7dfc32
Author: yonzhang 
Date:   2016-08-04T19:42:46Z

upgrade siddhi to 3.1.1 for external time batch

commit 805f7dbf4587b89b2c76cc2eaca67741d6de748a
Author: yonzhang 
Date:   2016-08-04T23:55:31Z

enhance api for stream aggregator api




---
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-410) stream tumbling window aggregate library

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-410:
--

GitHub user yonzhang opened a pull request:

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

Stream tumbling aggregator library

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

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/301.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 #301


commit d94d27715cfe7bcafedc891539a3977d1a556bee
Author: yonzhang 
Date:   2016-08-03T23:41:42Z

convert hbase audit monitoring to app

commit ff7fa43e63a118ade30c026e1da8eafba6c20696
Author: yonzhang 
Date:   2016-08-03T23:42:44Z

test namenode fail 3 times

commit 5556ed0b959b76de56f18ba43038fc394d922aa6
Author: yonzhang 
Date:   2016-08-04T17:45:47Z

aggregation using siddhi lib

commit d75c0ebc7b94f3b4db96091df6da6725e2303a0c
Author: yonzhang 
Date:   2016-08-04T17:47:44Z

merge with latest upstream/develop

commit efece0d5346694caba042f35d8450707fd7dfc32
Author: yonzhang 
Date:   2016-08-04T19:42:46Z

upgrade siddhi to 3.1.1 for external time batch

commit 805f7dbf4587b89b2c76cc2eaca67741d6de748a
Author: yonzhang 
Date:   2016-08-04T23:55:31Z

enhance api for stream aggregator api




> stream tumbling window aggregate library
> 
>
> Key: EAGLE-410
> URL: https://issues.apache.org/jira/browse/EAGLE-410
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> Many use cases need aggregate data in streaming process, but Storm does not 
> provide high level aggregation API. The most frequently used example is to 
> aggregate data per minute while data is streamlined.
> After investigation, we found Siddhi CEP engine is good for this task.
> https://docs.wso2.com/display/CEP420/Inbuilt+Windows#InbuiltWindows-externalTimeBatchexternalTimeBatch
> This ticket will develop a preview of simple aggregation API for Eagle use 
> case.



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

[jira] [Created] (EAGLE-410) stream tumbling window aggregate library

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-410:
--

 Summary: stream tumbling window aggregate library
 Key: EAGLE-410
 URL: https://issues.apache.org/jira/browse/EAGLE-410
 Project: Eagle
  Issue Type: Task
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


Many use cases need aggregate data in streaming process, but Storm does not 
provide high level aggregation API. The most frequently used example is to 
aggregate data per minute while data is streamlined.

After investigation, we found Siddhi CEP engine is good for this task.

https://docs.wso2.com/display/CEP420/Inbuilt+Windows#InbuiltWindows-externalTimeBatchexternalTimeBatch

This ticket will develop a preview of simple aggregation API for Eagle use case.



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

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

[Apache Jenkins Server]

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

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

[Apache Jenkins Server]

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

[jira] [Created] (EAGLE-411) Refactor EmbededHbase for unit test cases depending on hbase

[Hao Chen (JIRA)]

Hao Chen created EAGLE-411:
--

 Summary: Refactor EmbededHbase for unit test cases depending on 
hbase
 Key: EAGLE-411
 URL: https://issues.apache.org/jira/browse/EAGLE-411
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.4.0, v0.3.0
Reporter: Hao Chen
Assignee: Hao Chen
 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



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

[jira] [Created] (EAGLE-412) WebService Query StartTime & EndTime Support LONG timestamp

[Hao Chen (JIRA)]

Hao Chen created EAGLE-412:
--

 Summary: WebService Query StartTime & EndTime Support LONG 
timestamp
 Key: EAGLE-412
 URL: https://issues.apache.org/jira/browse/EAGLE-412
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.4.0, v0.3.0






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

[jira] [Updated] (EAGLE-412) WebService Query StartTime & EndTime Support LONG timestamp

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-412:
---
Description: WebService Query StartTime & EndTime Support LONG timestamp

> WebService Query StartTime & EndTime Support LONG timestamp
> ---
>
> Key: EAGLE-412
> URL: https://issues.apache.org/jira/browse/EAGLE-412
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.3.0, v0.4.0
>
>
> WebService Query StartTime & EndTime Support LONG timestamp



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

[GitHub] incubator-eagle issue #301: Stream tumbling aggregator library

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/301
  
Following unit tests failed:

~~~
Tests in error:
  test07Pull76(org.apache.eagle.alert.siddhi.TestExternalBatchWindow)
  test02NoMsg(org.apache.eagle.alert.siddhi.TestExternalBatchWindow)
  test06EdgeCase(org.apache.eagle.alert.siddhi.TestExternalBatchWindow)
  test01DownSampling(org.apache.eagle.alert.siddhi.TestExternalBatchWindow
~~~

For exception:
~~~
org.wso2.siddhi.query.api.exception.ExecutionPlanValidationException: No 
extension exist for WindowExtension{namespace='eagle'} , when creating query 
query in execution plan "a75398be-60e8-4248-9eaf-37166841ea88"

at 
org.wso2.siddhi.core.util.parser.ExecutionPlanParser.parse(ExecutionPlanParser.java:185)
at 
org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime(SiddhiManager.java:59)
at 
org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime(SiddhiManager.java:73)
at 
org.apache.eagle.alert.siddhi.TestExternalBatchWindow.simpleQueryRuntime(TestExternalBatchWindow.java:91)
at 
org.apache.eagle.alert.siddhi.TestExternalBatchWindow.test02NoMsg(TestExternalBatchWindow.java:57)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
at 
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
at 
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException: 
No extension exist for WindowExtension{namespace='eagle'} , when creating query 
query
at 
org.wso2.siddhi.core.util.parser.QueryParser.parse(QueryParser.java:195)
at 
org.wso2.siddhi.core.util.parser.ExecutionPlanParser.parse(ExecutionPlanParser.java:169)
... 41 more
Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException: 
No extension exist for WindowExtension{namespace='eagle'} 
at 
org.wso2.siddhi.core.util.SiddhiClassLoader.loadExtensionImplementation(SiddhiClassLoader.java:67)
at 
org.wso2.siddhi.core.util.parser.SingleInputStreamParser.generateProcessor(SingleInputStreamParser.java:172)

hbase-data-activity-monitoring for help

[kangq...@chinamobile.com]

Dear professor:
I'm a developer on eagle, it's a great and useful system for me to 
monitor the data activity of various apache open-source tools. But I have a 
question when I try to input the hbase log into the eagle.
In page 
"http://eagle.apache.org/docs/hbase-data-activity-monitoring.html";,  step 2 of 
"How to add a Kafka log4j appender"  tells me to add “KAFKA_HBASE_AUDIT” log4j 
appender to Security audit appender, I find the content need to add contains 
the following information:

log4j.appender.KAFKA_HBASE_AUDIT=org.apache.eagle.log4j.kafka.KafkaLog4jAppender
  log4j.appender.KAFKA_HBASE_AUDIT.Topic=sandbox_hbase_security_log
   
log4j.appender.KAFKA_HBASE_AUDIT.BrokerList=sandbox.hortonworks.com:6667 (the 
kafka config??)
   
log4j.appender.KAFKA_HBASE_AUDIT.Layout=org.apache.log4j.PatternLayout
  log4j.appender.KAFKA_HBASE_AUDIT.Layout.ConversionPattern=%d{ISO8601} 
%p %c: %m%n
  log4j.appender.KAFKA_HBASE_AUDIT.ProducerType=async
   
log4j.appender.KAFKA_HDFS_AUDIT.KeyClass=org.apache.eagle.log4j.kafka.hadoop.GenericLogKeyer
 
  log4j.appender.KAFKA_HDFS_AUDIT.KeyPattern=user=(\\w+),\\s+ 

Were the "KAFKA_HDFS_AUDIT" is right in the appender?
I'm looking forward to your reply!



Best Regards!
--
Kang qian

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

[haoch]

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

https://github.com/apache/incubator-eagle/pull/300#discussion_r73635073
  
--- Diff: eagle-security/eagle-security-maprfs-web/pom.xml ---
@@ -64,6 +64,16 @@
   eagle-security-common
   ${project.version}
   
+  
+  com.mapr.hadoop
+  maprfs
+  ${maprfs.version}
+  
+  
+  org.apache.httpcomponents
+  httpclient
+  4.5.2
--- End diff --

Please avoid declaring any dependency with explicit version but use 
property defined in root pom instead. Better way is to define in 
dependency-management firstly and include without version.


---
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-283) Convert fid,uid in MapR's audit log to FIle/folder name, user name

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

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

https://github.com/apache/incubator-eagle/pull/300#discussion_r73635073
  
--- Diff: eagle-security/eagle-security-maprfs-web/pom.xml ---
@@ -64,6 +64,16 @@
   eagle-security-common
   ${project.version}
   
+  
+  com.mapr.hadoop
+  maprfs
+  ${maprfs.version}
+  
+  
+  org.apache.httpcomponents
+  httpclient
+  4.5.2
--- End diff --

Please avoid declaring any dependency with explicit version but use 
property defined in root pom instead. Better way is to define in 
dependency-management firstly and include without version.


> 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 #300: EAGLE-283 Convert fid,uid in MapR's audit...

[haoch]

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

https://github.com/apache/incubator-eagle/pull/300#discussion_r73635124
  
--- Diff: 
eagle-security/eagle-security-maprfs-auditlog/src/main/resources/maprFSAuditLog-init.sh
 ---
@@ -32,7 +32,7 @@ curl -u ${EAGLE_SERVICE_USER}:${EAGLE_SERVICE_PASSWD} -X 
POST -H 'Content-Type:a
"application":"maprFSAuditLog"
 },
 "enabled": true,
-"config": "classification.fs.defaultFS=maprfs:///"
+"config": 
"classification.fs.defaultFS=hdfs://mapr1.da.dg:7222\nclassification.mapr.webhttps=https://mapr1.da.dg:8443\nclassification.mapr.username=mapr\nclassification.mapr.password=mapr";
--- End diff --

Is `mapr1.da.dg` dataguise sensitive info? :-)


---
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-283) Convert fid,uid in MapR's audit log to FIle/folder name, user name

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

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

https://github.com/apache/incubator-eagle/pull/300#discussion_r73635124
  
--- Diff: 
eagle-security/eagle-security-maprfs-auditlog/src/main/resources/maprFSAuditLog-init.sh
 ---
@@ -32,7 +32,7 @@ curl -u ${EAGLE_SERVICE_USER}:${EAGLE_SERVICE_PASSWD} -X 
POST -H 'Content-Type:a
"application":"maprFSAuditLog"
 },
 "enabled": true,
-"config": "classification.fs.defaultFS=maprfs:///"
+"config": 
"classification.fs.defaultFS=hdfs://mapr1.da.dg:7222\nclassification.mapr.webhttps=https://mapr1.da.dg:8443\nclassification.mapr.username=mapr\nclassification.mapr.password=mapr";
--- End diff --

Is `mapr1.da.dg` dataguise sensitive info? :-)


> 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 #300: EAGLE-283 Convert fid,uid in MapR's audit...

[haoch]

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

https://github.com/apache/incubator-eagle/pull/300#discussion_r73635217
  
--- Diff: 
eagle-security/eagle-security-maprfs-web/src/main/test/java/MapRNameResolverTest.java
 ---
@@ -0,0 +1,35 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+
+import org.apache.eagle.service.security.hdfs.rest.MapRNameResolver;
+
+public class MapRNameResolverTest {
+
+public static void main(String[] args){
--- End diff --

Could you pls. refactor the `main` to a unit test case?


---
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-283) Convert fid,uid in MapR's audit log to FIle/folder name, user name

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

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

https://github.com/apache/incubator-eagle/pull/300#discussion_r73635217
  
--- Diff: 
eagle-security/eagle-security-maprfs-web/src/main/test/java/MapRNameResolverTest.java
 ---
@@ -0,0 +1,35 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+
+import org.apache.eagle.service.security.hdfs.rest.MapRNameResolver;
+
+public class MapRNameResolverTest {
+
+public static void main(String[] args){
--- End diff --

Could you pls. refactor the `main` to a unit test case?


> 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 #300: EAGLE-283 Convert fid,uid in MapR's audit...

[haoch]

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

https://github.com/apache/incubator-eagle/pull/300#discussion_r73635450
  
--- Diff: 
eagle-security/eagle-security-maprfs-web/src/main/test/java/org/apache/eagle/service/security/hdfs/rest/HttpRequestTest.java
 ---
@@ -0,0 +1,33 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.eagle.service.security.hdfs.rest;
+
+import 
org.apache.eagle.service.security.hdfs.resolver.MAPRFSVolumeResolver;
+import org.json.JSONObject;
+
+import java.util.List;
+
+public class HttpRequestTest {
+public static void main(String args[]) throws Exception {
+String restUrl = "https://mapr1.da.dg:8443/rest/volume/list";;
--- End diff --

- Could you pls. refactor the `main` to a unit test case ?
- Probably sensitive info?



---
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-283) Convert fid,uid in MapR's audit log to FIle/folder name, user name

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

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

https://github.com/apache/incubator-eagle/pull/300#discussion_r73635450
  
--- Diff: 
eagle-security/eagle-security-maprfs-web/src/main/test/java/org/apache/eagle/service/security/hdfs/rest/HttpRequestTest.java
 ---
@@ -0,0 +1,33 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.eagle.service.security.hdfs.rest;
+
+import 
org.apache.eagle.service.security.hdfs.resolver.MAPRFSVolumeResolver;
+import org.json.JSONObject;
+
+import java.util.List;
+
+public class HttpRequestTest {
+public static void main(String args[]) throws Exception {
+String restUrl = "https://mapr1.da.dg:8443/rest/volume/list";;
--- End diff --

- Could you pls. refactor the `main` to a unit test case ?
- Probably sensitive info?



> 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 #300: EAGLE-283 Convert fid,uid in MapR's audit...

[haoch]

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

https://github.com/apache/incubator-eagle/pull/300#discussion_r73635506
  
--- Diff: eagle-webservice/src/main/resources/application.conf ---
@@ -16,13 +16,24 @@
 {
eagle {
service {
-   storage-type = "hbase"
--- End diff --

Please keep hbase storage as default store type


---
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-283) Convert fid,uid in MapR's audit log to FIle/folder name, user name

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

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

https://github.com/apache/incubator-eagle/pull/300#discussion_r73635506
  
--- Diff: eagle-webservice/src/main/resources/application.conf ---
@@ -16,13 +16,24 @@
 {
eagle {
service {
-   storage-type = "hbase"
--- End diff --

Please keep hbase storage as default store type


> 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 issue #300: EAGLE-283 Convert fid,uid in MapR's audit log to...

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/300
  
@DadanielZ reviewed as above.


---
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-283) Convert fid,uid in MapR's audit log to FIle/folder name, user name

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/300
  
@DadanielZ reviewed as above.


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

Re: hbase-data-activity-monitoring for help

[Senthil Kumar]

Thanks Kang for trying out Apache Eagle.

Yes KAFKA_HBASE_AUDIT is correct log4J Appender which directly pushes your
log messages to Kafka Topic .. Also you should have Kafka and Scala library
in your hbase lib path to use KafkaLog4jAppender API .

-- Senthil

On Aug 5, 2016 8:04 AM, "kangq...@chinamobile.com" 
wrote:

> Dear professor:
> I'm a developer on eagle, it's a great and useful system for me to
> monitor the data activity of various apache open-source tools. But I have a
> question when I try to input the hbase log into the eagle.
> In page "http://eagle.apache.org/docs/hbase-data-activity-
> monitoring.html",  step 2 of "How to add a Kafka log4j appender"  tells
> me to add “KAFKA_HBASE_AUDIT” log4j appender to Security audit appender, I
> find the content need to add contains the following information:
> log4j.appender.KAFKA_HBASE_AUDIT=org.apache.eagle.log4j.
> kafka.KafkaLog4jAppender
>   log4j.appender.KAFKA_HBASE_AUDIT.Topic=sandbox_hbase_
> security_log
>log4j.appender.KAFKA_HBASE_AUDIT.BrokerList=sandbox.
> hortonworks.com:6667 (the kafka config??)
>log4j.appender.KAFKA_HBASE_AUDIT.Layout=org.apache.log4j.
> PatternLayout
>   
> log4j.appender.KAFKA_HBASE_AUDIT.Layout.ConversionPattern=%d{ISO8601}
> %p %c: %m%n
>   log4j.appender.KAFKA_HBASE_AUDIT.ProducerType=async
>log4j.appender.KAFKA_HDFS_AUDIT.KeyClass=org.apache.
> eagle.log4j.kafka.hadoop.GenericLogKeyer
>   log4j.appender.KAFKA_HDFS_AUDIT.KeyPattern=user=(\\w+),\\s+
>
> Were the "KAFKA_HDFS_AUDIT" is right in the appender?
> I'm looking forward to your reply!
>
>
>
> Best Regards!
> --
> Kang qian
>

[jira] [Created] (EAGLE-414) Spark Streaming based Alert Engine

[Hao Chen (JIRA)]

Hao Chen created EAGLE-414:
--

 Summary: Spark Streaming based Alert Engine
 Key: EAGLE-414
 URL: https://issues.apache.org/jira/browse/EAGLE-414
 Project: Eagle
  Issue Type: New Feature
Affects Versions: v0.6.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.4.0, v0.3.0


Currently alert engine is based on storm, we could consider to extend alert 
engine to support spark streaming as well.



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

[jira] [Created] (EAGLE-413) Fix Unit Test org.apache.eagle.alert.siddhi.TestExternalBatchWindow

[Hao Chen (JIRA)]

Hao Chen created EAGLE-413:
--

 Summary: Fix Unit Test 
org.apache.eagle.alert.siddhi.TestExternalBatchWindow
 Key: EAGLE-413
 URL: https://issues.apache.org/jira/browse/EAGLE-413
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.4.0, v0.3.0


org.wso2.siddhi.query.api.exception.ExecutionPlanValidationException: No 
extension exist for WindowExtension{namespace='eagle'} , when creating query 
pull76 in execution plan "1b43d978-cf66-465b-a6be-ac251025d85d"

at 
org.wso2.siddhi.core.util.parser.ExecutionPlanParser.parse(ExecutionPlanParser.java:185)
at 
org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime(SiddhiManager.java:59)
at 
org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime(SiddhiManager.java:73)
at 
org.apache.eagle.alert.siddhi.TestExternalBatchWindow.test07Pull76(TestExternalBatchWindow.java:170)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
at 
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
at 
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException: No 
extension exist for WindowExtension{namespace='eagle'} , when creating query 
pull76
at 
org.wso2.siddhi.core.util.parser.QueryParser.parse(QueryParser.java:195)
at 
org.wso2.siddhi.core.util.parser.ExecutionPlanParser.parse(ExecutionPlanParser.java:169)
... 40 more
Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException: No 
extension exist for WindowExtension{namespace='eagle'} 
at 
org.wso2.siddhi.core.util.SiddhiClassLoader.loadExtensionImplementation(SiddhiClassLoader.java:67)
at 
org.wso2.siddhi.core.util.parser.SingleInputStreamParser.generateProcessor(SingleInputStreamParser.java:172)
at 
org.wso2.siddhi.core.util.parser.SingleInputStreamParser.parseInputStream(SingleInputStreamParser.java:104)
at 
org.wso2.siddhi.core.util.parser.InputStreamParser.parse(InputStreamPa

[jira] [Updated] (EAGLE-412) WebService Query StartTime & EndTime Support LONG timestamp

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-412:
---
Description: WebService Entity Query currently only support date string in 
format of -MM-DD HH-mm-SS, we should also StartTime & EndTime Support in 
LONG timestamp  (was: WebService Query StartTime & EndTime Support LONG 
timestamp)

> WebService Query StartTime & EndTime Support LONG timestamp
> ---
>
> Key: EAGLE-412
> URL: https://issues.apache.org/jira/browse/EAGLE-412
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.3.0, v0.4.0
>
>
> WebService Entity Query currently only support date string in format of 
> -MM-DD HH-mm-SS, we should also StartTime & EndTime Support in LONG 
> timestamp



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

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

[DadanielZ]

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

https://github.com/apache/incubator-eagle/pull/300#discussion_r73637287
  
--- Diff: eagle-webservice/src/main/resources/application.conf ---
@@ -16,13 +16,24 @@
 {
eagle {
service {
-   storage-type = "hbase"
--- End diff --

thank you for the review，will update it and create a new PR 


---
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 #300: EAGLE-283 Convert fid,uid in MapR's audit...

[DadanielZ]

Github user DadanielZ closed the pull request at:

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


---
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-412) WebService Query StartTime & EndTime Support LONG timestamp

[Hao Chen (JIRA)]

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

Hao Chen commented on EAGLE-412:


[~smith3816]

> WebService Query StartTime & EndTime Support LONG timestamp
> ---
>
> Key: EAGLE-412
> URL: https://issues.apache.org/jira/browse/EAGLE-412
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.3.0, v0.4.0
>
>
> WebService Entity Query currently only support date string in format of 
> -MM-DD HH-mm-SS, we should also StartTime & EndTime Support in LONG 
> timestamp



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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

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

https://github.com/apache/incubator-eagle/pull/300#discussion_r73637287
  
--- Diff: eagle-webservice/src/main/resources/application.conf ---
@@ -16,13 +16,24 @@
 {
eagle {
service {
-   storage-type = "hbase"
--- End diff --

thank you for the review，will update it and create a new PR 


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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

Github user DadanielZ closed the pull request at:

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


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

[jira] [Closed] (EAGLE-414) Spark Streaming based Alert Engine

[Hao Chen (JIRA)]

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

Hao Chen closed EAGLE-414.
--
Resolution: Duplicate

Duplicated with https://issues.apache.org/jira/browse/EAGLE-348

> Spark Streaming based Alert Engine
> --
>
> Key: EAGLE-414
> URL: https://issues.apache.org/jira/browse/EAGLE-414
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.6.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: extension
> Fix For: v0.4.0, v0.3.0
>
>
> Currently alert engine is based on storm, we could consider to extend alert 
> engine to support spark streaming as well.



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

[jira] [Updated] (EAGLE-348) Alert engtin base on spark streaming

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-348:
---
Fix Version/s: v0.4.0

> Alert engtin base on spark streaming
> 
>
> Key: EAGLE-348
> URL: https://issues.apache.org/jira/browse/EAGLE-348
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.6.0
>Reporter: JiJunTang
>Assignee: Hao Chen
>Priority: Minor
> Fix For: v0.4.0
>
>
> {noformat}
> New alert engine architecture:
> 1)Metaservice:   a) get meta(policies,topologies,streamdefinitions and so on) 
> 2)Coordinator:   a) pull policies and figure out if polices are changed by 
> Metaservice and notify config consumer of config changes by ConfigBusService 
> (powered by zk node cache)
>  b) placePolicy depend on policy usage on alertbolt
> 3)UnitTopology:  a) connect CorrelationSpout(read all topics data from kafka) 
> StreamRouterBolt(find which alertbolt to execute) AlertBolt(execute policy on 
> stream) AlertPublisherBolt (publish execute result to db,email and so on)
> 
> Let the alert engine to work on spark streaming,I think :
> 1) #1 and #2 can be worked on both storm and spark platform, can use 
> broadcast to distribute this service
> 2) we should rewirte 
> CorrelationSpout,StreamRouterBolt,AlertBolt,AlertPublisherBolt to Dstream and 
> connect them as DAG,then submit into spark platform.
> 3) spark can dynamic allocation executor without restart 
> 4) in the future spark streaming can support add or delete kafka topic 
> without restart
> {noformat}



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

[jira] [Updated] (EAGLE-348) Alert engtin base on spark streaming

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-348:
---
Affects Version/s: (was: v0.5.0)
   v0.6.0

> Alert engtin base on spark streaming
> 
>
> Key: EAGLE-348
> URL: https://issues.apache.org/jira/browse/EAGLE-348
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.6.0
>Reporter: JiJunTang
>Assignee: Hao Chen
>Priority: Minor
> Fix For: v0.4.0
>
>
> {noformat}
> New alert engine architecture:
> 1)Metaservice:   a) get meta(policies,topologies,streamdefinitions and so on) 
> 2)Coordinator:   a) pull policies and figure out if polices are changed by 
> Metaservice and notify config consumer of config changes by ConfigBusService 
> (powered by zk node cache)
>  b) placePolicy depend on policy usage on alertbolt
> 3)UnitTopology:  a) connect CorrelationSpout(read all topics data from kafka) 
> StreamRouterBolt(find which alertbolt to execute) AlertBolt(execute policy on 
> stream) AlertPublisherBolt (publish execute result to db,email and so on)
> 
> Let the alert engine to work on spark streaming,I think :
> 1) #1 and #2 can be worked on both storm and spark platform, can use 
> broadcast to distribute this service
> 2) we should rewirte 
> CorrelationSpout,StreamRouterBolt,AlertBolt,AlertPublisherBolt to Dstream and 
> connect them as DAG,then submit into spark platform.
> 3) spark can dynamic allocation executor without restart 
> 4) in the future spark streaming can support add or delete kafka topic 
> without restart
> {noformat}



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

[jira] [Commented] (EAGLE-348) Alert engtin base on spark streaming

[Hao Chen (JIRA)]

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

Hao Chen commented on EAGLE-348:


[~Jijun] would you pls. update some design document about current problem/use 
case/solution/architecture/design at 
https://cwiki.apache.org/confluence/display/EAG/Alert+Engine+on+Spark+Streaming?

> Alert engtin base on spark streaming
> 
>
> Key: EAGLE-348
> URL: https://issues.apache.org/jira/browse/EAGLE-348
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.6.0
>Reporter: JiJunTang
>Assignee: Hao Chen
>Priority: Minor
> Fix For: v0.4.0
>
>
> {noformat}
> New alert engine architecture:
> 1)Metaservice:   a) get meta(policies,topologies,streamdefinitions and so on) 
> 2)Coordinator:   a) pull policies and figure out if polices are changed by 
> Metaservice and notify config consumer of config changes by ConfigBusService 
> (powered by zk node cache)
>  b) placePolicy depend on policy usage on alertbolt
> 3)UnitTopology:  a) connect CorrelationSpout(read all topics data from kafka) 
> StreamRouterBolt(find which alertbolt to execute) AlertBolt(execute policy on 
> stream) AlertPublisherBolt (publish execute result to db,email and so on)
> 
> Let the alert engine to work on spark streaming,I think :
> 1) #1 and #2 can be worked on both storm and spark platform, can use 
> broadcast to distribute this service
> 2) we should rewirte 
> CorrelationSpout,StreamRouterBolt,AlertBolt,AlertPublisherBolt to Dstream and 
> connect them as DAG,then submit into spark platform.
> 3) spark can dynamic allocation executor without restart 
> 4) in the future spark streaming can support add or delete kafka topic 
> without restart
> {noformat}



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

[jira] [Commented] (EAGLE-348) Alert engtin base on spark streaming

[JiJunTang (JIRA)]

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

JiJunTang commented on EAGLE-348:
-

ok

> Alert engtin base on spark streaming
> 
>
> Key: EAGLE-348
> URL: https://issues.apache.org/jira/browse/EAGLE-348
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.6.0
>Reporter: JiJunTang
>Assignee: Hao Chen
>Priority: Minor
> Fix For: v0.4.0
>
>
> {noformat}
> New alert engine architecture:
> 1)Metaservice:   a) get meta(policies,topologies,streamdefinitions and so on) 
> 2)Coordinator:   a) pull policies and figure out if polices are changed by 
> Metaservice and notify config consumer of config changes by ConfigBusService 
> (powered by zk node cache)
>  b) placePolicy depend on policy usage on alertbolt
> 3)UnitTopology:  a) connect CorrelationSpout(read all topics data from kafka) 
> StreamRouterBolt(find which alertbolt to execute) AlertBolt(execute policy on 
> stream) AlertPublisherBolt (publish execute result to db,email and so on)
> 
> Let the alert engine to work on spark streaming,I think :
> 1) #1 and #2 can be worked on both storm and spark platform, can use 
> broadcast to distribute this service
> 2) we should rewirte 
> CorrelationSpout,StreamRouterBolt,AlertBolt,AlertPublisherBolt to Dstream and 
> connect them as DAG,then submit into spark platform.
> 3) spark can dynamic allocation executor without restart 
> 4) in the future spark streaming can support add or delete kafka topic 
> without restart
> {noformat}



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

[GitHub] incubator-eagle issue #300: EAGLE-283 Convert fid,uid in MapR's audit log to...

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/300
  
@DadanielZ thanks, but I think you don't have to reopen another new pull 
request but could continue to modify and commit on you current branch as any 
additional changes will append directly to this PR. 

But as a better practice, you are recommended to create an independent 
feature branch (typically named EAGLE-${JIRA_ID}) from latest apache `develop` 
branch in your own forked repository for every new pull request instead of 
using `develop` branch always :-)


---
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-283) Convert fid,uid in MapR's audit log to FIle/folder name, user name

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/300
  
@DadanielZ thanks, but I think you don't have to reopen another new pull 
request but could continue to modify and commit on you current branch as any 
additional changes will append directly to this PR. 

But as a better practice, you are recommended to create an independent 
feature branch (typically named EAGLE-${JIRA_ID}) from latest apache `develop` 
branch in your own forked repository for every new pull request instead of 
using `develop` branch always :-)


> 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 #282: EAGLE-40: Compile errors in develop branc...

[dbosco]

Github user dbosco closed the pull request at:

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


---
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-40) Policy detail page support alert list display

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-40:
-

Github user dbosco closed the pull request at:

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


> Policy detail page support alert list display
> -
>
> Key: EAGLE-40
> URL: https://issues.apache.org/jira/browse/EAGLE-40
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
>Priority: Minor
> Fix For: v0.3.0
>
>
> As a user, want to view the alert list content in the policy page directly.



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

[jira] [Created] (EAGLE-415) Compilation failure in develop branch - Copyright missing

[Don Bosco Durai (JIRA)]

Don Bosco Durai created EAGLE-415:
-

 Summary: Compilation failure in develop branch - Copyright missing
 Key: EAGLE-415
 URL: https://issues.apache.org/jira/browse/EAGLE-415
 Project: Eagle
  Issue Type: Bug
Reporter: Don Bosco Durai
Assignee: Don Bosco Durai


Apache copyright is missing in file 
eagle-examples/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java




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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

GitHub user DadanielZ reopened a pull request:

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

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

Eg: after 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 for volume and status input.
In this way, the policy is human readable and can be used to match the 
ids in maprfsAuditLog for monitoring.

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

5. Added license for 
"/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java"
 to pass rat check.

For user id conversion I haven't come up with a perfect solution, this is 
because:
- As user id is more OS standard staff, user might need to make OS calls to 
get the user ids.
- If user use LDAP, it will make it easier as we can query that directly.

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

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

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

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


commit c6d10261e5ba32bf22c1fcee07c8c0ebf6f43a68
Author: Daniel 
Date:   2016-07-05T18:11:12Z

Merge pull request #12 from apache/develop

EAGLE-276 eagle support for mr & spark history job monitoring

commit 92d7a14a529b17608f018fb624039bb9115b9dff
Author: Daniel 
Date:   2016-07-21T05:18:22Z

Merge pull request #13 from apache/develop

update from Eagle develop

commit 2d97d281ec10eb24dca76f64557733d412ce6a19
Author: Daniel 
Date:   2016-07-28T17:56:52Z

Merge pull request #14 from apache/develop

update from eagle-develop

commit 1e2e6a98569d2000f3561c420067e2f926fa2a75
Author: Daniel 
Date:   2016-07-29T19:38:01Z

Merge pull request #15 from apache/develop

update from apache-eagle develop branch

commit 55b6e1d8279be9b72b3958c52fc36bbe72a2ceb0
Author: Daniel 
Date:   2016-08-04T05:10:29Z

Merge pull request #16 from apache/develop

update from eagle-develop

commit 7340451cbb0621bfc1eebae1deeed730349ee8a6
Author: Daniel 
Date:   2016-08-04T21:19:37Z

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

Eg: 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 for volume and status input.
In this way, the policy is human readable and can be used to match the 
ids in maprfsAuditLog.

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

5. Added license for 
"/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java"
 to pass rat check.




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

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

[DadanielZ]

GitHub user DadanielZ reopened a pull request:

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

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

Eg: after 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 for volume and status input.
In this way, the policy is human readable and can be used to match the 
ids in maprfsAuditLog for monitoring.

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

5. Added license for 
"/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java"
 to pass rat check.

For user id conversion I haven't come up with a perfect solution, this is 
because:
- As user id is more OS standard staff, user might need to make OS calls to 
get the user ids.
- If user use LDAP, it will make it easier as we can query that directly.

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

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

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

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


commit c6d10261e5ba32bf22c1fcee07c8c0ebf6f43a68
Author: Daniel 
Date:   2016-07-05T18:11:12Z

Merge pull request #12 from apache/develop

EAGLE-276 eagle support for mr & spark history job monitoring

commit 92d7a14a529b17608f018fb624039bb9115b9dff
Author: Daniel 
Date:   2016-07-21T05:18:22Z

Merge pull request #13 from apache/develop

update from Eagle develop

commit 2d97d281ec10eb24dca76f64557733d412ce6a19
Author: Daniel 
Date:   2016-07-28T17:56:52Z

Merge pull request #14 from apache/develop

update from eagle-develop

commit 1e2e6a98569d2000f3561c420067e2f926fa2a75
Author: Daniel 
Date:   2016-07-29T19:38:01Z

Merge pull request #15 from apache/develop

update from apache-eagle develop branch

commit 55b6e1d8279be9b72b3958c52fc36bbe72a2ceb0
Author: Daniel 
Date:   2016-08-04T05:10:29Z

Merge pull request #16 from apache/develop

update from eagle-develop

commit 7340451cbb0621bfc1eebae1deeed730349ee8a6
Author: Daniel 
Date:   2016-08-04T21:19:37Z

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

Eg: 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 for volume and status input.
In this way, the policy is human readable and can be used to match the 
ids in maprfsAuditLog.

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

5. Added license for 
"/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java"
 to pass rat 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.
---

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-283:
--

Github user DadanielZ commented on the issue:

https://github.com/apache/incubator-eagle/pull/300
  
@haoch  thanks for your advice! XD 
Working on a feature branch will be a good practice. 


> 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 issue #300: EAGLE-283 Convert fid,uid in MapR's audit log to...

[DadanielZ]

Github user DadanielZ commented on the issue:

https://github.com/apache/incubator-eagle/pull/300
  
@haoch  thanks for your advice! XD 
Working on a feature branch will be a good practice. 


---
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-411) Refactor EmbededHbase for unit test cases depending on hbase

[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:
---
Description: 
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/

  was:
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


> Refactor EmbededHbase for unit test cases depending on 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: Hao 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)

[GitHub] incubator-eagle pull request #302: EAGLE-415 Compilation failure in develop ...

[dbosco]

GitHub user dbosco opened a pull request:

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

EAGLE-415 Compilation failure in develop branch - Copyright missing



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

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

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

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


commit 4bcd77c2c7aae983b8b78dd522c993ee06814184
Author: Don Bosco Durai 
Date:   2016-08-05T04:59:29Z

EAGLE-415 Compilation failure in develop branch - Copyright missing




---
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-415) Compilation failure in develop branch - Copyright missing

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-415:
--

GitHub user dbosco opened a pull request:

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

EAGLE-415 Compilation failure in develop branch - Copyright missing



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

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

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

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


commit 4bcd77c2c7aae983b8b78dd522c993ee06814184
Author: Don Bosco Durai 
Date:   2016-08-05T04:59:29Z

EAGLE-415 Compilation failure in develop branch - Copyright missing




> Compilation failure in develop branch - Copyright missing
> -
>
> Key: EAGLE-415
> URL: https://issues.apache.org/jira/browse/EAGLE-415
> Project: Eagle
>  Issue Type: Bug
>Reporter: Don Bosco Durai
>Assignee: Don Bosco Durai
>
> Apache copyright is missing in file 
> eagle-examples/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java



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

[jira] [Commented] (EAGLE-411) Refactor EmbededHbase for unit test cases depending on hbase

[Hao Chen (JIRA)]

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

Hao Chen commented on EAGLE-411:


Please try to use mockito with mini-hbase referring to 
http://blog.cloudera.com/blog/2013/09/how-to-test-hbase-applications-using-popular-tools/.
 Unit test cases depending on hbase are critical blocking for improving eagle 
code coverage.

> Refactor EmbededHbase for unit test cases depending on 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: Hao Chen
>  Labels: unit-test
> Fix For: v0.5.0
>
>
> Current implementation is really not stable which cause unit test like 
> TestHBaseLogReader2 unable to pass in meanful time, we need a better version.
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-embed/eagle-embed-hbase/src/main/java/org/apache/eagle/service/hbase/EmbeddedHbase.java
> http://blog.cloudera.com/blog/2013/09/how-to-test-hbase-applications-using-popular-tools/



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

[jira] [Resolved] (EAGLE-415) Compilation failure in develop branch - Copyright missing

[Don Bosco Durai (JIRA)]

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

Don Bosco Durai resolved EAGLE-415.
---
Resolution: Fixed

Pull request created https://github.com/apache/incubator-eagle/pull/302

> Compilation failure in develop branch - Copyright missing
> -
>
> Key: EAGLE-415
> URL: https://issues.apache.org/jira/browse/EAGLE-415
> Project: Eagle
>  Issue Type: Bug
>Reporter: Don Bosco Durai
>Assignee: Don Bosco Durai
>
> Apache copyright is missing in file 
> eagle-examples/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java



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

[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:
---
Summary: Refactor hbase related unit test cases with mockito and mini-hbase 
 (was: Refactor EmbededHbase for unit test cases depending on hbase)

> 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: Hao 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] [Created] (EAGLE-416) Add check style support

[JiJunTang (JIRA)]

JiJunTang created EAGLE-416:
---

 Summary: Add check style support
 Key: EAGLE-416
 URL: https://issues.apache.org/jira/browse/EAGLE-416
 Project: Eagle
  Issue Type: Improvement
Reporter: JiJunTang
Assignee: JiJunTang
Priority: Trivial


Add check style when build the project. Just print warning in console.



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

[jira] [Deleted] (EAGLE-414) Spark Streaming based Alert Engine

[Hao Chen (JIRA)]

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

Hao Chen deleted EAGLE-414:
---


> Spark Streaming based Alert Engine
> --
>
> Key: EAGLE-414
> URL: https://issues.apache.org/jira/browse/EAGLE-414
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: extension
>
> Currently alert engine is based on storm, we could consider to extend alert 
> engine to support spark streaming as well.



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

[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: JiJun Tang  (was: Hao Chen)

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

[Hao Chen (JIRA)]

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

Hao Chen commented on EAGLE-411:


[~r7raul] , please assign this task to anybody interested in contribution about 
unit test development.

> 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: JiJun Tang
>  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)

[GitHub] incubator-eagle issue #302: EAGLE-415 Compilation failure in develop branch ...

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/302
  
LGTM, thanks.


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

[jira] [Commented] (EAGLE-415) Compilation failure in develop branch - Copyright missing

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-415:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/302
  
LGTM, thanks.


> Compilation failure in develop branch - Copyright missing
> -
>
> Key: EAGLE-415
> URL: https://issues.apache.org/jira/browse/EAGLE-415
> Project: Eagle
>  Issue Type: Bug
>Reporter: Don Bosco Durai
>Assignee: Don Bosco Durai
>
> Apache copyright is missing in file 
> eagle-examples/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java



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

Created branch "spark" for supporting alert engine on spark streaming

[Hao Chen]

During offline meetup, some engineering team located at Shanghai is very
interested in contributing   eagle alert engine by supporting spark
streaming instead of being bound with storm, and eagle community is also
believe the ability for eagle to support diversified streaming
infrastructure like spark streaming or flink should be a positive trend in
future. So we create an exploratory branch named "spark" for related
development works about "spark streaming based alert engine" like EAGLE-414.

- Hao

[GitHub] incubator-eagle issue #302: EAGLE-415 Compilation failure in develop branch ...

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/302
  
@dbosco Patch applied. Thanks for the contribution and would you pls. close 
the pull request?


---
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-415) Compilation failure in develop branch - Copyright missing

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-415:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/302
  
@dbosco Patch applied. Thanks for the contribution and would you pls. close 
the pull request?


> Compilation failure in develop branch - Copyright missing
> -
>
> Key: EAGLE-415
> URL: https://issues.apache.org/jira/browse/EAGLE-415
> Project: Eagle
>  Issue Type: Bug
>Reporter: Don Bosco Durai
>Assignee: Don Bosco Durai
>
> Apache copyright is missing in file 
> eagle-examples/eagle-app-example/src/main/java/org/apache/eagle/app/example/ExampleStormConfig.java



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

[GitHub] incubator-eagle pull request #303: [EAGLE-416] Add check style support

[r7raul1984]

GitHub user r7raul1984 opened a pull request:

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

[EAGLE-416] Add check style support

- Add checkstyle plugin config in pom file.
- Add eagle_checks and suppressions file.

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

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

$ git pull https://github.com/r7raul1984/incubator-eagle checkstyle-EAGLE416

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

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


commit edfa70cdffa9fa362f16bc6b5db575b2ed0d937c
Author: r7raul1984 
Date:   2016-08-05T05:18:28Z

[EAGLE-416] Add check style support
- Add checkstyle plugin config in pom file.
- Add eagle_checks and suppressions file.

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




---
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-416) Add check style support

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-416:
--

GitHub user r7raul1984 opened a pull request:

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

[EAGLE-416] Add check style support

- Add checkstyle plugin config in pom file.
- Add eagle_checks and suppressions file.

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

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

$ git pull https://github.com/r7raul1984/incubator-eagle checkstyle-EAGLE416

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

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


commit edfa70cdffa9fa362f16bc6b5db575b2ed0d937c
Author: r7raul1984 
Date:   2016-08-05T05:18:28Z

[EAGLE-416] Add check style support
- Add checkstyle plugin config in pom file.
- Add eagle_checks and suppressions file.

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




> Add check style support
> ---
>
> Key: EAGLE-416
> URL: https://issues.apache.org/jira/browse/EAGLE-416
> Project: Eagle
>  Issue Type: Improvement
>Reporter: JiJun Tang
>Assignee: JiJun Tang
>Priority: Trivial
>
> Add check style when build the project. Just print warning in console.



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

[GitHub] incubator-eagle issue #303: [EAGLE-416] Add check style support

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/303
  
It seems that the PR created as new directory 
[`build`](/r7raul1984/incubator-eagle/tree/checkstyle-EAGLE416/build) under 
project root, would you please just put the checkstyle files under 
[`eagle-dev`](/apache/incubator-eagle/tree/master/eagle-dev) directly?


---
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-416) Add check style support

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-416:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/303
  
It seems that the PR created as new directory 
[`build`](/r7raul1984/incubator-eagle/tree/checkstyle-EAGLE416/build) under 
project root, would you please just put the checkstyle files under 
[`eagle-dev`](/apache/incubator-eagle/tree/master/eagle-dev) directly?


> Add check style support
> ---
>
> Key: EAGLE-416
> URL: https://issues.apache.org/jira/browse/EAGLE-416
> Project: Eagle
>  Issue Type: Improvement
>Reporter: JiJun Tang
>Assignee: JiJun Tang
>Priority: Trivial
>
> Add check style when build the project. Just print warning in console.



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

[jira] [Commented] (EAGLE-416) Add check style support

[Hao Chen (JIRA)]

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

Hao Chen commented on EAGLE-416:


Pls. update *Fix version* and *Start Progress* when patch is available.

> Add check style support
> ---
>
> Key: EAGLE-416
> URL: https://issues.apache.org/jira/browse/EAGLE-416
> Project: Eagle
>  Issue Type: Improvement
>Reporter: JiJun Tang
>Assignee: JiJun Tang
>Priority: Trivial
>
> Add check style when build the project. Just print warning in console.



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

[jira] [Commented] (EAGLE-416) Add check style support

[JiJun Tang (JIRA)]

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

JiJun Tang commented on EAGLE-416:
--

ok

> Add check style support
> ---
>
> Key: EAGLE-416
> URL: https://issues.apache.org/jira/browse/EAGLE-416
> Project: Eagle
>  Issue Type: Improvement
>Reporter: JiJun Tang
>Assignee: JiJun Tang
>Priority: Trivial
>
> Add check style when build the project. Just print warning in console.



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

[jira] [Updated] (EAGLE-416) Add check style support

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-416:
---
Labels: engineering pull-request-available  (was: )

> Add check style support
> ---
>
> Key: EAGLE-416
> URL: https://issues.apache.org/jira/browse/EAGLE-416
> Project: Eagle
>  Issue Type: Improvement
>Reporter: JiJun Tang
>Assignee: JiJun Tang
>Priority: Trivial
>  Labels: engineering, pull-request-available
>
> Add check style when build the project. Just print warning in console.



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

[GitHub] incubator-eagle issue #301: Stream tumbling aggregator library

[yonzhang]

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/301
  
ok, fixed, and will create another PR


---
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 #301: Stream tumbling aggregator library

[yonzhang]

Github user yonzhang closed the pull request at:

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


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

Re: Created branch "spark" for supporting alert engine on spark streaming

[Daniel Zhou]

This is so exiting! Great to have spark support! 

Regards,
Da



> On Aug 4, 2016, at 10:45 PM, Hao Chen  wrote:
> 
> During offline meetup, some engineering team located at Shanghai is very
> interested in contributing   eagle alert engine by supporting spark
> streaming instead of being bound with storm, and eagle community is also
> believe the ability for eagle to support diversified streaming
> infrastructure like spark streaming or flink should be a positive trend in
> future. So we create an exploratory branch named "spark" for related
> development works about "spark streaming based alert engine" like EAGLE-414.
> 
> - Hao

[jira] [Commented] (EAGLE-410) stream tumbling window aggregate library

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-410:
--

Github user yonzhang closed the pull request at:

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


> stream tumbling window aggregate library
> 
>
> Key: EAGLE-410
> URL: https://issues.apache.org/jira/browse/EAGLE-410
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> Many use cases need aggregate data in streaming process, but Storm does not 
> provide high level aggregation API. The most frequently used example is to 
> aggregate data per minute while data is streamlined.
> After investigation, we found Siddhi CEP engine is good for this task.
> https://docs.wso2.com/display/CEP420/Inbuilt+Windows#InbuiltWindows-externalTimeBatchexternalTimeBatch
> This ticket will develop a preview of simple aggregation API for Eagle use 
> case.



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

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

[Apache Jenkins Server]

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

[GitHub] incubator-eagle pull request #304: Stream tumbling aggregator library

[yonzhang]

GitHub user yonzhang opened a pull request:

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

Stream tumbling aggregator library

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


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/304.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 #304


commit d94d27715cfe7bcafedc891539a3977d1a556bee
Author: yonzhang 
Date:   2016-08-03T23:41:42Z

convert hbase audit monitoring to app

commit ff7fa43e63a118ade30c026e1da8eafba6c20696
Author: yonzhang 
Date:   2016-08-03T23:42:44Z

test namenode fail 3 times

commit 5556ed0b959b76de56f18ba43038fc394d922aa6
Author: yonzhang 
Date:   2016-08-04T17:45:47Z

aggregation using siddhi lib

commit d75c0ebc7b94f3b4db96091df6da6725e2303a0c
Author: yonzhang 
Date:   2016-08-04T17:47:44Z

merge with latest upstream/develop

commit efece0d5346694caba042f35d8450707fd7dfc32
Author: yonzhang 
Date:   2016-08-04T19:42:46Z

upgrade siddhi to 3.1.1 for external time batch

commit 805f7dbf4587b89b2c76cc2eaca67741d6de748a
Author: yonzhang 
Date:   2016-08-04T23:55:31Z

enhance api for stream aggregator api

commit 88da4bc684b623bff37d44e5ca10d84504caf1d9
Author: yonzhang 
Date:   2016-08-05T05:07:12Z

fix unit test bug for externalTimeBatch

commit 3d33167e4487a68faccaa683aeb984e1044c9381
Author: yonzhang 
Date:   2016-08-05T06:22:52Z

merge with conflict




---
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-416) Add check style support

[JiJun Tang (JIRA)]

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

JiJun Tang updated EAGLE-416:
-
Fix Version/s: v0.5.0

> Add check style support
> ---
>
> Key: EAGLE-416
> URL: https://issues.apache.org/jira/browse/EAGLE-416
> Project: Eagle
>  Issue Type: Improvement
>Reporter: JiJun Tang
>Assignee: JiJun Tang
>Priority: Trivial
>  Labels: engineering, pull-request-available
> Fix For: v0.5.0
>
>
> Add check style when build the project. Just print warning in console.



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

[jira] [Commented] (EAGLE-410) stream tumbling window aggregate library

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-410:
--

GitHub user yonzhang opened a pull request:

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

Stream tumbling aggregator library

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


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/304.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 #304


commit d94d27715cfe7bcafedc891539a3977d1a556bee
Author: yonzhang 
Date:   2016-08-03T23:41:42Z

convert hbase audit monitoring to app

commit ff7fa43e63a118ade30c026e1da8eafba6c20696
Author: yonzhang 
Date:   2016-08-03T23:42:44Z

test namenode fail 3 times

commit 5556ed0b959b76de56f18ba43038fc394d922aa6
Author: yonzhang 
Date:   2016-08-04T17:45:47Z

aggregation using siddhi lib

commit d75c0ebc7b94f3b4db96091df6da6725e2303a0c
Author: yonzhang 
Date:   2016-08-04T17:47:44Z

merge with latest upstream/develop

commit efece0d5346694caba042f35d8450707fd7dfc32
Author: yonzhang 
Date:   2016-08-04T19:42:46Z

upgrade siddhi to 3.1.1 for external time batch

commit 805f7dbf4587b89b2c76cc2eaca67741d6de748a
Author: yonzhang 
Date:   2016-08-04T23:55:31Z

enhance api for stream aggregator api

commit 88da4bc684b623bff37d44e5ca10d84504caf1d9
Author: yonzhang 
Date:   2016-08-05T05:07:12Z

fix unit test bug for externalTimeBatch

commit 3d33167e4487a68faccaa683aeb984e1044c9381
Author: yonzhang 
Date:   2016-08-05T06:22:52Z

merge with conflict




> stream tumbling window aggregate library
> 
>
> Key: EAGLE-410
> URL: https://issues.apache.org/jira/browse/EAGLE-410
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> Many use cases need aggregate data in streaming process, but Storm does not 
> provide high level aggregation API. The most frequently used example is to 
> aggregate data per minute while data is streamlined.
> After investigation, we found Siddhi CEP engine is good for this task.
> https://docs.wso2.com/display/CEP420/Inbuilt+Windows#InbuiltWindows-externalTimeBatchexternalTimeBatch
> This ticket will develop a preview of simple aggregation API for Eagle use 
> case.



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

Re: Created branch "spark" for supporting alert engine on spark streaming

[Zhang, Edward (GDI Hadoop)]

Is this feature aligned with new alert engine in 0.5?

Thanks
Edward

On 8/4/16, 23:14, "Daniel Zhou"  wrote:

>This is so exiting! Great to have spark support!
>
>Regards,
>Da
>
>
>
>> On Aug 4, 2016, at 10:45 PM, Hao Chen  wrote:
>> 
>> During offline meetup, some engineering team located at Shanghai is very
>> interested in contributing   eagle alert engine by supporting spark
>> streaming instead of being bound with storm, and eagle community is also
>> believe the ability for eagle to support diversified streaming
>> infrastructure like spark streaming or flink should be a positive trend
>>in
>> future. So we create an exploratory branch named "spark" for related
>> development works about "spark streaming based alert engine" like
>>EAGLE-414.
>> 
>> - Hao

Re: Created branch "spark" for supporting alert engine on spark streaming

[Hao Chen]

Yes, the purpose is to extend the new correlation alert engine in v0.5 to
support spark streaming, though it's currently a research feature and  not
planed in the release of v0.5 yet.

- Hao

On Fri, Aug 5, 2016 at 2:23 PM, Zhang, Edward (GDI Hadoop) <
yonzh...@ebay.com> wrote:

> Is this feature aligned with new alert engine in 0.5?
>
> Thanks
> Edward
>
> On 8/4/16, 23:14, "Daniel Zhou"  wrote:
>
> >This is so exiting! Great to have spark support!
> >
> >Regards,
> >Da
> >
> >
> >
> >> On Aug 4, 2016, at 10:45 PM, Hao Chen  wrote:
> >>
> >> During offline meetup, some engineering team located at Shanghai is very
> >> interested in contributing   eagle alert engine by supporting spark
> >> streaming instead of being bound with storm, and eagle community is also
> >> believe the ability for eagle to support diversified streaming
> >> infrastructure like spark streaming or flink should be a positive trend
> >>in
> >> future. So we create an exploratory branch named "spark" for related
> >> development works about "spark streaming based alert engine" like
> >>EAGLE-414.
> >>
> >> - Hao
>
>

Re: Created branch "spark" for supporting alert engine on spark streaming

[Hao Chen]

The "spark" branch will keep syncing latest code from "develop" branch and
continuously commit new features about Alert Engine on Spark Streaming upon
it.

- Hao

On Fri, Aug 5, 2016 at 2:34 PM, Hao Chen  wrote:

> Yes, the purpose is to extend the new correlation alert engine in v0.5 to
> support spark streaming, though it's currently a research feature and  not
> planed in the release of v0.5 yet.
>
> - Hao
>
> On Fri, Aug 5, 2016 at 2:23 PM, Zhang, Edward (GDI Hadoop) <
> yonzh...@ebay.com> wrote:
>
>> Is this feature aligned with new alert engine in 0.5?
>>
>> Thanks
>> Edward
>>
>> On 8/4/16, 23:14, "Daniel Zhou"  wrote:
>>
>> >This is so exiting! Great to have spark support!
>> >
>> >Regards,
>> >Da
>> >
>> >
>> >
>> >> On Aug 4, 2016, at 10:45 PM, Hao Chen  wrote:
>> >>
>> >> During offline meetup, some engineering team located at Shanghai is
>> very
>> >> interested in contributing   eagle alert engine by supporting spark
>> >> streaming instead of being bound with storm, and eagle community is
>> also
>> >> believe the ability for eagle to support diversified streaming
>> >> infrastructure like spark streaming or flink should be a positive trend
>> >>in
>> >> future. So we create an exploratory branch named "spark" for related
>> >> development works about "spark streaming based alert engine" like
>> >>EAGLE-414.
>> >>
>> >> - Hao
>>
>>
>

[GitHub] incubator-eagle issue #301: Stream tumbling aggregator library

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/301
  
Thanks, in fact, you don't have to reopen another new pull request but 
could continue to modify and commit on the current branch as any new changes 
will append directly to this PR.


---
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-417) Fix unit test failure on develop branch

[Hao Chen (JIRA)]

Hao Chen created EAGLE-417:
--

 Summary: Fix unit test failure on develop branch
 Key: EAGLE-417
 URL: https://issues.apache.org/jira/browse/EAGLE-417
 Project: Eagle
  Issue Type: Bug
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)