[jira] [Resolved] (EAGLE-114) Enable RAT check and fix missing license headers
[ https://issues.apache.org/jira/browse/EAGLE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar resolved EAGLE-114. --- Resolution: Fixed Patch pulled in master. Thanks [~haoch] for the review and merge! > Enable RAT check and fix missing license headers > > > Key: EAGLE-114 > URL: https://issues.apache.org/jira/browse/EAGLE-114 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Prasad Mujumdar > > Enable maven rat check plugin to ensue that the source code has Apache > license header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-79) Provide analytic DSL support
[ https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091540#comment-15091540 ] ASF GitHub Bot commented on EAGLE-79: - Github user RalphSu commented on the pull request: https://github.com/apache/incubator-eagle/pull/52#issuecomment-170452146 Add aggregate purely on single user given QL support > Provide analytic DSL support > - > > Key: EAGLE-79 > URL: https://issues.apache.org/jira/browse/EAGLE-79 > Project: Eagle > Issue Type: New Feature >Affects Versions: 0.3.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: 0.3.0 > > > Eagle input comes with stream data (like security audit log), eagle provide > alerting computation based on CEP DSL. > Similar to this process, eagle should be able to provide same DSL support to > expose the real-time monitoring feature, and furthermore could be integrated > with some storage backend to provide dashboard/presentation to user. > This would require > 1. eagle programming API to support a new semantic of query(or aggregation), > using the similar alert DSL. > 2. a clear definition of time series storage interface (so that different > storage engine could be adopted), currently we might start from the eagle > built-in hbase implementation > 3. Metric API/Dashboard. > Currently, it require a lot of user customization and CEP engine capability > could not be reused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user RalphSu commented on the pull request: https://github.com/apache/incubator-eagle/pull/52#issuecomment-170452146 Add aggregate purely on single user given QL support --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-eagle pull request: EAGLE-84 create first version of aut...
Github user anyway1021 commented on the pull request: https://github.com/apache/incubator-eagle/pull/42#issuecomment-170446877 Updates made until commit "359546f": 1. Embed debug messages when the script is executed with argument â-l debugâ or â--log-level debugâ, other wise, it only output âinfoâ log. 2. Enhance the error handling and env-recovery mechanism. 3. Add non-patch mode to accomplish the goal. If the script is executed with a â-pâ or â--patchâ argument, it will use the patch mode, otherwise it uses non-patch mode by default. 4. Improve the compatibility for running it in windows and mac system. 5. Enrich help message for better instructions. --- 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-84) Create scripts for merging PRs automatically
[
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091520#comment-15091520
]
ASF GitHub Bot commented on EAGLE-84:
-
Github user anyway1021 commented on the pull request:
https://github.com/apache/incubator-eagle/pull/42#issuecomment-170446877
Updates made until commit "359546f":
1. Embed debug messages when the script is executed with argument “-l
debug” or “--log-level debug”, other wise, it only output “info” log.
2. Enhance the error handling and env-recovery mechanism.
3. Add non-patch mode to accomplish the goal. If the script is executed
with a “-p” or “--patch” argument, it will use the patch mode, otherwise it
uses non-patch mode by default.
4. Improve the compatibility for running it in windows and mac system.
5. Enrich help message for better instructions.
> Create scripts for merging PRs automatically
>
>
> Key: EAGLE-84
> URL: https://issues.apache.org/jira/browse/EAGLE-84
> Project: Eagle
> Issue Type: Task
>Reporter: Michael Wu
>Assignee: Hao Chen
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> While a pull request gets passed the testing steps, and is verified as
> good-to-merge, people are willing to merge it with scripts to go through
> necessary steps automatically, and can form the message of final aggregated
> commit in a unified format. To achieve this, we are attempted to create the
> script.
> As discussed, the format of message should be like below (ignore the lines
> consisted of asterisks):
> **
> EAGLE-${ticket_number} ${ticket_title}
> ${ticket_url}
> Author: ${commiter}
> Reviewer: ${reviewer}
> Closes #${pr_number} from ${do_person}
> **
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EAGLE-84) Create scripts for merging PRs automatically
[
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091519#comment-15091519
]
ASF GitHub Bot commented on EAGLE-84:
-
Github user anyway1021 commented on the pull request:
https://github.com/apache/incubator-eagle/pull/42#issuecomment-170446226
@haoch
The error of #51 occurs because the title of the PR is not in the expected
format, it starts with "EAGLE-114:" but not "EAGLE-114", there is an additional
":"
For sure, it's possible to support passing jira-id, do you mean in this way
we don't have to check the title, but instead form a correct title by the
script itself? I think this is a good idea, but do we need to check the
authenticity of the jira id? Please confirm.
BTW, did you mean to get author's email from the info in patch file or some
other place? Actually we can get a lot of info from a pr url, but emails may
vary in different places. E.g. my global git config takes company's account and
email as a user, but for apache projects, I have to config the local user with
github accounts, if anyone forget this, the email info in commits will be
different. So, which will be better reliable?
> Create scripts for merging PRs automatically
>
>
> Key: EAGLE-84
> URL: https://issues.apache.org/jira/browse/EAGLE-84
> Project: Eagle
> Issue Type: Task
>Reporter: Michael Wu
>Assignee: Hao Chen
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> While a pull request gets passed the testing steps, and is verified as
> good-to-merge, people are willing to merge it with scripts to go through
> necessary steps automatically, and can form the message of final aggregated
> commit in a unified format. To achieve this, we are attempted to create the
> script.
> As discussed, the format of message should be like below (ignore the lines
> consisted of asterisks):
> **
> EAGLE-${ticket_number} ${ticket_title}
> ${ticket_url}
> Author: ${commiter}
> Reviewer: ${reviewer}
> Closes #${pr_number} from ${do_person}
> **
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-84 create first version of aut...
Github user anyway1021 commented on the pull request: https://github.com/apache/incubator-eagle/pull/42#issuecomment-170446226 @haoch The error of #51 occurs because the title of the PR is not in the expected format, it starts with "EAGLE-114:" but not "EAGLE-114", there is an additional ":" For sure, it's possible to support passing jira-id, do you mean in this way we don't have to check the title, but instead form a correct title by the script itself? I think this is a good idea, but do we need to check the authenticity of the jira id? Please confirm. BTW, did you mean to get author's email from the info in patch file or some other place? Actually we can get a lot of info from a pr url, but emails may vary in different places. E.g. my global git config takes company's account and email as a user, but for apache projects, I have to config the local user with github accounts, if anyone forget this, the email info in commits will be different. So, which will be better reliable? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[EAGLE BUILD FAILED] incubator-eagle-main failed on build #7
The Apache Jenkins build system has built incubator-eagle-main (build #7) Status: Still Failing Check console output at https://builds.apache.org/job/incubator-eagle-main/7/ to view the results.
[jira] [Commented] (EAGLE-84) Create scripts for merging PRs automatically
[
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091454#comment-15091454
]
ASF GitHub Bot commented on EAGLE-84:
-
Github user haoch commented on the pull request:
https://github.com/apache/incubator-eagle/pull/42#issuecomment-170434434
Could we get the author email from commit patch instead of github account
api?
> Create scripts for merging PRs automatically
>
>
> Key: EAGLE-84
> URL: https://issues.apache.org/jira/browse/EAGLE-84
> Project: Eagle
> Issue Type: Task
>Reporter: Michael Wu
>Assignee: Hao Chen
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> While a pull request gets passed the testing steps, and is verified as
> good-to-merge, people are willing to merge it with scripts to go through
> necessary steps automatically, and can form the message of final aggregated
> commit in a unified format. To achieve this, we are attempted to create the
> script.
> As discussed, the format of message should be like below (ignore the lines
> consisted of asterisks):
> **
> EAGLE-${ticket_number} ${ticket_title}
> ${ticket_url}
> Author: ${commiter}
> Reviewer: ${reviewer}
> Closes #${pr_number} from ${do_person}
> **
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EAGLE-114) Enable RAT check and fix missing license headers
[ https://issues.apache.org/jira/browse/EAGLE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091453#comment-15091453 ] ASF GitHub Bot commented on EAGLE-114: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/51 > Enable RAT check and fix missing license headers > > > Key: EAGLE-114 > URL: https://issues.apache.org/jira/browse/EAGLE-114 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Prasad Mujumdar > > Enable maven rat check plugin to ensue that the source code has Apache > license header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-84 create first version of aut...
Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/42#issuecomment-170434434 Could we get the author email from commit patch instead of github account 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. ---
[GitHub] incubator-eagle pull request: EAGLE-114: Enable RAT check and fix ...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/51 --- 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: EAGLE-84 create first version of aut...
Github user haoch commented on the pull request:
https://github.com/apache/incubator-eagle/pull/42#issuecomment-170425595
Failed to merge "https://github.com/apache/incubator-eagle/pull/51"; due to
`ERR: the title of the pull request should start with "EAGLE-${jira_id}",
followed by a white-space and textual content, please revise accordingly, exit
with code -1 ...`, maybe it possible to support give jirap-id by parameters?
---
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-84) Create scripts for merging PRs automatically
[
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091388#comment-15091388
]
ASF GitHub Bot commented on EAGLE-84:
-
Github user haoch commented on the pull request:
https://github.com/apache/incubator-eagle/pull/42#issuecomment-170425595
Failed to merge "https://github.com/apache/incubator-eagle/pull/51"; due to
`ERR: the title of the pull request should start with "EAGLE-${jira_id}",
followed by a white-space and textual content, please revise accordingly, exit
with code -1 ...`, maybe it possible to support give jirap-id by parameters?
> Create scripts for merging PRs automatically
>
>
> Key: EAGLE-84
> URL: https://issues.apache.org/jira/browse/EAGLE-84
> Project: Eagle
> Issue Type: Task
>Reporter: Michael Wu
>Assignee: Hao Chen
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> While a pull request gets passed the testing steps, and is verified as
> good-to-merge, people are willing to merge it with scripts to go through
> necessary steps automatically, and can form the message of final aggregated
> commit in a unified format. To achieve this, we are attempted to create the
> script.
> As discussed, the format of message should be like below (ignore the lines
> consisted of asterisks):
> **
> EAGLE-${ticket_number} ${ticket_title}
> ${ticket_url}
> Author: ${commiter}
> Reviewer: ${reviewer}
> Closes #${pr_number} from ${do_person}
> **
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EAGLE-114) Enable RAT check and fix missing license headers
[ https://issues.apache.org/jira/browse/EAGLE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091387#comment-15091387 ] ASF GitHub Bot commented on EAGLE-114: -- Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/51#issuecomment-170425504 @pmujumdar LGTM, will merge, thanks for your contribution. > Enable RAT check and fix missing license headers > > > Key: EAGLE-114 > URL: https://issues.apache.org/jira/browse/EAGLE-114 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Prasad Mujumdar > > Enable maven rat check plugin to ensue that the source code has Apache > license header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-114: Enable RAT check and fix ...
Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/51#issuecomment-170425504 @pmujumdar LGTM, will merge, thanks for your contribution. --- 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-104) Fix the unit test TestHDFSSecuritylogParser
[
https://issues.apache.org/jira/browse/EAGLE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091386#comment-15091386
]
ASF GitHub Bot commented on EAGLE-104:
--
Github user haoch commented on the pull request:
https://github.com/apache/incubator-eagle/pull/43#issuecomment-170425247
@sunlibin please help review this pull request.
> Fix the unit test TestHDFSSecuritylogParser
> -
>
> Key: EAGLE-104
> URL: https://issues.apache.org/jira/browse/EAGLE-104
> Project: Eagle
> Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Prasad Mujumdar
> Attachments: EAGLE-104.1.patch
>
>
> The test fails with following error
> {noformat}
> java.lang.StringIndexOutOfBoundsException">
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at
> java.lang.String.substring(String.java:1911) at
> org.apache.eagle.security.util.LogParseUtil.parseUserFromUGI(LogParseUtil.java:39)
> at
> org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parseAttr(HDFSSecurityLogParser.java:78)
> at
> org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parse(HDFSSecurityLogParser.java:52)
> at
> org.apache.eagle.security.TestHDFSSecuritylogParser.test(TestHDFSSecuritylogParser.java:36)
> {noformat}
> Looks like the problem is that the UGI parsing method is not handling the
> simple authentication scenario where user name is not a kerberos principal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle pull request: https://issues.apache.org/jira/brows...
Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/43#issuecomment-170425247 @sunlibin please help review this 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. ---
[EAGLE BUILD FAILED] incubator-eagle-main failed on build #6
The Apache Jenkins build system has built incubator-eagle-main (build #6) Status: Still Failing Check console output at https://builds.apache.org/job/incubator-eagle-main/6/ to view the results.
[jira] [Commented] (EAGLE-112) Should support sum aggregation in front end for slide window function
[ https://issues.apache.org/jira/browse/EAGLE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091373#comment-15091373 ] ASF GitHub Bot commented on EAGLE-112: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/53 > Should support sum aggregation in front end for slide window function > - > > Key: EAGLE-112 > URL: https://issues.apache.org/jira/browse/EAGLE-112 > Project: Eagle > Issue Type: Improvement >Reporter: Libin, Sun >Assignee: Jilin, Jiang >Priority: Blocker > > In GC monitoring user case, > [EAGLE-97|https://issues.apache.org/jira/browse/EAGLE-97], we need to > calculate total GC paused time in a fixed interval, thus need create policy > with sum aggregation in front end -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-112) Should support sum aggregation in front end for slide window function
[ https://issues.apache.org/jira/browse/EAGLE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jilin, Jiang resolved EAGLE-112. Resolution: Fixed > Should support sum aggregation in front end for slide window function > - > > Key: EAGLE-112 > URL: https://issues.apache.org/jira/browse/EAGLE-112 > Project: Eagle > Issue Type: Improvement >Reporter: Libin, Sun >Assignee: Jilin, Jiang >Priority: Blocker > > In GC monitoring user case, > [EAGLE-97|https://issues.apache.org/jira/browse/EAGLE-97], we need to > calculate total GC paused time in a fixed interval, thus need create policy > with sum aggregation in front end -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-112 Should support sum aggrega...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/53 --- 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: EAGLE-114: Enable RAT check and fix ...
Github user pmujumdar commented on the pull request: https://github.com/apache/incubator-eagle/pull/51#issuecomment-170419053 @haoch It works in my setup. Takes a little time at the beginning thought. Please note that the check goal will run with default configuration and will not apply the explicit excludes listed in the pom. You'll need to run the specific execution id, eg mvn apache-rat:check@header-check The verify (or install etc) goals run with the specified execution id. --- 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-114) Enable RAT check and fix missing license headers
[ https://issues.apache.org/jira/browse/EAGLE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091347#comment-15091347 ] ASF GitHub Bot commented on EAGLE-114: -- Github user pmujumdar commented on the pull request: https://github.com/apache/incubator-eagle/pull/51#issuecomment-170419053 @haoch It works in my setup. Takes a little time at the beginning thought. Please note that the check goal will run with default configuration and will not apply the explicit excludes listed in the pom. You'll need to run the specific execution id, eg mvn apache-rat:check@header-check The verify (or install etc) goals run with the specified execution id. > Enable RAT check and fix missing license headers > > > Key: EAGLE-114 > URL: https://issues.apache.org/jira/browse/EAGLE-114 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Prasad Mujumdar > > Enable maven rat check plugin to ensue that the source code has Apache > license header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
