[GitHub] incubator-eagle pull request: EAGLE-296 Test unit for JobConfParse...

[yonzhang]

Github user yonzhang commented on the pull request:

https://github.com/apache/incubator-eagle/pull/195#issuecomment-221773347
  
@r7raul1984 why this is re-opened please manually close this pull request, 
this has been merged in 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.
---

[jira] [Commented] (EAGLE-296) add unit test for eagle-storm-jobrunning-spout

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-296:
--

Github user qingwen220 commented on the pull request:

https://github.com/apache/incubator-eagle/pull/195#issuecomment-221773080
  
have conflicts. Maybe rebase is needed


> add unit test for eagle-storm-jobrunning-spout
> --
>
> Key: EAGLE-296
> URL: https://issues.apache.org/jira/browse/EAGLE-296
> Project: Eagle
>  Issue Type: Test
>Reporter: tangjunjie
>Priority: Minor
>
> Add unit test for  eagle-storm-jobrunning-spout



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

[GitHub] incubator-eagle pull request: EAGLE-296 Test unit for JobConfParse...

[qingwen220]

Github user qingwen220 commented on the pull request:

https://github.com/apache/incubator-eagle/pull/195#issuecomment-221773080
  
have conflicts. Maybe rebase is needed


---
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-310) already existing active topology status not displayed when a deleted topology+execution re-created with same name

[Michael Wu (JIRA)]

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

Michael Wu updated EAGLE-310:
-
Description: 
Preproduce:
1. create a topology and an execution bound to it, and then start the execution.
2. deleted the execution started in the last step without stopping it.
3. recreate the topology and execution, with same topology name.
4. as a result, on the monitoring page, the recreated execution displays "NEW" 
status that customers can hit the "start" button and get an error message 
"Topology with name `eagle-sandbox-hbaseSecurityLog-demo001` already exists on 
cluster", however, the execution status is refreshed to "STARTED" in 5 seconds 
after syncing with the cluster.

Investigated cause: as deleting topology and execution without stopping the 
execution, system doesn't actually delete the corresponding topology in storm, 
so when we recreate the pair (topology+execution), the same named topology 
cannot be recreated in storm.

Point of view: customers will be confused if they recreate the same named pair, 
with error message but get it running in 5 seconds, meanwhile, being able to 
hit "start" button of execution will make them confused also.

Action required: please consider, as a user recreate a same named execution, if 
it's possible to get topology status in storm before showing the list on 
monitoring page, and show the real status of the execution in the list after 
that, as well as changing the "start" button to "stop" button accordingly. 

There should be a notification issue of deleting a "started" execution, please 
refer: 

  was:
Preproduce:
1. create a topology and an execution bound to it.
2. deleted the 2 created in the last step.
3. recreate the topology and execution, with same topology name.
4. as a result, on the monitoring page, the recreated execution displays "NEW" 
status that customers can hit the "start" button and get an error message 
"Topology with name `eagle-sandbox-hbaseSecurityLog-demo001` already exists on 
cluster", however, the execution status is refreshed to "STARTED" in 5 seconds 
after syncing with the cluster.

Investigated cause: as deleting topology and execution, system doesn't actually 
delete the corresponding topology in storm, so when we recreate the pair 
(topology+execution), the same named topology cannot recreated in storm.

Point of view: customers will be confused if they recreate the same named pair, 
with error message but get it running in 5 seconds, meanwhile, being able to 
hit "start" button of execution will make them confused.

Action required: please consider, as a user recreate a same named execution, if 
it's possible to get topology status in storm before showing the list on 
monitoring page, and show the real status of the execution in the list after 
that, as well as changing the "start" button to "stop" button accordingly. 


> already existing active topology status not displayed when a deleted 
> topology+execution re-created with same name
> -
>
> Key: EAGLE-310
> URL: https://issues.apache.org/jira/browse/EAGLE-310
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Michael Wu
>Assignee: Zhao, Qingwen
> Fix For: v0.4.0
>
>
> Preproduce:
> 1. create a topology and an execution bound to it, and then start the 
> execution.
> 2. deleted the execution started in the last step without stopping it.
> 3. recreate the topology and execution, with same topology name.
> 4. as a result, on the monitoring page, the recreated execution displays 
> "NEW" status that customers can hit the "start" button and get an error 
> message "Topology with name `eagle-sandbox-hbaseSecurityLog-demo001` already 
> exists on cluster", however, the execution status is refreshed to "STARTED" 
> in 5 seconds after syncing with the cluster.
> Investigated cause: as deleting topology and execution without stopping the 
> execution, system doesn't actually delete the corresponding topology in 
> storm, so when we recreate the pair (topology+execution), the same named 
> topology cannot be recreated in storm.
> Point of view: customers will be confused if they recreate the same named 
> pair, with error message but get it running in 5 seconds, meanwhile, being 
> able to hit "start" button of execution will make them confused also.
> Action required: please consider, as a user recreate a same named execution, 
> if it's possible to get topology status in storm before showing the list on 
> monitoring page, and show the real status of the execution in the list after 
> that, as well as changing the "start" button to "stop" button accordingly. 
> There should be a notification issue of deleting a "started" execution, 
> please refer: 



--
This 

[jira] [Updated] (EAGLE-310) already existing active topology status not displayed when a deleted topology+execution re-created with same name

[Michael Wu (JIRA)]

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

Michael Wu updated EAGLE-310:
-
Description: 
Preproduce:
1. create a topology and an execution bound to it, and then start the execution.
2. deleted the execution started in the last step without stopping it.
3. recreate the topology and execution, with same topology name.
4. as a result, on the monitoring page, the recreated execution displays "NEW" 
status that customers can hit the "start" button and get an error message 
"Topology with name `eagle-sandbox-hbaseSecurityLog-demo001` already exists on 
cluster", however, the execution status is refreshed to "STARTED" in 5 seconds 
after syncing with the cluster.

Investigated cause: as deleting topology and execution without stopping the 
execution, system doesn't actually delete the corresponding topology in storm, 
so when we recreate the pair (topology+execution), the same named topology 
cannot be recreated in storm.

Point of view: customers will be confused if they recreate the same named pair, 
with error message but get it running in 5 seconds, meanwhile, being able to 
hit "start" button of execution will make them confused also.

Action required: please consider, as a user recreate a same named execution, if 
it's possible to get topology status in storm before showing the list on 
monitoring page, and show the real status of the execution in the list after 
that, as well as changing the "start" button to "stop" button accordingly. 

There should be a notification issue of deleting a "started" execution, please 
refer: https://issues.apache.org/jira/browse/EAGLE-312

  was:
Preproduce:
1. create a topology and an execution bound to it, and then start the execution.
2. deleted the execution started in the last step without stopping it.
3. recreate the topology and execution, with same topology name.
4. as a result, on the monitoring page, the recreated execution displays "NEW" 
status that customers can hit the "start" button and get an error message 
"Topology with name `eagle-sandbox-hbaseSecurityLog-demo001` already exists on 
cluster", however, the execution status is refreshed to "STARTED" in 5 seconds 
after syncing with the cluster.

Investigated cause: as deleting topology and execution without stopping the 
execution, system doesn't actually delete the corresponding topology in storm, 
so when we recreate the pair (topology+execution), the same named topology 
cannot be recreated in storm.

Point of view: customers will be confused if they recreate the same named pair, 
with error message but get it running in 5 seconds, meanwhile, being able to 
hit "start" button of execution will make them confused also.

Action required: please consider, as a user recreate a same named execution, if 
it's possible to get topology status in storm before showing the list on 
monitoring page, and show the real status of the execution in the list after 
that, as well as changing the "start" button to "stop" button accordingly. 

There should be a notification issue of deleting a "started" execution, please 
refer: 


> already existing active topology status not displayed when a deleted 
> topology+execution re-created with same name
> -
>
> Key: EAGLE-310
> URL: https://issues.apache.org/jira/browse/EAGLE-310
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Michael Wu
>Assignee: Zhao, Qingwen
> Fix For: v0.4.0
>
>
> Preproduce:
> 1. create a topology and an execution bound to it, and then start the 
> execution.
> 2. deleted the execution started in the last step without stopping it.
> 3. recreate the topology and execution, with same topology name.
> 4. as a result, on the monitoring page, the recreated execution displays 
> "NEW" status that customers can hit the "start" button and get an error 
> message "Topology with name `eagle-sandbox-hbaseSecurityLog-demo001` already 
> exists on cluster", however, the execution status is refreshed to "STARTED" 
> in 5 seconds after syncing with the cluster.
> Investigated cause: as deleting topology and execution without stopping the 
> execution, system doesn't actually delete the corresponding topology in 
> storm, so when we recreate the pair (topology+execution), the same named 
> topology cannot be recreated in storm.
> Point of view: customers will be confused if they recreate the same named 
> pair, with error message but get it running in 5 seconds, meanwhile, being 
> able to hit "start" button of execution will make them confused also.
> Action required: please consider, as a user recreate a same named execution, 
> if it's possible to get topology status in storm before showing the list on 
> monitoring page, and show 

[jira] [Commented] (EAGLE-296) add unit test for eagle-storm-jobrunning-spout

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-296:
--

GitHub user r7raul1984 reopened a pull request:

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

EAGLE-296 Test unit for JobConfParserImpl

- TestJobConfParserImpl and jobconf.html to test jobconf parse.

Jira: https://issues.apache.org/jira/browse/EAGLE-296

 

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

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

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

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


commit da224c287ed9903bd5a57145b7cb77e4be1f0d7f
Author: r7raul1984 
Date:   2016-05-23T04:36:28Z

Add TestJobConfParserImpl and jobconf.html to test jobconf parse.




> add unit test for eagle-storm-jobrunning-spout
> --
>
> Key: EAGLE-296
> URL: https://issues.apache.org/jira/browse/EAGLE-296
> Project: Eagle
>  Issue Type: Test
>Reporter: tangjunjie
>Priority: Minor
>
> Add unit test for  eagle-storm-jobrunning-spout



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

[GitHub] incubator-eagle pull request: EAGLE-296 Test unit for JobConfParse...

[r7raul1984]

GitHub user r7raul1984 reopened a pull request:

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

EAGLE-296 Test unit for JobConfParserImpl

- TestJobConfParserImpl and jobconf.html to test jobconf parse.

Jira: https://issues.apache.org/jira/browse/EAGLE-296

 

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

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

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

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


commit da224c287ed9903bd5a57145b7cb77e4be1f0d7f
Author: r7raul1984 
Date:   2016-05-23T04:36:28Z

Add TestJobConfParserImpl and jobconf.html to test jobconf parse.




---
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-312) delete a started topology-execution on topology-monitoring page doesn't notify users that the execution may remain in system

[Michael Wu (JIRA)]

Michael Wu created EAGLE-312:


 Summary: delete a started topology-execution on 
topology-monitoring page doesn't notify users that the execution may remain in 
system
 Key: EAGLE-312
 URL: https://issues.apache.org/jira/browse/EAGLE-312
 Project: Eagle
  Issue Type: Bug
Reporter: Michael Wu
Assignee: Zhao, Qingwen
Priority: Minor


Reproduce:
1. on topology-monitoring page, create a topology execution and start it.
2. delete the execution without stopping it.
3. as a result, in the pop-up confirm overlay, no notification for users to 
know that the topology still remains in storm.

Point of view: users should be notified that the deletion only removes the item 
created in the managing pane, not affecting the existence of the topology in 
storm.

Action required: please consider to add some notification for users to delete a 
topology-execution that is in "started" status.



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

[jira] [Updated] (EAGLE-311) operations of items listed on topology-management monitoring page require buffering loading approaches

[Michael Wu (JIRA)]

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

Michael Wu updated EAGLE-311:
-
Assignee: Jilin, Jiang  (was: Zhao, Qingwen)

> operations of items listed on topology-management monitoring page require 
> buffering loading approaches
> --
>
> Key: EAGLE-311
> URL: https://issues.apache.org/jira/browse/EAGLE-311
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Michael Wu
>Assignee: Jilin, Jiang
> Fix For: v0.4.0
>
>
> Don't know if you are responsible of this, if you aren't please let me know 
> or directly forward it to appropriate people, thanks.
> Phenomenon: on topology-management monitoring page, operations of items 
> listed as topology-executions usually require several seconds to complete, 
> however, after users click start/stop/delete button of an item, the status 
> and operating buttons don't change to "pending" status and remain until the 
> operations complete, this may confuse users, giving them no way of knowing 
> what's going on with their operations.
> Point of view: to improve user experience, after a user hits any button, the 
> status icon should immediately change to "pending", and the button should 
> change to "disabled" status, unless the operation is problematic and should 
> be rejected immediately.
> Action required: please consider if we can change the related displayed 
> status to "pending" immediately after users start an operation, and when 
> results got, change the status again to what it should be.



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

[jira] [Created] (EAGLE-311) operations of items listed on topology-management monitoring page require buffering loading approaches

[Michael Wu (JIRA)]

Michael Wu created EAGLE-311:


 Summary: operations of items listed on topology-management 
monitoring page require buffering loading approaches
 Key: EAGLE-311
 URL: https://issues.apache.org/jira/browse/EAGLE-311
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.3.0
Reporter: Michael Wu
Assignee: Zhao, Qingwen
 Fix For: v0.4.0


Don't know if you are responsible of this, if you aren't please let me know or 
directly forward it to appropriate people, thanks.

Phenomenon: on topology-management monitoring page, operations of items listed 
as topology-executions usually require several seconds to complete, however, 
after users click start/stop/delete button of an item, the status and operating 
buttons don't change to "pending" status and remain until the operations 
complete, this may confuse users, giving them no way of knowing what's going on 
with their operations.

Point of view: to improve user experience, after a user hits any button, the 
status icon should immediately change to "pending", and the button should 
change to "disabled" status, unless the operation is problematic and should be 
rejected immediately.

Action required: please consider if we can change the related displayed status 
to "pending" immediately after users start an operation, and when results got, 
change the status again to what it should be.



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

Podling Report Reminder - May 2016

[johndament]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, June 1st).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.

This should be appended to the Incubator Wiki page at:

http://wiki.apache.org/incubator/May2016

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

[jira] [Commented] (EAGLE-280) Update logstash-kafka-conf.md

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-280:
--

GitHub user DadanielZ opened a pull request:

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

EAGLE-280 EAGLE-282 EAGLE-284 EAGLE-307: Mapr integration

EAGLE-280:Update logstash-kafka-conf.md

Updated logstash-kafka-conf.md and included a sample of logstash config 
file for logstash version 2.x
EAGLE-282:Auditlogparser for MapR's audit log

added class MAPRFSAuditLogObject
Renamed class MAPRAuditLogParser to MAPRFSAuditLogParser .
added MapRAuditLogKafkaDeserializer and MapRFSAuditLogProcessorMain.java
EAGLE-284:Connect to MapR's CLDB service

created profile in pom for mapr build
build passed for both hdp and mapr in local environment
EAGLE-307:Add applicaiton "maprFSAuditLog"

added module eagle-security-maprfs-web
added resolver for mapr: MAPRFSCommandResolver, MAPRStatusCodeResolver,
added a script to initialize mapFSAuditLog application

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

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

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

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


commit 7e8516c214f3a3b5b5e84f76344b26257e606feb
Author: Daniel 
Date:   2016-05-26T01:13:00Z

EAGLE-280:Update logstash-kafka-conf.md

Updated logstash-kafka-conf.md and included a sample of logstash config 
file for logstash version 2.x
EAGLE-282:Auditlogparser for MapR's audit log

added class MAPRFSAuditLogObject
Renamed class MAPRAuditLogParser to MAPRFSAuditLogParser .
added MapRAuditLogKafkaDeserializer and MapRFSAuditLogProcessorMain.java
EAGLE-284:Connect to MapR's CLDB service

created profile in pom for mapr build
build passed for both hdp and mapr in local environment
EAGLE-307:Add applicaiton "maprFSAuditLog"

added module eagle-security-maprfs-web
added resolver for mapr: MAPRFSCommandResolver, MAPRStatusCodeResolver,
added a script to initialize mapFSAuditLog application

commit e6497de230e843d126d0113a3d95c0a58da3f4c7
Author: Daniel 
Date:   2016-05-26T01:15:26Z

EAGLE-282:Auditlogparser for MapR's audit log
- added dependency on eagle-security-maprfs-web for eagle-webservice




> Update logstash-kafka-conf.md
> -
>
> Key: EAGLE-280
> URL: https://issues.apache.org/jira/browse/EAGLE-280
> Project: Eagle
>  Issue Type: Task
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> The 2.0 release of Logstash includes a new version of the Kafka output plugin 
> with significant configuration changes. One might need a new sample of 
> logstash config file for logstash2.X version.



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

[jira] [Commented] (EAGLE-280) Update logstash-kafka-conf.md

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-280:
--

Github user DadanielZ closed the pull request at:

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


> Update logstash-kafka-conf.md
> -
>
> Key: EAGLE-280
> URL: https://issues.apache.org/jira/browse/EAGLE-280
> Project: Eagle
>  Issue Type: Task
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> The 2.0 release of Logstash includes a new version of the Kafka output plugin 
> with significant configuration changes. One might need a new sample of 
> logstash config file for logstash2.X version.



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

[GitHub] incubator-eagle pull request: EAGLE-280 EAGLE-282 EAGLE-284 EAGLE-...

[DadanielZ]

Github user DadanielZ closed the pull request at:

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


---
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-280) Update logstash-kafka-conf.md

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-280:
--

GitHub user DadanielZ opened a pull request:

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

EAGLE-280 EAGLE-282 EAGLE-284 EAGLE-307

EAGLE-280:Update logstash-kafka-conf.md
- Updated logstash-kafka-conf.md and included a sample of logstash config 
file for logstash version 2.x

EAGLE-282:Auditlogparser for MapR's audit log
- added class MAPRFSAuditLogObject
- Renamed class MAPRAuditLogParser to  MAPRFSAuditLogParser .
- added MapRAuditLogKafkaDeserializer and MapRFSAuditLogProcessorMain.java

EAGLE-284:Connect to MapR's CLDB service
- created profile in pom for mapr build
- build passed for both hdp and mapr in local environment

EAGLE-307:Add applicaiton "maprFSAuditLog"
- added module eagle-security-maprfs-web
- added resolver for mapr: MAPRFSCommandResolver, MAPRStatusCodeResolver, 
- added a script to initialize mapFSAuditLog application

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

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

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

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


commit cfd79f715d9c0a7d7bfee19f0afa85ac4e011667
Author: Daniel 
Date:   2016-05-06T21:58:48Z

EAGLE-284:Connect to MapR's CLDB service
- Created a profile for MapR in pom.xml
- Added necessary dependencies in MapR's profile

commit d8f20ecbd817a4b0409a684e7f97bf444ec420f2
Author: Daniel 
Date:   2016-05-06T22:18:27Z

EAGLE-280:Update logstash-kafka-conf.md
- Updated logstash-kafka-conf.md and included a sample of logstash config 
file for logstash version 2.x

commit 79a5d96723464713874b930e973305b7173223b8
Author: Daniel 
Date:   2016-05-10T19:38:53Z

EAGLE-284:Connect to MapR's CLDB service
- updated dependencies for MapR in pom.xml (eagle-parent)
- build passed for both hdp and mapr in local environment

commit b5a3047badf963bef0f7a32092bd44da74592c94
Author: Daniel 
Date:   2016-05-11T23:16:55Z

EAGLE-282:Auditlogparser for MapR's audit log

- Created class MAPRAuditLogParser which can parse mapr's audit log into a 
HDFSAuditLogObject.
- Create module "eagle-security-maprfs-auditlog"
- Created class MAPRAuditLogKafkaDeserializer which use MAPRAuditLogParser 
to parse log messages.
- Unit test passed

commit 9b8666b2b8f70d9dfa34d10cbe6d24c2b71e3d00
Author: Daniel 
Date:   2016-05-13T22:22:33Z

Merge pull request #1 from apache/dev

Update from eagle-dev

commit 74b6f2c9b7844498facffdb59f24d6b23a39ba14
Author: Daniel 
Date:   2016-05-24T20:23:18Z

EAGLE-282:Auditlogparser for MapR's audit log

- added class MAPRFSAuditLogObject
- Renamed class MAPRAuditLogParser to  MAPRFSAuditLogParser .
- added MapRAuditLogKafkaDeserializer and MapRFSAuditLogProcessorMain.java

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

-added MAPRIdResolver to convert between fid and names
-test passed

EAGLE-307:Add applicaiton "maprFSAuditLog"

- added module eagle-security-maprfs-web
- added resolver for mapr: MAPRFSCommandResolver, MAPRStatusCodeResolver, 
MAPRFSResourceResolver
- added a script to initialize mapFSAuditLog application

Tested in local machine, alerts can be triggered.

commit 2100a562dfe22a034eab01d09da0e4670cfd201c
Author: Daniel 
Date:   2016-05-24T21:08:08Z

EAGLE-307:Add applicaiton "maprFSAuditLog"

- Added dependency on eagle-security-maprfs-web for eagle-webservice

commit 12089e90a08befa6d3fad9722c1b50279851febb
Author: Daniel 
Date:   2016-05-24T22:51:01Z

-removed MapRIdResolver.java and related tests

commit 59641385c8ae05fd90185b597a7ff4a9e41157a2
Author: Daniel 
Date:   2016-05-24T23:14:23Z

Merge pull request #2 from apache/dev

update from eagle-dev

commit 19376a495beaae9343b0accd643fc440b115efe2
Author: Daniel 
Date:   2016-05-24T23:23:43Z

EAGLE-307:Add applicaiton "maprFSAuditLog"
- updated project version number to 0.4.0-incubating-SNAPSHOT




> Update logstash-kafka-conf.md
> -
>
> Key: EAGLE-280
> URL: https://issues.apache.org/jira/browse/EAGLE-280
> Project: Eagle
>  Issue Type: 

[GitHub] incubator-eagle pull request: EAGLE-280 EAGLE-282 EAGLE-284 EAGLE-...

[DadanielZ]

GitHub user DadanielZ opened a pull request:

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

EAGLE-280 EAGLE-282 EAGLE-284 EAGLE-307

EAGLE-280:Update logstash-kafka-conf.md
- Updated logstash-kafka-conf.md and included a sample of logstash config 
file for logstash version 2.x

EAGLE-282:Auditlogparser for MapR's audit log
- added class MAPRFSAuditLogObject
- Renamed class MAPRAuditLogParser to  MAPRFSAuditLogParser .
- added MapRAuditLogKafkaDeserializer and MapRFSAuditLogProcessorMain.java

EAGLE-284:Connect to MapR's CLDB service
- created profile in pom for mapr build
- build passed for both hdp and mapr in local environment

EAGLE-307:Add applicaiton "maprFSAuditLog"
- added module eagle-security-maprfs-web
- added resolver for mapr: MAPRFSCommandResolver, MAPRStatusCodeResolver, 
- added a script to initialize mapFSAuditLog application

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

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

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

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


commit cfd79f715d9c0a7d7bfee19f0afa85ac4e011667
Author: Daniel 
Date:   2016-05-06T21:58:48Z

EAGLE-284:Connect to MapR's CLDB service
- Created a profile for MapR in pom.xml
- Added necessary dependencies in MapR's profile

commit d8f20ecbd817a4b0409a684e7f97bf444ec420f2
Author: Daniel 
Date:   2016-05-06T22:18:27Z

EAGLE-280:Update logstash-kafka-conf.md
- Updated logstash-kafka-conf.md and included a sample of logstash config 
file for logstash version 2.x

commit 79a5d96723464713874b930e973305b7173223b8
Author: Daniel 
Date:   2016-05-10T19:38:53Z

EAGLE-284:Connect to MapR's CLDB service
- updated dependencies for MapR in pom.xml (eagle-parent)
- build passed for both hdp and mapr in local environment

commit b5a3047badf963bef0f7a32092bd44da74592c94
Author: Daniel 
Date:   2016-05-11T23:16:55Z

EAGLE-282:Auditlogparser for MapR's audit log

- Created class MAPRAuditLogParser which can parse mapr's audit log into a 
HDFSAuditLogObject.
- Create module "eagle-security-maprfs-auditlog"
- Created class MAPRAuditLogKafkaDeserializer which use MAPRAuditLogParser 
to parse log messages.
- Unit test passed

commit 9b8666b2b8f70d9dfa34d10cbe6d24c2b71e3d00
Author: Daniel 
Date:   2016-05-13T22:22:33Z

Merge pull request #1 from apache/dev

Update from eagle-dev

commit 74b6f2c9b7844498facffdb59f24d6b23a39ba14
Author: Daniel 
Date:   2016-05-24T20:23:18Z

EAGLE-282:Auditlogparser for MapR's audit log

- added class MAPRFSAuditLogObject
- Renamed class MAPRAuditLogParser to  MAPRFSAuditLogParser .
- added MapRAuditLogKafkaDeserializer and MapRFSAuditLogProcessorMain.java

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

-added MAPRIdResolver to convert between fid and names
-test passed

EAGLE-307:Add applicaiton "maprFSAuditLog"

- added module eagle-security-maprfs-web
- added resolver for mapr: MAPRFSCommandResolver, MAPRStatusCodeResolver, 
MAPRFSResourceResolver
- added a script to initialize mapFSAuditLog application

Tested in local machine, alerts can be triggered.

commit 2100a562dfe22a034eab01d09da0e4670cfd201c
Author: Daniel 
Date:   2016-05-24T21:08:08Z

EAGLE-307:Add applicaiton "maprFSAuditLog"

- Added dependency on eagle-security-maprfs-web for eagle-webservice

commit 12089e90a08befa6d3fad9722c1b50279851febb
Author: Daniel 
Date:   2016-05-24T22:51:01Z

-removed MapRIdResolver.java and related tests

commit 59641385c8ae05fd90185b597a7ff4a9e41157a2
Author: Daniel 
Date:   2016-05-24T23:14:23Z

Merge pull request #2 from apache/dev

update from eagle-dev

commit 19376a495beaae9343b0accd643fc440b115efe2
Author: Daniel 
Date:   2016-05-24T23:23:43Z

EAGLE-307:Add applicaiton "maprFSAuditLog"
- updated project version number to 0.4.0-incubating-SNAPSHOT




---
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-280) Update logstash-kafka-conf.md

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-280:
--

Github user DadanielZ closed the pull request at:

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


> Update logstash-kafka-conf.md
> -
>
> Key: EAGLE-280
> URL: https://issues.apache.org/jira/browse/EAGLE-280
> Project: Eagle
>  Issue Type: Task
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> The 2.0 release of Logstash includes a new version of the Kafka output plugin 
> with significant configuration changes. One might need a new sample of 
> logstash config file for logstash2.X version.



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

[GitHub] incubator-eagle pull request: EAGLE-280 EAGLE-284 Added a profile ...

[DadanielZ]

Github user DadanielZ closed the pull request at:

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


---
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-309) Add code formatter template

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-309:
--

GitHub user RalphSu opened a pull request:

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

EAGLE-309: Add code formatter template

Add eclipse formatter.

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

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

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

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


commit 3304114440312aaf9fbe504d19ecb8dd1bce2eff
Author: Ralph, Su 
Date:   2016-05-25T10:07:20Z

EAGLE-309: Add code formatter template




> Add code formatter template
> ---
>
> Key: EAGLE-309
> URL: https://issues.apache.org/jira/browse/EAGLE-309
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: v0.4.0
>
>




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

[GitHub] incubator-eagle pull request: EAGLE-309: Add code formatter templa...

[RalphSu]

GitHub user RalphSu opened a pull request:

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

EAGLE-309: Add code formatter template

Add eclipse formatter.

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

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

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

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


commit 3304114440312aaf9fbe504d19ecb8dd1bce2eff
Author: Ralph, Su 
Date:   2016-05-25T10:07:20Z

EAGLE-309: Add code formatter template




---
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-309) Add code formatter template

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-309:
---
Fix Version/s: (was: v0.5.0)
   v0.4.0

> Add code formatter template
> ---
>
> Key: EAGLE-309
> URL: https://issues.apache.org/jira/browse/EAGLE-309
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: v0.4.0
>
>




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

[jira] [Created] (EAGLE-310) already existing active topology status not displayed when a deleted topology+execution re-created with same name

[Michael Wu (JIRA)]

Michael Wu created EAGLE-310:


 Summary: already existing active topology status not displayed 
when a deleted topology+execution re-created with same name
 Key: EAGLE-310
 URL: https://issues.apache.org/jira/browse/EAGLE-310
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.3.0
Reporter: Michael Wu
Assignee: Zhao, Qingwen
 Fix For: v0.4.0


Preproduce:
1. create a topology and an execution bound to it.
2. deleted the 2 created in the last step.
3. recreate the topology and execution, with same topology name.
4. as a result, on the monitoring page, the recreated execution displays "NEW" 
status that customers can hit the "start" button and get an error message 
"Topology with name `eagle-sandbox-hbaseSecurityLog-demo001` already exists on 
cluster", however, the execution status is refreshed to "STARTED" in 5 seconds 
after syncing with the cluster.

Investigated cause: as deleting topology and execution, system doesn't actually 
delete the corresponding topology in storm, so when we recreate the pair 
(topology+execution), the same named topology cannot recreated in storm.

Point of view: customers will be confused if they recreate the same named pair, 
with error message but get it running in 5 seconds, meanwhile, being able to 
hit "start" button of execution will make them confused.

Action required: please consider, as a user recreate a same named execution, if 
it's possible to get topology status in storm before showing the list on 
monitoring page, and show the real status of the execution in the list after 
that, as well as changing the "start" button to "stop" button accordingly. 



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

[jira] [Created] (EAGLE-309) Add code formatter template

[Su Ralph (JIRA)]

Su Ralph created EAGLE-309:
--

 Summary: Add code formatter template
 Key: EAGLE-309
 URL: https://issues.apache.org/jira/browse/EAGLE-309
 Project: Eagle
  Issue Type: Task
Affects Versions: v0.5.0
Reporter: Su Ralph
Assignee: Su Ralph
 Fix For: v0.5.0






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

[jira] [Commented] (EAGLE-298) Oozie auditlog integration for Oozie security monitoring

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-298:
--

GitHub user r7raul1984 opened a pull request:

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

EAGLE-298 Oozie auditlog integration for Oozie security monitoring

- Add oozie auditlog parse code and related test code.
- Add job.html and controll.js code for new view type job.
- Add oozie auditlog entity ,oozie metatdata access config code and related 
test code.

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

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

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

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

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


commit d65032cb25ca5d8d667229f4cbf123b852699843
Author: r7raul1984 
Date:   2016-05-13T05:06:51Z

test unit for JobConfParserImpl

commit 24f95869db81aa818fe82c968a04422e83194233
Author: r7raul1984 
Date:   2016-05-16T02:22:31Z

EAGLE-299 Add thread sleep after executionPlanRuntime.getInputHandler to 
avoid test fail. This is a dirty workaround.

commit 1c5fbe1120761c068182eaaf928748553b1e23bc
Author: r7raul1984 
Date:   2016-05-16T09:51:55Z

EAGLE-298 Add oozie related entity and metadataAccess class.

commit 6f03a04cc97ae38bb83626de38c3ad7dab2c42b4
Author: r7raul1984 
Date:   2016-05-17T04:26:11Z

EAGLE-298 Add oozie sensitivity metadata logic and related test.

commit 197cc13bd95855ab044c88e19278dcde010e903a
Author: r7raul1984 
Date:   2016-05-17T08:18:16Z

EAGLE-298 Add oozie resource rest api and related test.

commit b2fbf021ba177cbc4049f9dbe188116f855486a8
Author: r7raul1984 
Date:   2016-05-19T01:14:51Z

EAGLE-298 Change oozie resource entity sensitivity from appname to jobId.

commit 9132feed096f465c3c477f8bf0e825ca46e18f69
Author: r7raul1984 
Date:   2016-05-19T07:58:51Z

EAGLE-298 Oozie audit log parser.

commit 12b235ee1ca98f9ac394cda84948723a6ad15fe8
Author: r7raul1984 
Date:   2016-05-19T08:00:41Z

EAGLE-298 Add pom for oozie auditlog moudle.

commit b7b7a17c4d0fda3845f68c09e0857517309685c7
Author: r7raul1984 
Date:   2016-05-19T09:59:39Z

EAGLE-298 Remove code which is nouse.

commit c028aaa915d866242094530fb77c1a703a6a89ab
Author: r7raul1984 
Date:   2016-05-20T04:38:22Z

EAGLE-298 Submit storm related code

commit ee85b8746138d8c4d447ac04997178b4b4565e11
Author: r7raul1984 
Date:   2016-05-20T04:42:44Z

EAGLE-298 Chang to oozie audit log.

commit 04e3dd298a427ab90971d06752145e66058fe3c1
Author: r7raul1984 
Date:   2016-05-20T09:36:16Z

EAGLE-298 Fix OozieResourceSensitivityAPIEntity to 
OozieResourceSensitivityService.

commit dfd3afa9a608c3926bb2d83525a7531a996a242b
Author: r7raul1984 
Date:   2016-05-23T01:30:43Z

EAGLE-298 Change executor name to oozieAuditLogAlertExecutor.

commit 63fe55e5118fd39ec0e9775d8d51a104ed207e83
Author: r7raul1984 
Date:   2016-05-23T02:48:54Z

EAGLE-298 Change xml-apis version to 1.4.01.

commit 38adcfebed88ae30ae90efa28f926325a5c8e1e2
Author: r7raul1984 
Date:   2016-05-23T05:05:40Z

Add view for job type and add related controller code.

commit a08201a31e9500e09d20906bbd0d4c0ad1b5ba67
Author: r7raul1984 
Date:   2016-05-23T06:34:30Z

Add view for job type and add related controller code.

commit 67683a0935c1b4d689e3eff03e4213fc9dc05a32
Author: r7raul1984 
Date:   2016-05-23T08:20:33Z

Remove some nouse code.

commit 6a7c6ff44309c905200e2b13da9d7da932c72500
Author: r7raul1984 
Date:   2016-05-24T04:46:24Z

Merge code from dev.

commit 117bbb506cb38e111797a861a86257c940b690be
Author: r7raul1984 
Date:   2016-05-24T04:50:31Z

Merge branch 'dev' of https://github.com/apache/incubator-eagle into oozie

Conflicts:

eagle-core/eagle-data-process/eagle-storm-jobrunning-spout/src/test/resources/jobconf.html

eagle-security/eagle-security-common/src/test/java/org/apache/eagle/security/crawler/audit/TestMetaDataAccessConfigRepo.java
eagle-topology-assembly/pom.xml
eagle-webservice/pom.xml

commit be733d46dc76ae6da10b0f0242843fce53a5a1aa
Author: r7raul1984 
Date:   2016-05-24T05:29:35Z

Change config frow web to classification.

commit 895488c6c434dabc214c4437f7de6a7d0fdfc7fb
Author: 

[GitHub] incubator-eagle pull request: EAGLE-296 Test unit for JobConfParse...

[r7raul1984]

Github user r7raul1984 closed the pull request at:

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


---
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-303) Refactor message format in the email template.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-303:
--

GitHub user pkuwm opened a pull request:

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

EAGLE-303. Split event fields into table in email for clearly reading.

Make alert message more clearly to read in email. Please see the attached 
email screenshot.
https://cloud.githubusercontent.com/assets/5187721/15531285/6ede59dc-220e-11e6-9891-17b2281874bb.png;>


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

$ git pull https://github.com/pkuwm/incubator-eagle EAGLE-303-DEV

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

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


commit 1960d27a236d5b3024da1d9d610d649e8ae1f7d0
Author: pkuwm 
Date:   2016-05-25T07:13:04Z

EAGLE-303. Split event fields into table in email for clearly reading.




> Refactor message format in the email template.
> --
>
> Key: EAGLE-303
> URL: https://issues.apache.org/jira/browse/EAGLE-303
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Huizhi Lu
>Assignee: Huizhi Lu
> Fix For: v0.4.0
>
>
> Make the message in the email look nicer and clearer.
> The Policy "testLevel" has been detected with the below information: 
> message="org.apache.hive.hcatalog.common.HCatException : 9001 : Exception 
> occurred while processing HCat request : NoSuchObjectException while fetching 
> table.. Cause : NoSuchObjectException(message:default.test3 table not found)" 
> time="2016-05-17 21:45:32.654+" sendTo="" level="ERROR" host="" 
> sendFrom="" actionSuggestion="" role="WebHCat Server" cluster=""



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

[GitHub] incubator-eagle pull request: EAGLE-303. Split event fields into t...

[pkuwm]

GitHub user pkuwm opened a pull request:

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

EAGLE-303. Split event fields into table in email for clearly reading.

Make alert message more clearly to read in email. Please see the attached 
email screenshot.
https://cloud.githubusercontent.com/assets/5187721/15531285/6ede59dc-220e-11e6-9891-17b2281874bb.png;>


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

$ git pull https://github.com/pkuwm/incubator-eagle EAGLE-303-DEV

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

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


commit 1960d27a236d5b3024da1d9d610d649e8ae1f7d0
Author: pkuwm 
Date:   2016-05-25T07:13:04Z

EAGLE-303. Split event fields into table in email for clearly reading.




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