[jira] [Created] (EAGLE-83) Integrate Jenkins with GitHub for checking pull requests
Michael Wu created EAGLE-83: --- Summary: Integrate Jenkins with GitHub for checking pull requests Key: EAGLE-83 URL: https://issues.apache.org/jira/browse/EAGLE-83 Project: Eagle Issue Type: Task Reporter: Michael Wu Priority: Critical We expect that when a pull request comes up, a Jenkins job is triggered to verify the quality of new updates relevant to the PR, and automatically provide advices for whether it should be applied, with the verification result posted to github PR page for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-84) Create scripts for merging PRs automatically
Michael Wu created EAGLE-84:
---
Summary: 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
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] [Issue Comment Deleted] (EAGLE-84) Create scripts for merging PRs automatically
[
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Wu updated EAGLE-84:
Comment: was deleted
(was: The format is messy in description, try to tidy it here.
**
EAGLE-${ticket_number} ${ticket_title}
${ticket_url}
Author: ${commiter}
Reviewer: ${reviewer}
Closes #${pr_number} from ${do_person}
**)
> 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
> 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] [Updated] (EAGLE-83) Integrate Jenkins with GitHub for checking pull requests
[ https://issues.apache.org/jira/browse/EAGLE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-83: Priority: Major (was: Critical) > Integrate Jenkins with GitHub for checking pull requests > > > Key: EAGLE-83 > URL: https://issues.apache.org/jira/browse/EAGLE-83 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > Labels: test > Original Estimate: 168h > Remaining Estimate: 168h > > We expect that when a pull request comes up, a Jenkins job is triggered to > verify the quality of new updates relevant to the PR, and automatically > provide advices for whether it should be applied, with the verification > result posted to github PR page for reference. -- 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=15048842#comment-15048842
]
Michael Wu commented on EAGLE-84:
-
The format is messy in description, try to tidy it here.
**
EAGLE-${ticket_number} ${ticket_title}
${ticket_url}
Author: ${commiter}
Reviewer: ${reviewer}
Closes #${pr_number} from ${do_person}
**
> 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
> 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] [Assigned] (EAGLE-84) Create scripts for merging PRs automatically
[
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Wu reassigned EAGLE-84:
---
Assignee: Michael Wu
> 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: Michael Wu
> 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=15052986#comment-15052986
]
Michael Wu commented on EAGLE-84:
-
log steps with pseudocode for reference:
> turn to the repo_folder
> get latest master updates: git pull git://git.apache.org/incubator-eagle.git
> master
> download the patch to repo_folder/../patches/: wget
> https://patch-diff.githubusercontent.com/raw/apache/incubator-eagle/pull/${pr_number}.patch
> replace the placeholders in repo_folder/../template/commit_msg.template, with
> real values, and with the final content, create a file:
> pr${pr_number}_commit_msg
> git commit -at repo_folder/../template/pr${pr_number}_commit_msg
> git push git://git.apache.org/incubator-eagle.git master
the script should handle switches and exceptions
> 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: Michael Wu
> 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=15062232#comment-15062232
]
Michael Wu commented on EAGLE-84:
-
state:
1. pre-merge preparation, e.g. setup directories, download patch, etc.:
finished.
2. auto-checking approval of a pr: finished.
3. merge and push steps: on going, will finish by this friday.
Overall: will finish by this friday.
> 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=15065881#comment-15065881
]
Michael Wu commented on EAGLE-84:
-
All functionalities of the script have been completed, including. Have to
review it with the team to determine:
1. if there is any workflow issue omitted.
2. if the criteria inside the script makes sense.
3. in conjunction with github site, if the defined review flow makes sense.
4. where it should be place.
After all are solved and clear, it should be the time to check-in.
> 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-83) Integrate Jenkins with GitHub for checking pull requests
[ https://issues.apache.org/jira/browse/EAGLE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069690#comment-15069690 ] Michael Wu commented on EAGLE-83: - Progress: have linked apache/incubator-eagle.git with apache CI job, new pr can trigger builds. Problem: git clone failed, and haven't found out the root cause. See: https://builds.apache.org/job/incubator-eagle-pr-reviewer/1/console Will try to figure it out. > Integrate Jenkins with GitHub for checking pull requests > > > Key: EAGLE-83 > URL: https://issues.apache.org/jira/browse/EAGLE-83 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Hao Chen > Labels: test > Original Estimate: 168h > Remaining Estimate: 168h > > We expect that when a pull request comes up, a Jenkins job is triggered to > verify the quality of new updates relevant to the PR, and automatically > provide advices for whether it should be applied, with the verification > result posted to github PR page for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-83) Integrate Jenkins with GitHub for checking pull requests
[ https://issues.apache.org/jira/browse/EAGLE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070529#comment-15070529 ] Michael Wu commented on EAGLE-83: - Progress: the git clone issue has been resolved. Findings: ci building status marks pr as failed or successful, never considering at which step the ci fails. So we should create either plugin or script to exactly check the building result and call github api to change the status accordingly. > Integrate Jenkins with GitHub for checking pull requests > > > Key: EAGLE-83 > URL: https://issues.apache.org/jira/browse/EAGLE-83 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > Labels: test > Original Estimate: 168h > Remaining Estimate: 168h > > We expect that when a pull request comes up, a Jenkins job is triggered to > verify the quality of new updates relevant to the PR, and automatically > provide advices for whether it should be applied, with the verification > result posted to github PR page for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-101) cannot compile eagle successfully with jdk1.8
Michael Wu created EAGLE-101: Summary: cannot compile eagle successfully with jdk1.8 Key: EAGLE-101 URL: https://issues.apache.org/jira/browse/EAGLE-101 Project: Eagle Issue Type: Bug Environment: 1. mac 2. jenkins CI job Reporter: Michael Wu Priority: Trivial While using jdk1.8 to compile the project, there are constantly errors thrown as following: [INFO] --- maven-scala-plugin:2.15.0:compile (scala-compile-first) @ eagle-stream-process-base --- [INFO] Checking for multiple versions of scala [WARNING] Expected all dependencies to require Scala version: 2.10.0 [WARNING] org.apache.kafka:kafka_2.10:0.8.1.2.2.0.0-2041 requires scala version: 2.10.4 [WARNING] Multiple versions of scala libraries detected! [INFO] includes = [**/*.java,**/*.scala,] [INFO] excludes = [] [INFO] /Users/ziwu/test/incubator-eagle/eagle-core/eagle-data-process/eagle-stream-process-base/src/main/java:-1: info: compiling [INFO] /Users/ziwu/test/incubator-eagle/eagle-core/eagle-data-process/eagle-stream-process-base/src/main/scala:-1: info: compiling [INFO] Compiling 17 source files to /Users/ziwu/test/incubator-eagle/eagle-core/eagle-data-process/eagle-stream-process-base/target/classes at 1451275265312 [ERROR] error: error while loading CharSequence, class file '/Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home/jre/lib/rt.jar(java/lang/CharSequence.class)' is broken [INFO] (class java.lang.RuntimeException/bad constant pool tag 18 at byte 10) [ERROR] error: error while loading AnnotatedElement, class file '/Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home/jre/lib/rt.jar(java/lang/reflect/AnnotatedElement.class)' is broken [INFO] (class java.lang.RuntimeException/bad constant pool tag 18 at byte 76) [ERROR] error: error while loading ConcurrentMap, class file '/Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home/jre/lib/rt.jar(java/util/concurrent/ConcurrentMap.class)' is broken [INFO] (class java.lang.RuntimeException/bad constant pool tag 18 at byte 61) [ERROR] three errors found [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache Eagle Parent SUCCESS [ 0.494 s] [INFO] eagle core . SUCCESS [ 0.012 s] [INFO] eagle-query-parent . SUCCESS [ 0.099 s] [INFO] eagle-common ... SUCCESS [ 2.992 s] [INFO] eagle-data-process-parent .. SUCCESS [ 0.009 s] [INFO] eagle-stream-process-base .. FAILURE [ 2.843 s] [INFO] eagle-embed-parent . SKIPPED [INFO] eagle-embed-server . SKIPPED [INFO] eagle-embed-hbase .. SKIPPED [INFO] eagle-antlr SKIPPED [INFO] eagle-entity-base .. SKIPPED [INFO] eagle-client-base .. SKIPPED [INFO] eagle-alert-parent . SKIPPED [INFO] eagle-alert-base ... SKIPPED [INFO] eagle-metric ... SKIPPED [INFO] eagle-alert-process SKIPPED [INFO] eagle-stream-process-api ... SKIPPED [INFO] eagle-job-common ... SKIPPED [INFO] eagle-storm-jobrunning-spout ... SKIPPED [INFO] eagle-query-base ... SKIPPED [INFO] eagle-storage-base . SKIPPED [INFO] eagle-storage-hbase SKIPPED [INFO] eagle-service-base . SKIPPED [INFO] eagle-alert-service SKIPPED [INFO] eagle-storage-jdbc . SKIPPED [INFO] eagle-machinelearning-parent ... SKIPPED [INFO] eagle-machinelearning-base . SKIPPED [INFO] eagle-security-parent .. SKIPPED [INFO] eagle-security-common .. SKIPPED [INFO] eagle-security-hbase-web ... SKIPPED [INFO] eagle-security-hive-web SKIPPED [INFO] eagle-security-hdfs-web SKIPPED [INFO] eagle-security-userprofile-parent .. SKIPPED [INFO] eagle-security-userprofile-common .. SKIPPED [INFO] eagle-webservice ... SKIPPED [INFO] eagle-security-hdfs-auditlog ... SKIPPED [INFO] eagle-security-userprofile-detection ... SKIPPED [INFO] eagle-security-userprofile-training SKIPPED [INFO] eagle-security-hive
[jira] [Commented] (EAGLE-83) Integrate Jenkins with GitHub for checking pull requests
[ https://issues.apache.org/jira/browse/EAGLE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072440#comment-15072440 ] Michael Wu commented on EAGLE-83: - Progress: project get passed with compilation by changing JDK version from 1.8 to 1.7. Plan: create some mechanism to send back a comment to Jenkins as a review result. > Integrate Jenkins with GitHub for checking pull requests > > > Key: EAGLE-83 > URL: https://issues.apache.org/jira/browse/EAGLE-83 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > Labels: test > Original Estimate: 168h > Remaining Estimate: 168h > > We expect that when a pull request comes up, a Jenkins job is triggered to > verify the quality of new updates relevant to the PR, and automatically > provide advices for whether it should be applied, with the verification > result posted to github PR page for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-102) ask jenkins-admin's help to setup "Embeddable Build Status Plugin" and make the status visible in Readme.md of incubator-eagle.git
Michael Wu created EAGLE-102: Summary: ask jenkins-admin's help to setup "Embeddable Build Status Plugin" and make the status visible in Readme.md of incubator-eagle.git Key: EAGLE-102 URL: https://issues.apache.org/jira/browse/EAGLE-102 Project: Eagle Issue Type: Task Reporter: Michael Wu Assignee: Michael Wu reference url of the plugin: https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-103) add comments to readme to tell users: currently, eagle is tested under jdk1.7.x, may have compile error with jdk1.8.x
Michael Wu created EAGLE-103: Summary: add comments to readme to tell users: currently, eagle is tested under jdk1.7.x, may have compile error with jdk1.8.x Key: EAGLE-103 URL: https://issues.apache.org/jira/browse/EAGLE-103 Project: Eagle Issue Type: Improvement Reporter: Michael Wu Assignee: Hao Chen Priority: Minor Compilation error found while building with JDK1.8.x (refer to https://issues.apache.org/jira/browse/EAGLE-101). I think we should update the required version of jdk in readme file of the project. -- 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=15072834#comment-15072834
]
Michael Wu commented on EAGLE-84:
-
Progress: ave opened pr #42 for review, not including unit test checking logic,
but the script has already been a useable version.
Plan: the integration of Github & CI is under way, and I will update the script
once I'm aware enough of the logic of checking unit test results.
> 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-102) ask jenkins-admin's help to setup "Embeddable Build Status Plugin" and make the status visible in Readme.md of incubator-eagle.git
[ https://issues.apache.org/jira/browse/EAGLE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072835#comment-15072835 ] Michael Wu commented on EAGLE-102: -- Have opened ticket INFRA-11006 for jenkins admin team. > ask jenkins-admin's help to setup "Embeddable Build Status Plugin" and make > the status visible in Readme.md of incubator-eagle.git > -- > > Key: EAGLE-102 > URL: https://issues.apache.org/jira/browse/EAGLE-102 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > > reference url of the plugin: > https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-107) Build Status Icon has been enabled for our github repo, please apply it to readme.md
[ https://issues.apache.org/jira/browse/EAGLE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-107: - Description: As requested, the Build Status Icon is eligible for our project. We need to add it to readme.md of the project. Status links are at: https://builds.apache.org/job/incubator-eagle-pr-reviewer/badge/ was:As requested, the Build Status Icon is eligible for our project. We need to add it to readme.md of the project. > Build Status Icon has been enabled for our github repo, please apply it to > readme.md > > > Key: EAGLE-107 > URL: https://issues.apache.org/jira/browse/EAGLE-107 > Project: Eagle > Issue Type: Improvement >Reporter: Michael Wu >Assignee: Michael Wu > > As requested, the Build Status Icon is eligible for our project. We need to > add it to readme.md of the project. > Status links are at: > https://builds.apache.org/job/incubator-eagle-pr-reviewer/badge/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-107) Build Status Icon has been enabled for our github repo, please apply it to readme.md
Michael Wu created EAGLE-107: Summary: Build Status Icon has been enabled for our github repo, please apply it to readme.md Key: EAGLE-107 URL: https://issues.apache.org/jira/browse/EAGLE-107 Project: Eagle Issue Type: Improvement Reporter: Michael Wu Assignee: Michael Wu As requested, the Build Status Icon is eligible for our project. We need to add it to readme.md of the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-102) ask jenkins-admin's help to setup "Embeddable Build Status Plugin" and make the status visible in Readme.md of incubator-eagle.git
[ https://issues.apache.org/jira/browse/EAGLE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu resolved EAGLE-102. -- Resolution: Fixed > ask jenkins-admin's help to setup "Embeddable Build Status Plugin" and make > the status visible in Readme.md of incubator-eagle.git > -- > > Key: EAGLE-102 > URL: https://issues.apache.org/jira/browse/EAGLE-102 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > > reference url of the plugin: > https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-102) ask jenkins-admin's help to setup "Embeddable Build Status Plugin" and make the status visible in Readme.md of incubator-eagle.git
[ https://issues.apache.org/jira/browse/EAGLE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-102. the plugin has been installed. > ask jenkins-admin's help to setup "Embeddable Build Status Plugin" and make > the status visible in Readme.md of incubator-eagle.git > -- > > Key: EAGLE-102 > URL: https://issues.apache.org/jira/browse/EAGLE-102 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > > reference url of the plugin: > https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-110) unit test "TestHBaseWriteEntitiesPerformance.testWrite1MLogAPIEntities" need to be fixed
Michael Wu created EAGLE-110: Summary: unit test "TestHBaseWriteEntitiesPerformance.testWrite1MLogAPIEntities" need to be fixed Key: EAGLE-110 URL: https://issues.apache.org/jira/browse/EAGLE-110 Project: Eagle Issue Type: Bug Reporter: Michael Wu In CI builds, there is a unit test error blocking most of our pull requests. Its stacktrace is as pasted below, which is mainly thrown out from method: org.apache.eagle.log.entity.TestHBaseWriteEntitiesPerformance.testWrite1MLogAPIEntities(TestHBaseWriteEntitiesPerformance.java:125) Could anyone who own this unit test try to fix it? CI build url: https://builds.apache.org/job/incubator-eagle-pr-reviewer/22/ Stacktrace: org.apache.eagle.log.entity.TestHBaseWriteEntitiesPerformance.testWrite1MLogAPIEntities(TestHBaseWriteEntitiesPerformance.java:125) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:120) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:103) at org.apache.maven.surefire.Surefire.run(Surefire.java:169) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-111) create post build script for Jenkins CI to send details back to github
Michael Wu created EAGLE-111: Summary: create post build script for Jenkins CI to send details back to github Key: EAGLE-111 URL: https://issues.apache.org/jira/browse/EAGLE-111 Project: Eagle Issue Type: Task Reporter: Michael Wu Assignee: Michael Wu When a CI build finishes, it only mark the pr as success or failed, we need to write some script and place it on CI jobs as a post build operation to send detailed information back to github, which could be considered as a criteria for approval/rejection in the future. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-83) Integrate Jenkins with GitHub for checking pull requests
[ https://issues.apache.org/jira/browse/EAGLE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074646#comment-15074646 ] Michael Wu commented on EAGLE-83: - Issue: find incorrect configuration for Pull Request Builder plugin. Will try to fix it. Have sent notification email to dev mailing list. Will send notification once the issue is resolved. > Integrate Jenkins with GitHub for checking pull requests > > > Key: EAGLE-83 > URL: https://issues.apache.org/jira/browse/EAGLE-83 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > Labels: test > Original Estimate: 168h > Remaining Estimate: 168h > > We expect that when a pull request comes up, a Jenkins job is triggered to > verify the quality of new updates relevant to the PR, and automatically > provide advices for whether it should be applied, with the verification > result posted to github PR page for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-83) Integrate Jenkins with GitHub for checking pull requests
[ https://issues.apache.org/jira/browse/EAGLE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082319#comment-15082319 ] Michael Wu commented on EAGLE-83: - open a jira ticket for Infrastructure team: INFRA-11026 now is trying to write commands as a workaround. > Integrate Jenkins with GitHub for checking pull requests > > > Key: EAGLE-83 > URL: https://issues.apache.org/jira/browse/EAGLE-83 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > Labels: test > Original Estimate: 168h > Remaining Estimate: 168h > > We expect that when a pull request comes up, a Jenkins job is triggered to > verify the quality of new updates relevant to the PR, and automatically > provide advices for whether it should be applied, with the verification > result posted to github PR page for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-117) update Build Status Link and make it point to CI job building upon master
Michael Wu created EAGLE-117: Summary: update Build Status Link and make it point to CI job building upon master Key: EAGLE-117 URL: https://issues.apache.org/jira/browse/EAGLE-117 Project: Eagle Issue Type: Task Reporter: Michael Wu Assignee: Michael Wu shall point to https://builds.apache.org/job/incubator-eagle-main/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-117) update Build Status Link and make it point to CI job building upon master
[ https://issues.apache.org/jira/browse/EAGLE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-117. Resolution: Done > update Build Status Link and make it point to CI job building upon master > - > > Key: EAGLE-117 > URL: https://issues.apache.org/jira/browse/EAGLE-117 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > > shall point to https://builds.apache.org/job/incubator-eagle-main/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-84) Create scripts for merging PRs automatically
[
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Wu resolved EAGLE-84.
-
Resolution: Done
It's now being tested.
After it's merged to master, I'll close this ticket.
> 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] [Created] (EAGLE-131) make eagle main CI build pass
Michael Wu created EAGLE-131: Summary: make eagle main CI build pass Key: EAGLE-131 URL: https://issues.apache.org/jira/browse/EAGLE-131 Project: Eagle Issue Type: Task Reporter: Michael Wu Assignee: Michael Wu Priority: Critical task complete measurement should be: 1. the whole project is completely and successfully built 2. all unit tests run pass -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-131) make eagle main CI build pass
[ https://issues.apache.org/jira/browse/EAGLE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106165#comment-15106165 ] Michael Wu commented on EAGLE-131: -- Currently, previously failed unit tests are fixed, the project failed at the step to build eagle-webservice module. The apparent cause is the lack of npm, and ticket INFRA-11093 is opened to ask for help and install npm on the jenkins service. > make eagle main CI build pass > - > > Key: EAGLE-131 > URL: https://issues.apache.org/jira/browse/EAGLE-131 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu >Priority: Critical > > task complete measurement should be: > 1. the whole project is completely and successfully built > 2. all unit tests run pass -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-132) Apply static code check on eagle quality pipeline.
Michael Wu created EAGLE-132: Summary: Apply static code check on eagle quality pipeline. Key: EAGLE-132 URL: https://issues.apache.org/jira/browse/EAGLE-132 Project: Eagle Issue Type: Task Reporter: Michael Wu Assignee: Michael Wu Priority: Minor Need to add static code check to the pipeline, should take the CI job https://builds.apache.org/job/incubator-eagle-main as the basis. And this task depends on the successful build phases of compilation and unit-test-pass. Means the completion of ticket EAGLE-131. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-133) Analyze code coverage of unit test in quality pipeline.
Michael Wu created EAGLE-133: Summary: Analyze code coverage of unit test in quality pipeline. Key: EAGLE-133 URL: https://issues.apache.org/jira/browse/EAGLE-133 Project: Eagle Issue Type: Task Reporter: Michael Wu Assignee: Michael Wu Priority: Minor Need to analyze code coverage (CC) in the pipeline and showcase it to an appropriate place, should take the CI job https://builds.apache.org/job/incubator-eagle-main as the basis, and consider if embedded CC report and a separate sonar makes sense. And this task depends on the successful build phases of compilation and unit-test-pass. Means the completion of ticket EAGLE-131. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-134) publish javadoc of eagle
Michael Wu created EAGLE-134: Summary: publish javadoc of eagle Key: EAGLE-134 URL: https://issues.apache.org/jira/browse/EAGLE-134 Project: Eagle Issue Type: Bug Reporter: Michael Wu Assignee: Michael Wu Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-83) Integrate Jenkins with GitHub for checking pull requests
[ https://issues.apache.org/jira/browse/EAGLE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110162#comment-15110162 ] Michael Wu commented on EAGLE-83: - Scripts are still needed to make the status back onto github accurate enough. Will close this one and focus on other tickets as needed. > Integrate Jenkins with GitHub for checking pull requests > > > Key: EAGLE-83 > URL: https://issues.apache.org/jira/browse/EAGLE-83 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > Labels: test > Original Estimate: 168h > Remaining Estimate: 168h > > We expect that when a pull request comes up, a Jenkins job is triggered to > verify the quality of new updates relevant to the PR, and automatically > provide advices for whether it should be applied, with the verification > result posted to github PR page for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-83) Integrate Jenkins with GitHub for checking pull requests
[ https://issues.apache.org/jira/browse/EAGLE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-83. --- Resolution: Resolved See: https://builds.apache.org/job/incubator-eagle-pr-reviewer/ https://builds.apache.org/job/incubator-eagle-main/ > Integrate Jenkins with GitHub for checking pull requests > > > Key: EAGLE-83 > URL: https://issues.apache.org/jira/browse/EAGLE-83 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > Labels: test > Original Estimate: 168h > Remaining Estimate: 168h > > We expect that when a pull request comes up, a Jenkins job is triggered to > verify the quality of new updates relevant to the PR, and automatically > provide advices for whether it should be applied, with the verification > result posted to github PR page for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-131) make eagle main CI build pass
[ https://issues.apache.org/jira/browse/EAGLE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-131. Resolution: Resolved The job succeeded with all unit test cases passing at: https://builds.apache.org/job/incubator-eagle-main/21/ > make eagle main CI build pass > - > > Key: EAGLE-131 > URL: https://issues.apache.org/jira/browse/EAGLE-131 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu >Priority: Critical > > task complete measurement should be: > 1. the whole project is completely and successfully built > 2. all unit tests run pass -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-137) narrow unit test scope of pr reviewer ci job so that it only test the affections in the corresponding pr
Michael Wu created EAGLE-137: Summary: narrow unit test scope of pr reviewer ci job so that it only test the affections in the corresponding pr Key: EAGLE-137 URL: https://issues.apache.org/jira/browse/EAGLE-137 Project: Eagle Issue Type: Improvement Reporter: Michael Wu Assignee: Michael Wu Priority: Critical Currently, the job checking PR is running all the unit test cases as a whole, we have to narrow down the scope to focus on the things affected only in the PR. This may not be accomplishable based on what we now have, but we should try it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-134) publish javadoc of eagle
[ https://issues.apache.org/jira/browse/EAGLE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-134: - Issue Type: Improvement (was: Bug) > publish javadoc of eagle > > > Key: EAGLE-134 > URL: https://issues.apache.org/jira/browse/EAGLE-134 > Project: Eagle > Issue Type: Improvement >Reporter: Michael Wu >Assignee: Michael Wu >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-147) Add checkstyle and jacoco plugin to eagle's pom.
Michael Wu created EAGLE-147: Summary: Add checkstyle and jacoco plugin to eagle's pom. Key: EAGLE-147 URL: https://issues.apache.org/jira/browse/EAGLE-147 Project: Eagle Issue Type: Task Reporter: Michael Wu Assignee: Michael Wu -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-132) Apply static code check on eagle quality pipeline.
[ https://issues.apache.org/jira/browse/EAGLE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15129695#comment-15129695 ] Michael Wu commented on EAGLE-132: -- Depends on ticket EAGLE-147. > Apply static code check on eagle quality pipeline. > -- > > Key: EAGLE-132 > URL: https://issues.apache.org/jira/browse/EAGLE-132 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu >Priority: Minor > > Need to add static code check to the pipeline, should take the CI job > https://builds.apache.org/job/incubator-eagle-main as the basis. > And this task depends on the successful build phases of compilation and > unit-test-pass. Means the completion of ticket EAGLE-131. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-133) Analyze code coverage of unit test in quality pipeline.
[ https://issues.apache.org/jira/browse/EAGLE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15129697#comment-15129697 ] Michael Wu commented on EAGLE-133: -- Depends on ticket EAGLE-147. > Analyze code coverage of unit test in quality pipeline. > --- > > Key: EAGLE-133 > URL: https://issues.apache.org/jira/browse/EAGLE-133 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu >Priority: Minor > > Need to analyze code coverage (CC) in the pipeline and showcase it to an > appropriate place, should take the CI job > https://builds.apache.org/job/incubator-eagle-main as the basis, and consider > if embedded CC report and a separate sonar makes sense. > And this task depends on the successful build phases of compilation and > unit-test-pass. Means the completion of ticket EAGLE-131. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-159) XML parser configured in org.apache.eagle.jobrunning.crawler.XmlHelper is not protected from Xml eXternal Entities injection attack
Michael Wu created EAGLE-159: Summary: XML parser configured in org.apache.eagle.jobrunning.crawler.XmlHelper is not protected from Xml eXternal Entities injection attack Key: EAGLE-159 URL: https://issues.apache.org/jira/browse/EAGLE-159 Project: Eagle Issue Type: Bug Reporter: Michael Wu Assignee: Hao Chen Scanned and found by Fortify app: At org.apache.eagle.jobrunning.crawler.XmlHelper:41, XML parser configured at this position does not prevent nor limit external entities resolution, this can expose the parser to an XML External Entities attack. >> Explanation of the issue: 1. XML External Entities attacks benefit from an XML feature to build documents dynamically at the time of processing. An XML entity allows inclusion of data dynamically from a given resource. External entities allow an XML document to include data from an external URI. Unless configured to do otherwise, external entities force the XML parser to access the resource specified by the URI, e.g., a file on the local machine or on a remote system. This behavior exposes the application to XML External Entity (XXE) attacks, which can be used to perform denial of service of the local system, gain unauthorized access to files on the local machine, scan remote machines, and perform denial of service of remote systems. 2. The following XML document shows an example of an XXE attack. * ]>&xxe; * This example could crash the server (on a UNIX system), if the XML parser attempts to substitute the entity with the contents of the /dev/random file. >> Solving recommendation: 1. The XML unmarshaller should be configured securely so that it does not allow external entities as part of an incoming XML document. 2. To avoid XXE injection do not use unmarshal methods that process an XML source directly as java.io.File, java.io.Reader or java.io.InputStream. Parse the document with a securely configured parser and use an unmarshal method that takes the secure parser as the XML source as shown in the following example: ** // suppose we've got Unmarshaller instance referenced by unmarshaller DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance(); dbf.setExpandEntityReferences(false); DocumentBuilder db = dbf.newDocumentBuilder(); Document document = db.parse(); Model model = (Model) unmarshaller.unmarshal(document); ** -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-160) a password value is exposed which violates security rules
Michael Wu created EAGLE-160: Summary: a password value is exposed which violates security rules Key: EAGLE-160 URL: https://issues.apache.org/jira/browse/EAGLE-160 Project: Eagle Issue Type: Bug Reporter: Michael Wu Assignee: Hao Chen Priority: Minor At org.apache.eagle.service.security.pwdgen.PasswordEncoderGenerator:23 and :26, there are hardcoded password and println(hashedPassword) clause that violating the security rules. >> Solving recommendation: For the clauses are in a "main" method for testing, and that main method is the only method in the class, maybe we can delete the class or remove the main method from the class. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-160) a password value is exposed which violates security rules
[ https://issues.apache.org/jira/browse/EAGLE-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-160: - Assignee: Michael Wu (was: Hao Chen) > a password value is exposed which violates security rules > - > > Key: EAGLE-160 > URL: https://issues.apache.org/jira/browse/EAGLE-160 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Michael Wu >Priority: Minor > > At org.apache.eagle.service.security.pwdgen.PasswordEncoderGenerator:23 and > :26, there are hardcoded password and println(hashedPassword) clause that > violating the security rules. > >> Solving recommendation: > For the clauses are in a "main" method for testing, and that main method is > the only method in the class, maybe we can delete the class or remove the > main method from the class. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-161) add code coverage plugin to ealge's pom
Michael Wu created EAGLE-161: Summary: add code coverage plugin to ealge's pom Key: EAGLE-161 URL: https://issues.apache.org/jira/browse/EAGLE-161 Project: Eagle Issue Type: Task Reporter: Michael Wu Assignee: Michael Wu -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-147) Add pmd plugin and pmd rules location to eagle's pom.
[ https://issues.apache.org/jira/browse/EAGLE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-147: - Summary: Add pmd plugin and pmd rules location to eagle's pom. (was: Add checkstyle and jacoco plugin to eagle's pom.) > Add pmd plugin and pmd rules location to eagle's pom. > - > > Key: EAGLE-147 > URL: https://issues.apache.org/jira/browse/EAGLE-147 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-132) Apply static code check on eagle quality pipeline.
[ https://issues.apache.org/jira/browse/EAGLE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151734#comment-15151734 ] Michael Wu commented on EAGLE-132: -- Open PR #92. > Apply static code check on eagle quality pipeline. > -- > > Key: EAGLE-132 > URL: https://issues.apache.org/jira/browse/EAGLE-132 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu >Priority: Minor > > Need to add static code check to the pipeline, should take the CI job > https://builds.apache.org/job/incubator-eagle-main as the basis. > And this task depends on the successful build phases of compilation and > unit-test-pass. Means the completion of ticket EAGLE-131. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-162) incomplete class path fails launching Eagle DAM HDFS in sandbox
Michael Wu created EAGLE-162: Summary: incomplete class path fails launching Eagle DAM HDFS in sandbox Key: EAGLE-162 URL: https://issues.apache.org/jira/browse/EAGLE-162 Project: Eagle Issue Type: Task Reporter: Michael Wu Assignee: Hao Chen When I tried to start Eagle DAM HDFS in sandbox, it failed and threw an error with message: "Could not find or load main class eagle.security.auditlog.HdfsAuditLogProcessorMain". According to stacktrace of the error, I refer to incubator-eagle/eagle-external/eagle-ambari/lib/EAGLE/package/scripts/actions.py and found, there are several lines with the incomplete class path configured for main_class variable, they are: line 67, 92, and 117. Please help fix them accordingly. Paste error stacktrace here: 2016-02-18 05:45:36,221 - Error while executing command 'start': Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 214, in execute method(env) File "/var/lib/ambari-agent/cache/common-services/EAGLE/0.0.1/package/scripts/eagle_hdfs_topology.py", line 78, in start eagle_hdfs_topology_exec(action = 'start') File "/var/lib/ambari-agent/cache/common-services/EAGLE/0.0.1/package/scripts/actions.py", line 110, in eagle_hdfs_topology_exec Execute(cmd, user=params.eagle_user) File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 148, in __init__ self.env.run() File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 152, in run self.run_action(resource, action) File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 118, in run_action provider_action() File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 274, in action_run raise ex Fail: Execution of '/usr/hdp/current/eagle/bin/eagle-topology.sh --main eagle.security.auditlog.HdfsAuditLogProcessorMain --topology sandbox-hdfsAuditLog-topology --config /usr/hdp/current/eagle/conf/sandbox-hdfsAuditLog-application.conf start' returned 1. Starting eagle topology ... jarName=/usr/hdp/current/eagle/bin/../lib/topology/eagle-topology-0.3.0-assembly.jar mainClass=eagle.security.auditlog.HdfsAuditLogProcessorMain configFile=/usr/hdp/current/eagle/conf/sandbox-hdfsAuditLog-application.conf Running: java -client -Dstorm.options=nimbus.host=localhost -Dstorm.home=/usr/hdp/2.2.4.2-2/storm -Dstorm.log.dir=/var/log/storm -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib:/usr/hdp/current/storm-client/lib -Dstorm.conf.file= -cp /usr/hdp/2.2.4.2-2/storm/lib/jetty-http-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/hiccup-0.3.6.jar:/usr/hdp/2.2.4.2-2/storm/lib/commons-configuration-1.10.jar:/usr/hdp/2.2.4.2-2/storm/lib/minlog-1.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/json-simple-1.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/commons-io-2.4.jar:/usr/hdp/2.2.4.2-2/storm/lib/ring-servlet-1.3.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/java.classpath-0.2.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/commons-logging-1.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/clj-time-0.4.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/commons-fileupload-1.2.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/ring-core-1.1.5.jar:/usr/hdp/2.2.4.2-2/storm/lib/crypto-equality-1.0.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/core.incubator-0.1.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/jetty-servlets-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/ns-tracker-0.2.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/joda-time-2.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/jetty-security-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/ranger-storm-plugin-0.4.0.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/objenesis-1.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/jetty-io-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/jersey-bundle-1.17.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/zookeeper.jar:/usr/hdp/2.2.4.2-2/storm/lib/javax.servlet-2.5.0.v201103041518.jar:/usr/hdp/2.2.4.2-2/storm/lib/tools.cli-0.2.4.jar:/usr/hdp/2.2.4.2-2/storm/lib/servlet-api-2.5.jar:/usr/hdp/2.2.4.2-2/storm/lib/hadoop-common-2.6.0.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/ranger-plugins-cred-0.4.0.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/clout-1.0.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/jgrapht-core-0.9.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/logback-classic-1.0.6.jar:/usr/hdp/2.2.4.2-2/storm/lib/eclipselink-2.5.2-M1.jar:/usr/hdp/2.2.4.2-2/storm/lib/ranger-plugins-audit-0.4.0.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/oncrpc-1.0.7.jar:/usr/hdp/2.2.4.2-2/storm/lib/storm-core-0.9.3.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/jetty-util-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/kryo-2.21.jar:/usr/hdp/2.2.4.2-2/storm/lib/tools.logging-0.2.3.jar:/usr/hdp/2.2.4.2-2/storm/lib/crypto-random-1.2.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/logback-core-1.0.6.jar:/usr/hdp/2.2.4.2-2/storm/lib/gson-2.2.4.jar:/usr/hdp/2.2.4.2-2/storm/lib/jetty-server-7
[jira] [Updated] (EAGLE-162) incomplete class path fails launching Eagle DAM HDFS in sandbox
[ https://issues.apache.org/jira/browse/EAGLE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-162: - Issue Type: Bug (was: Task) > incomplete class path fails launching Eagle DAM HDFS in sandbox > --- > > Key: EAGLE-162 > URL: https://issues.apache.org/jira/browse/EAGLE-162 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Hao Chen > > When I tried to start Eagle DAM HDFS in sandbox, it failed and threw an error > with message: "Could not find or load main class > eagle.security.auditlog.HdfsAuditLogProcessorMain". > According to stacktrace of the error, I refer to > incubator-eagle/eagle-external/eagle-ambari/lib/EAGLE/package/scripts/actions.py > and found, there are several lines with the incomplete class path configured > for main_class variable, they are: line 67, 92, and 117. Please help fix them > accordingly. > Paste error stacktrace here: > 2016-02-18 05:45:36,221 - Error while executing command 'start': > Traceback (most recent call last): > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 214, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/EAGLE/0.0.1/package/scripts/eagle_hdfs_topology.py", > line 78, in start > eagle_hdfs_topology_exec(action = 'start') > File > "/var/lib/ambari-agent/cache/common-services/EAGLE/0.0.1/package/scripts/actions.py", > line 110, in eagle_hdfs_topology_exec > Execute(cmd, user=params.eagle_user) > File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", > line 148, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 152, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 118, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", > line 274, in action_run > raise ex > Fail: Execution of '/usr/hdp/current/eagle/bin/eagle-topology.sh --main > eagle.security.auditlog.HdfsAuditLogProcessorMain --topology > sandbox-hdfsAuditLog-topology --config > /usr/hdp/current/eagle/conf/sandbox-hdfsAuditLog-application.conf start' > returned 1. Starting eagle topology ... > jarName=/usr/hdp/current/eagle/bin/../lib/topology/eagle-topology-0.3.0-assembly.jar > mainClass=eagle.security.auditlog.HdfsAuditLogProcessorMain > configFile=/usr/hdp/current/eagle/conf/sandbox-hdfsAuditLog-application.conf > Running: java -client -Dstorm.options=nimbus.host=localhost > -Dstorm.home=/usr/hdp/2.2.4.2-2/storm -Dstorm.log.dir=/var/log/storm > -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib:/usr/hdp/current/storm-client/lib > -Dstorm.conf.file= -cp > /usr/hdp/2.2.4.2-2/storm/lib/jetty-http-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/hiccup-0.3.6.jar:/usr/hdp/2.2.4.2-2/storm/lib/commons-configuration-1.10.jar:/usr/hdp/2.2.4.2-2/storm/lib/minlog-1.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/json-simple-1.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/commons-io-2.4.jar:/usr/hdp/2.2.4.2-2/storm/lib/ring-servlet-1.3.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/java.classpath-0.2.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/commons-logging-1.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/clj-time-0.4.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/commons-fileupload-1.2.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/ring-core-1.1.5.jar:/usr/hdp/2.2.4.2-2/storm/lib/crypto-equality-1.0.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/core.incubator-0.1.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/jetty-servlets-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/ns-tracker-0.2.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/joda-time-2.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/jetty-security-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/ranger-storm-plugin-0.4.0.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/objenesis-1.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/jetty-io-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/jersey-bundle-1.17.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/zookeeper.jar:/usr/hdp/2.2.4.2-2/storm/lib/javax.servlet-2.5.0.v201103041518.jar:/usr/hdp/2.2.4.2-2/storm/lib/tools.cli-0.2.4.jar:/usr/hdp/2.2.4.2-2/storm/lib/servlet-api-2.5.jar:/usr/hdp/2.2.4.2-2/storm/lib/hadoop-common-2.6.0.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/ranger-plugins-cred-0.4.0.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/clout-1.0.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/jgrapht-core-0.9.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/logback-classic-1.0.6.jar:/usr/hdp/2.2.4.2-2/storm/lib/eclipselink-2.5.2-M1.jar:/usr/hdp/2.2.4.2-2/storm/lib/ranger-plugins-audit-0.4.0.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/oncrpc-1.0.7.jar:/usr/hdp/2.2.4.2-2/storm/lib/storm-core-0.9.3.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/jetty-util-
[jira] [Updated] (EAGLE-171) Policy listing table is messed up by too long policy name.
[ https://issues.apache.org/jira/browse/EAGLE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-171: - Attachment: Screen Shot 2016-02-25 at 11.18.11.png > Policy listing table is messed up by too long policy name. > -- > > Key: EAGLE-171 > URL: https://issues.apache.org/jira/browse/EAGLE-171 > Project: Eagle > Issue Type: Bug > Environment: sandbox >Reporter: Michael Wu >Assignee: Jilin, Jiang >Priority: Minor > Attachments: Screen Shot 2016-02-25 at 11.18.11.png > > > When any policy name is defined as a long string, in the table for listing > policies, the second column is widened to accommodate the whole content. As a > result, the table is messed up. > The project is built upon branch: > https://github.com/zombieJ/incubator-eagle/tree/module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-172) Scripting string is allowed to create policy rules.
Michael Wu created EAGLE-172: Summary: Scripting string is allowed to create policy rules. Key: EAGLE-172 URL: https://issues.apache.org/jira/browse/EAGLE-172 Project: Eagle Issue Type: Bug Environment: sandbox Reporter: Michael Wu Assignee: Jilin, Jiang While creating a policy, to define a rule, users can input a scripting fragment. From security perspective, such behavior should be forbidden. Such as . See the attached screenshot. The project is built upon branch: https://github.com/zombieJ/incubator-eagle/tree/module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-172) Scripting string is allowed to create policy rules.
[ https://issues.apache.org/jira/browse/EAGLE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-172: - Attachment: Screen Shot 2016-02-25 at 12.05.05.png > Scripting string is allowed to create policy rules. > --- > > Key: EAGLE-172 > URL: https://issues.apache.org/jira/browse/EAGLE-172 > Project: Eagle > Issue Type: Bug > Environment: sandbox >Reporter: Michael Wu >Assignee: Jilin, Jiang > Attachments: Screen Shot 2016-02-25 at 12.05.05.png > > > While creating a policy, to define a rule, users can input a scripting > fragment. From security perspective, such behavior should be forbidden. Such > as . See the attached screenshot. > The project is built upon branch: > https://github.com/zombieJ/incubator-eagle/tree/module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-171) Policy listing table is messed up by too long policy name.
Michael Wu created EAGLE-171: Summary: Policy listing table is messed up by too long policy name. Key: EAGLE-171 URL: https://issues.apache.org/jira/browse/EAGLE-171 Project: Eagle Issue Type: Bug Environment: sandbox Reporter: Michael Wu Assignee: Jilin, Jiang Priority: Minor When any policy name is defined as a long string, in the table for listing policies, the second column is widened to accommodate the whole content. As a result, the table is messed up. The project is built upon branch: https://github.com/zombieJ/incubator-eagle/tree/module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-173) Mark/Un-mark a sensitivity type does not sync status mark in the table list.
[ https://issues.apache.org/jira/browse/EAGLE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-173: - Attachment: Screen Shot 2016-02-25 at 12.52.54.png > Mark/Un-mark a sensitivity type does not sync status mark in the table list. > > > Key: EAGLE-173 > URL: https://issues.apache.org/jira/browse/EAGLE-173 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Jilin, Jiang >Priority: Minor > Attachments: Screen Shot 2016-02-25 at 12.52.54.png > > > On classification page, mark a column as a sensitive type, then in the table > list, the corresponding table doesn't show the "marked" icon. The icon only > shows up when we refresh the page. > The project is built upon branch: > https://github.com/zombieJ/incubator-eagle/tree/module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-171) Policy listing table is messed up by too long policy name.
[ https://issues.apache.org/jira/browse/EAGLE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-171: - Description: When any policy name is defined as a long string, in the table for listing policies, the second column is widened to accommodate the whole content. As a result, the table is messed up. See the screenshot in the attachment. The project is built upon branch: https://github.com/zombieJ/incubator-eagle/tree/module was: When any policy name is defined as a long string, in the table for listing policies, the second column is widened to accommodate the whole content. As a result, the table is messed up. The project is built upon branch: https://github.com/zombieJ/incubator-eagle/tree/module > Policy listing table is messed up by too long policy name. > -- > > Key: EAGLE-171 > URL: https://issues.apache.org/jira/browse/EAGLE-171 > Project: Eagle > Issue Type: Bug > Environment: sandbox >Reporter: Michael Wu >Assignee: Jilin, Jiang >Priority: Minor > Attachments: Screen Shot 2016-02-25 at 11.18.11.png > > > When any policy name is defined as a long string, in the table for listing > policies, the second column is widened to accommodate the whole content. As a > result, the table is messed up. See the screenshot in the attachment. > The project is built upon branch: > https://github.com/zombieJ/incubator-eagle/tree/module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-173) Mark/Un-mark a sensitivity type does not sync status mark in the table list.
Michael Wu created EAGLE-173: Summary: Mark/Un-mark a sensitivity type does not sync status mark in the table list. Key: EAGLE-173 URL: https://issues.apache.org/jira/browse/EAGLE-173 Project: Eagle Issue Type: Bug Reporter: Michael Wu Assignee: Jilin, Jiang Priority: Minor Attachments: Screen Shot 2016-02-25 at 12.52.54.png On classification page, mark a column as a sensitive type, then in the table list, the corresponding table doesn't show the "marked" icon. The icon only shows up when we refresh the page. The project is built upon branch: https://github.com/zombieJ/incubator-eagle/tree/module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-172) Scripting string is allowed to create policy rules.
[ https://issues.apache.org/jira/browse/EAGLE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-172: - Priority: Minor (was: Major) > Scripting string is allowed to create policy rules. > --- > > Key: EAGLE-172 > URL: https://issues.apache.org/jira/browse/EAGLE-172 > Project: Eagle > Issue Type: Bug > Environment: sandbox >Reporter: Michael Wu >Assignee: Jilin, Jiang >Priority: Minor > Attachments: Screen Shot 2016-02-25 at 12.05.05.png > > > While creating a policy, to define a rule, users can input a scripting > fragment. From security perspective, such behavior should be forbidden. Such > as . See the attached screenshot. > The project is built upon branch: > https://github.com/zombieJ/incubator-eagle/tree/module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-261) create jekyll-infra for eagle landing page
Michael Wu created EAGLE-261: Summary: create jekyll-infra for eagle landing page Key: EAGLE-261 URL: https://issues.apache.org/jira/browse/EAGLE-261 Project: Eagle Issue Type: Sub-task Reporter: Michael Wu Assignee: Michael Wu based on branch "document" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-262) create jekyll-infra for eagle version-based page
Michael Wu created EAGLE-262: Summary: create jekyll-infra for eagle version-based page Key: EAGLE-262 URL: https://issues.apache.org/jira/browse/EAGLE-262 Project: Eagle Issue Type: Sub-task Reporter: Michael Wu Assignee: Michael Wu based on branch "master" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-300) Disable spring debug log by default in webservice
Michael Wu created EAGLE-300: Summary: Disable spring debug log by default in webservice Key: EAGLE-300 URL: https://issues.apache.org/jira/browse/EAGLE-300 Project: Eagle Issue Type: Bug Affects Versions: v0.4.0, v0.3.1 Reporter: Michael Wu Assignee: Michael Wu Fix For: v0.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-301) Tables omitted for using mysql
Michael Wu created EAGLE-301: Summary: Tables omitted for using mysql Key: EAGLE-301 URL: https://issues.apache.org/jira/browse/EAGLE-301 Project: Eagle Issue Type: Bug Affects Versions: v0.3.1 Reporter: Michael Wu Assignee: Michael Wu Fix For: v0.4.0 Omitted tables are: alertstream_alertstream alertexecutor_alertexecutor alertstreamschema_alertstreamschema alertdef_alertdef -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-301) Tables omitted for using mysql
[ https://issues.apache.org/jira/browse/EAGLE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-301: - Description: To reproduce the issue: 1. install eagle (based on dev branch) to sandbox and ssh into sandbox, making sure eagle's required components are started up. 2. execute command to enter mysql console: mysql -r root -p (default passcode of ambari's mysql is blank). 3. create mysql user "eagle", setting a preferred passcode, and granting all privileges to the user. 4. relogin mysql as user "eagle", and create database "eagle". 5. modify eagle/conf/eagle-service.conf according to https://github.com/apache/incubator-eagle/blob/dev/eagle-webservice/src/main/resources/application-mysql.conf 6. execute eagle/bin/eagle-service.sh start 7. by either monitoring eagle/logs/eagle-service.out or query tables in mysql, we can find that 12 tables are omitted as below: Omitted tables are: alertstreamschema_alertstreamschema alertdetail_hadoop alertdef_alertdef eagle_metadata_topologyoperation alertstream_alertstream unittest_testtsentity alertexecutor_alertexecutor aggregatedef_aggregatedef eagle_metadata_topologyexecution mlmodel_mlmodel serviceaudit_serviceaudit eagle_metric was: Omitted tables are: alertstream_alertstream alertexecutor_alertexecutor alertstreamschema_alertstreamschema alertdef_alertdef > Tables omitted for using mysql > -- > > Key: EAGLE-301 > URL: https://issues.apache.org/jira/browse/EAGLE-301 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.1 >Reporter: Michael Wu >Assignee: Michael Wu > Fix For: v0.4.0 > > > To reproduce the issue: > 1. install eagle (based on dev branch) to sandbox and ssh into sandbox, > making sure eagle's required components are started up. > 2. execute command to enter mysql console: mysql -r root -p (default passcode > of ambari's mysql is blank). > 3. create mysql user "eagle", setting a preferred passcode, and granting all > privileges to the user. > 4. relogin mysql as user "eagle", and create database "eagle". > 5. modify eagle/conf/eagle-service.conf according to > https://github.com/apache/incubator-eagle/blob/dev/eagle-webservice/src/main/resources/application-mysql.conf > 6. execute eagle/bin/eagle-service.sh start > 7. by either monitoring eagle/logs/eagle-service.out or query tables in > mysql, we can find that 12 tables are omitted as below: > Omitted tables are: > alertstreamschema_alertstreamschema > alertdetail_hadoop > alertdef_alertdef > eagle_metadata_topologyoperation > alertstream_alertstream > unittest_testtsentity > alertexecutor_alertexecutor > aggregatedef_aggregatedef > eagle_metadata_topologyexecution > mlmodel_mlmodel > serviceaudit_serviceaudit > eagle_metric -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-301) Tables omitted for using mysql
[ https://issues.apache.org/jira/browse/EAGLE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290684#comment-15290684 ] Michael Wu commented on EAGLE-301: -- Confirmed this is a bug, will fix it ASAP. > Tables omitted for using mysql > -- > > Key: EAGLE-301 > URL: https://issues.apache.org/jira/browse/EAGLE-301 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.1 >Reporter: Michael Wu >Assignee: Michael Wu > Fix For: v0.4.0 > > > To reproduce the issue: > 1. install eagle (based on dev branch) to sandbox and ssh into sandbox, > making sure eagle's required components are started up. > 2. execute command to enter mysql console: mysql -r root -p (default passcode > of ambari's mysql is blank). > 3. create mysql user "eagle", setting a preferred passcode, and granting all > privileges to the user. > 4. relogin mysql as user "eagle", and create database "eagle". > 5. modify eagle/conf/eagle-service.conf according to > https://github.com/apache/incubator-eagle/blob/dev/eagle-webservice/src/main/resources/application-mysql.conf > 6. execute eagle/bin/eagle-service.sh start > 7. by either monitoring eagle/logs/eagle-service.out or query tables in > mysql, we can find that 12 tables are omitted as below: > Omitted tables are: > alertstreamschema_alertstreamschema > alertdetail_hadoop > alertdef_alertdef > eagle_metadata_topologyoperation > alertstream_alertstream > unittest_testtsentity > alertexecutor_alertexecutor > aggregatedef_aggregatedef > eagle_metadata_topologyexecution > mlmodel_mlmodel > serviceaudit_serviceaudit > eagle_metric -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-301) Tables omitted for using mysql
[ https://issues.apache.org/jira/browse/EAGLE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15292978#comment-15292978 ] Michael Wu commented on EAGLE-301: -- Yes, it was confirmed to be that reason. It's the same thing as in PR #158. So far, it requires that we find a reasonable way to balance large column size and row size limitation. I'm thinking about this. > Tables omitted for using mysql > -- > > Key: EAGLE-301 > URL: https://issues.apache.org/jira/browse/EAGLE-301 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.1 >Reporter: Michael Wu >Assignee: Michael Wu > Fix For: v0.4.0 > > > To reproduce the issue: > 1. install eagle (based on dev branch) to sandbox and ssh into sandbox, > making sure eagle's required components are started up. > 2. execute command to enter mysql console: mysql -r root -p (default passcode > of ambari's mysql is blank). > 3. create mysql user "eagle", setting a preferred passcode, and granting all > privileges to the user. > 4. relogin mysql as user "eagle", and create database "eagle". > 5. modify eagle/conf/eagle-service.conf according to > https://github.com/apache/incubator-eagle/blob/dev/eagle-webservice/src/main/resources/application-mysql.conf > 6. execute eagle/bin/eagle-service.sh start > 7. by either monitoring eagle/logs/eagle-service.out or query tables in > mysql, we can find that 12 tables are omitted as below: > Omitted tables are: > alertstreamschema_alertstreamschema > alertdetail_hadoop > alertdef_alertdef > eagle_metadata_topologyoperation > alertstream_alertstream > unittest_testtsentity > alertexecutor_alertexecutor > aggregatedef_aggregatedef > eagle_metadata_topologyexecution > mlmodel_mlmodel > serviceaudit_serviceaudit > eagle_metric -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-305) Add a config tip to the document for "Application Manager Tutorial" - setting "appCommandLoaderEnabled=true"
Michael Wu created EAGLE-305: Summary: Add a config tip to the document for "Application Manager Tutorial" - setting "appCommandLoaderEnabled=true" Key: EAGLE-305 URL: https://issues.apache.org/jira/browse/EAGLE-305 Project: Eagle Issue Type: Improvement Affects Versions: v0.3.0 Reporter: Michael Wu Assignee: Zhao, Qingwen Priority: Minor Fix For: v0.4.0 In doc "Application Manager Tutorial", there is a config tip omitted: --> step x: in eagle-scheduler.conf, set appCommandLoaderEnabled as "true". Would be great if it could be added to the doc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-306) add metadata for showing "Topology" tab in left-nav by default
Michael Wu created EAGLE-306: Summary: add metadata for showing "Topology" tab in left-nav by default Key: EAGLE-306 URL: https://issues.apache.org/jira/browse/EAGLE-306 Project: Eagle Issue Type: Improvement Affects Versions: v0.3.0 Reporter: Michael Wu Assignee: Zhao, Qingwen Fix For: v0.4.0 When eagle-service is started up, on admin page, in the left-nav, there is no "Topology" tab showing up by default. Users have to add it as a new "Feature" to make it. Could you please add the metadata for default settings? Thanks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-308) Consistency issue: deleting a topology doesn't delete existing topology-execution bound to it.
Michael Wu created EAGLE-308: Summary: Consistency issue: deleting a topology doesn't delete existing topology-execution bound to it. Key: EAGLE-308 URL: https://issues.apache.org/jira/browse/EAGLE-308 Project: Eagle Issue Type: Bug Affects Versions: v0.3.0 Reporter: Michael Wu Assignee: Zhao, Qingwen Fix For: v0.4.0 Reproduce: 1. create a topology named "demo001", and create one topology-execution bound to "demo001". 2. on "management" page, delete "demo001", and confirm the deletion in the pop-up overlay (as a result the topology should be deleted as expected). 3. then turn to "monitoring" page, the topology-execution bound to "demo001" still exists on the page. Point of view: this behavior seems violating the consistency of binding a topology to an execution. Action required: please verify and confirm if this is a bug that the execution should be deleted together with the deletion of "demo001"; or otherwise, in the pop-up overlay of topology deletion, there should be a notification for customers to know that after deleting a topology, corresponding execution will be in wrong status and they should be deleted manually. -- 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 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-311) operations of items listed on topology-management monitoring page require buffering loading approaches
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)
[jira] [Updated] (EAGLE-311) operations of items listed on topology-management monitoring page require buffering loading approaches
[ 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-312) delete a started topology-execution on topology-monitoring page doesn't notify users that the execution may remain in system
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-310) already existing active topology status not displayed when a deleted topology+execution re-created with same name
[ 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 t
[jira] [Updated] (EAGLE-310) already existing active topology status not displayed when a deleted topology+execution re-created with same name
[ 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 me
[jira] [Created] (EAGLE-313) normally stopped topology-execution shows error message in the description column
Michael Wu created EAGLE-313: Summary: normally stopped topology-execution shows error message in the description column Key: EAGLE-313 URL: https://issues.apache.org/jira/browse/EAGLE-313 Project: Eagle Issue Type: Bug Affects Versions: v0.3.0 Reporter: Michael Wu Assignee: Zhao, Qingwen Fix For: v0.4.0 Reproduce: 1. create a topology-execution, start it, and then stop it by hitting the stop button. 2. as a result, after the execution is stopped successfully, there is a error message shown in description column of the execution: "Fail to find topology: eagle-sandbox-hbaseSecurityLog-test-pagination-003". Point of view: such message should be hidden because the execution is stopped normally, from users standpoint, the operation is successful. It's confusing that we show them an error message while actually the operation is successful. Action required: please consider if such error message could be hidden only if the "stop" operation is normally and successfully executed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-314) long text mess table up
Michael Wu created EAGLE-314: Summary: long text mess table up Key: EAGLE-314 URL: https://issues.apache.org/jira/browse/EAGLE-314 Project: Eagle Issue Type: Bug Reporter: Michael Wu Assignee: Jilin, Jiang Priority: Trivial This bug is found on topology management page, may apply to other pages that contains tables. Reproduce: 1. create a topology, and give it a long name + long execute-class. Here, "long text" means a long string with at least 100 chars without blank-space or carriage-return. 2. as a result, the table's first 2 columns will fill the right area of the table and thus other columns are pushed away from the display area. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-84) Create scripts for merging PRs automatically
[
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Wu closed EAGLE-84.
---
Assignee: Michael Wu (was: Hao Chen)
verified, it's done
> 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: Michael Wu
> Fix For: v0.3.0
>
> 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] [Closed] (EAGLE-171) Policy listing table is messed up by too long policy name.
[ https://issues.apache.org/jira/browse/EAGLE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-171. verified, it's done perfectly! > Policy listing table is messed up by too long policy name. > -- > > Key: EAGLE-171 > URL: https://issues.apache.org/jira/browse/EAGLE-171 > Project: Eagle > Issue Type: Bug > Environment: sandbox >Reporter: Michael Wu >Assignee: Jilin, Jiang >Priority: Minor > Attachments: Screen Shot 2016-02-25 at 11.18.11.png > > > When any policy name is defined as a long string, in the table for listing > policies, the second column is widened to accommodate the whole content. As a > result, the table is messed up. See the screenshot in the attachment. > The project is built upon branch: > https://github.com/zombieJ/incubator-eagle/tree/module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-173) Mark/Un-mark a sensitivity type does not sync status mark in the table list.
[ https://issues.apache.org/jira/browse/EAGLE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-173. verified, it's done. > Mark/Un-mark a sensitivity type does not sync status mark in the table list. > > > Key: EAGLE-173 > URL: https://issues.apache.org/jira/browse/EAGLE-173 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Jilin, Jiang >Priority: Minor > Attachments: Screen Shot 2016-02-25 at 12.52.54.png > > > On classification page, mark a column as a sensitive type, then in the table > list, the corresponding table doesn't show the "marked" icon. The icon only > shows up when we refresh the page. > The project is built upon branch: > https://github.com/zombieJ/incubator-eagle/tree/module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-317) error message flashes for an instant while submitting pop-up forms
Michael Wu created EAGLE-317: Summary: error message flashes for an instant while submitting pop-up forms Key: EAGLE-317 URL: https://issues.apache.org/jira/browse/EAGLE-317 Project: Eagle Issue Type: Bug Reporter: Michael Wu Assignee: Jilin, Jiang Reproduce: 1. go to topology management page, and create a topology-execution and submit the pop-up form. 2. as a result, in an instant immediately after the submission, error messages against the form input boxes shows up and disappears as the pop-up form closes. Point of view: although it doesn't block the submission of the form, this may sometime confuse users. Action required: please consider how to make the error message not shown when there is actually no error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-317) error message flashes for an instant while submitting pop-up forms
[ https://issues.apache.org/jira/browse/EAGLE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-317: - Description: Reproduce: 1. go to topology management page, and create a topology-execution and submit the pop-up form. 2. as a result, in an instant immediately after the submission, error messages against the form input boxes shows up and disappears as the pop-up form closes. See the attachment of this ticket. Point of view: although it doesn't block the submission of the form, this may sometime confuse users. Action required: please consider how to make the error message not shown when there is actually no error. was: Reproduce: 1. go to topology management page, and create a topology-execution and submit the pop-up form. 2. as a result, in an instant immediately after the submission, error messages against the form input boxes shows up and disappears as the pop-up form closes. Point of view: although it doesn't block the submission of the form, this may sometime confuse users. Action required: please consider how to make the error message not shown when there is actually no error. > error message flashes for an instant while submitting pop-up forms > -- > > Key: EAGLE-317 > URL: https://issues.apache.org/jira/browse/EAGLE-317 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Jilin, Jiang > Attachments: error_msg.png > > > Reproduce: > 1. go to topology management page, and create a topology-execution and submit > the pop-up form. > 2. as a result, in an instant immediately after the submission, error > messages against the form input boxes shows up and disappears as the pop-up > form closes. > See the attachment of this ticket. > Point of view: although it doesn't block the submission of the form, this may > sometime confuse users. > Action required: please consider how to make the error message not shown when > there is actually no error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-317) error message flashes for an instant while submitting pop-up forms
[ https://issues.apache.org/jira/browse/EAGLE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-317: - Attachment: error_msg.png > error message flashes for an instant while submitting pop-up forms > -- > > Key: EAGLE-317 > URL: https://issues.apache.org/jira/browse/EAGLE-317 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Jilin, Jiang > Attachments: error_msg.png > > > Reproduce: > 1. go to topology management page, and create a topology-execution and submit > the pop-up form. > 2. as a result, in an instant immediately after the submission, error > messages against the form input boxes shows up and disappears as the pop-up > form closes. > Point of view: although it doesn't block the submission of the form, this may > sometime confuse users. > Action required: please consider how to make the error message not shown when > there is actually no error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-317) error message flashes for an instant while submitting pop-up forms
[ https://issues.apache.org/jira/browse/EAGLE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-317: - Priority: Trivial (was: Major) > error message flashes for an instant while submitting pop-up forms > -- > > Key: EAGLE-317 > URL: https://issues.apache.org/jira/browse/EAGLE-317 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Jilin, Jiang >Priority: Trivial > Attachments: error_msg.png > > > Reproduce: > 1. go to topology management page, and create a topology-execution and submit > the pop-up form. > 2. as a result, in an instant immediately after the submission, error > messages against the form input boxes shows up and disappears as the pop-up > form closes. > See the attachment of this ticket. > Point of view: although it doesn't block the submission of the form, this may > sometime confuse users. > Action required: please consider how to make the error message not shown when > there is actually no error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-318) db entity column name "user" happens to be a reserved keyword of derby DB
Michael Wu created EAGLE-318: Summary: db entity column name "user" happens to be a reserved keyword of derby DB Key: EAGLE-318 URL: https://issues.apache.org/jira/browse/EAGLE-318 Project: Eagle Issue Type: Bug Reporter: Michael Wu Assignee: Hao Chen Priority: Minor Phenomenon: when derby DB is configured for eagle service, table "mlmodel_mlmodel" is not created successfully because one of its columns "user" happens to be a reserved keyword of derby DB. Action required: need to re-name the column with other word than "user", and modify relevant code if necessary. DB logs for reference: * 2016-05-27 06:26:29,215 DEBUG [http-bio-9099-exec-9] derby.DerbyPlatform[305]: About to execute SQL -- --- -- mlmodel_mlmodel -- --- CREATE TABLE mlmodel_mlmodel ( uuid VARCHAR(254) NOT NULL, timestamp BIGINT, site VARCHAR(8192), user VARCHAR(8192), algorithm VARCHAR(8192), content LONG VARCHAR, version BIGINT, PRIMARY KEY (uuid) ) 2016-05-27 06:26:29,236 WARN [http-bio-9099-exec-9] derby.DerbyPlatform[322]: SQL Command -- --- -- mlmodel_mlmodel -- --- CREATE TABLE mlmodel_mlmodel ( uuid VARCHAR(254) NOT NULL, timestamp BIGINT, site VARCHAR(8192), user VARCHAR(8192), algorithm VARCHAR(8192), content LONG VARCHAR, version BIGINT, PRIMARY KEY (uuid) ) failed with: Syntax error: Encountered "user" at line 10, column 5. 2016-05-27 06:26:29,237 DEBUG [http-bio-9099-exec-9] derby.DerbyPlatform[325]: java.sql.SQLSyntaxErrorException: Syntax error: Encountered "user" at line 10, column 5. * -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-319) java.sql.SQLSyntaxErrorException caught when querying from table topologyExecutionEntity
Michael Wu created EAGLE-319: Summary: java.sql.SQLSyntaxErrorException caught when querying from table topologyExecutionEntity Key: EAGLE-319 URL: https://issues.apache.org/jira/browse/EAGLE-319 Project: Eagle Issue Type: Bug Reporter: Michael Wu Assignee: Michael Wu When querying from table topology_execution, met below error in eagle service log: Error log with stacktrace: *** [ERROR] [05/27/2016 06:26:34.971] [application-manager-scheduler-akka.actor.default-dispatcher-19] [akka://application-manager-scheduler/user/$a/command-worker] Fail to load any topologyExecutionEntity due to Exception: java.io.IOException: org.apache.torque.TorqueException: java.sql.SQLSyntaxErrorException: Comparisons between 'LONG VARCHAR (UCS_BASIC)' and 'LONG VARCHAR (UCS_BASIC)' are not supported. Types must be comparable. String types must also have matching collation. If collation does not match, a possible solution is to cast operands to force them to the default collation (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) = 'T1') org.apache.eagle.storage.jdbc.JdbcStorage.query(JdbcStorage.java:179) org.apache.eagle.storage.operation.QueryStatement.execute(QueryStatement.java:47) org.apache.eagle.service.generic.GenericEntityServiceResource.search(GenericEntityServiceResource.java:443) sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:606) com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288) *** -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-320) Pull Request Reviewer CI job fails to checkout dev branch
Michael Wu created EAGLE-320: Summary: Pull Request Reviewer CI job fails to checkout dev branch Key: EAGLE-320 URL: https://issues.apache.org/jira/browse/EAGLE-320 Project: Eagle Issue Type: Bug Reporter: Michael Wu Assignee: Michael Wu https://builds.apache.org/job/incubator-eagle-pr-reviewer/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-320) Pull Request Reviewer CI job fails to checkout dev branch
[ https://issues.apache.org/jira/browse/EAGLE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304150#comment-15304150 ] Michael Wu commented on EAGLE-320: -- The git repo on a slave was in a wrong status by some accident, cleaned it and the issue was fixed. > Pull Request Reviewer CI job fails to checkout dev branch > - > > Key: EAGLE-320 > URL: https://issues.apache.org/jira/browse/EAGLE-320 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Michael Wu > > https://builds.apache.org/job/incubator-eagle-pr-reviewer/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-320) Pull Request Reviewer CI job fails to checkout dev branch
[ https://issues.apache.org/jira/browse/EAGLE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-320. Resolution: Fixed fixed. > Pull Request Reviewer CI job fails to checkout dev branch > - > > Key: EAGLE-320 > URL: https://issues.apache.org/jira/browse/EAGLE-320 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Michael Wu > > https://builds.apache.org/job/incubator-eagle-pr-reviewer/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-300) Disable spring debug log by default in webservice
[ https://issues.apache.org/jira/browse/EAGLE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-300. Resolution: Fixed fixed. > Disable spring debug log by default in webservice > - > > Key: EAGLE-300 > URL: https://issues.apache.org/jira/browse/EAGLE-300 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0, v0.3.1 >Reporter: Michael Wu >Assignee: Michael Wu > Fix For: v0.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-322) setup Buildbot configuration for eagle documentation
Michael Wu created EAGLE-322: Summary: setup Buildbot configuration for eagle documentation Key: EAGLE-322 URL: https://issues.apache.org/jira/browse/EAGLE-322 Project: Eagle Issue Type: Task Reporter: Michael Wu Assignee: Michael Wu Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-326) typo found in eagle documentation
Michael Wu created EAGLE-326: Summary: typo found in eagle documentation Key: EAGLE-326 URL: https://issues.apache.org/jira/browse/EAGLE-326 Project: Eagle Issue Type: Bug Affects Versions: v0.3.0 Reporter: Michael Wu Assignee: Michael Wu Priority: Trivial Fix For: v0.4.0 found ".app" which is supposed to be "app.", it impacts configuration for application. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-328) pr review jenkins job fails and has problems with jdk1.8 and pr comparison base branch
Michael Wu created EAGLE-328: Summary: pr review jenkins job fails and has problems with jdk1.8 and pr comparison base branch Key: EAGLE-328 URL: https://issues.apache.org/jira/browse/EAGLE-328 Project: Eagle Issue Type: Bug Reporter: Michael Wu Assignee: Michael Wu depending ticket: https://issues.apache.org/jira/browse/INFRA-12035 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (EAGLE-273) Issue with creating MySql tables , only 14 were created out of 24, reason being varchar(30000) for multiple columns lead to exceeding the maximum row size of 65,535 byte
[ https://issues.apache.org/jira/browse/EAGLE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu reassigned EAGLE-273: Assignee: Michael Wu (was: Hao Chen) > Issue with creating MySql tables , only 14 were created out of 24, reason > being varchar(3) for multiple columns lead to exceeding the maximum row > size of 65,535 bytes. > > > Key: EAGLE-273 > URL: https://issues.apache.org/jira/browse/EAGLE-273 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.0 >Reporter: Hao Chen >Assignee: Michael Wu > Fix For: v0.4.0 > > > h2. Problem > Issue with creating MySql tables , only 14 were created out of 24, reason > being varchar(3) for multiple columns lead to exceeding the maximum row > size of 65,535 bytes. I can look into this and fix it. Workaround is to > create the tables manually after changing the DDL. > h2. Root Cause & Problem > The problem is cause the limitation of maximum row size in mysql innodb > engine, so need to keep the column size relatively small, but it will cause > it can't store large field, it's a little tricky, so may have following > possible solutions: > * Solution One: Fix mysql innodb size to resolve the limitation. > * Solution Two: Keep the field relatively small to avoid exceeding maximum > row size and make sure creating table successfully, and modify field size > according to actual usage (Which is the approach we take for this problem) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-261) create jekyll-infra for eagle landing page
[ https://issues.apache.org/jira/browse/EAGLE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-261. Resolution: Won't Fix This task had been canceled. > create jekyll-infra for eagle landing page > -- > > Key: EAGLE-261 > URL: https://issues.apache.org/jira/browse/EAGLE-261 > Project: Eagle > Issue Type: Sub-task >Reporter: Michael Wu >Assignee: Michael Wu > Fix For: v0.4.0 > > > based on branch "document" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (EAGLE-261) create jekyll-infra for eagle landing page
[ https://issues.apache.org/jira/browse/EAGLE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu reopened EAGLE-261: -- Would like to move it to v0.5.0 > create jekyll-infra for eagle landing page > -- > > Key: EAGLE-261 > URL: https://issues.apache.org/jira/browse/EAGLE-261 > Project: Eagle > Issue Type: Sub-task >Reporter: Michael Wu >Assignee: Michael Wu > Fix For: v0.4.0 > > > based on branch "document" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-262) create jekyll-infra for eagle version-based page
[ https://issues.apache.org/jira/browse/EAGLE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-262: - Fix Version/s: (was: v0.4.0) v0.5.0 > create jekyll-infra for eagle version-based page > > > Key: EAGLE-262 > URL: https://issues.apache.org/jira/browse/EAGLE-262 > Project: Eagle > Issue Type: Sub-task >Reporter: Michael Wu >Assignee: Michael Wu > Fix For: v0.5.0 > > > based on branch "master" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (EAGLE-269) Comparisons between 'LONG VARCHAR (UCS_BASIC)' and 'LONG VARCHAR (UCS_BASIC)' are not supported
[
https://issues.apache.org/jira/browse/EAGLE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Wu reassigned EAGLE-269:
Assignee: Michael Wu (was: Hao Chen)
> Comparisons between 'LONG VARCHAR (UCS_BASIC)' and 'LONG VARCHAR (UCS_BASIC)'
> are not supported
> ---
>
> Key: EAGLE-269
> URL: https://issues.apache.org/jira/browse/EAGLE-269
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Zhao, Qingwen
>Assignee: Michael Wu
> Fix For: v0.4.0
>
>
> {code}
> 2016-04-17 12:03:53,862 DEBUG [http-bio-9098-exec-1]
> operation.CompiledQuery[267]: Output fields: all
> 2016-04-17 12:03:53,886 DEBUG [http-bio-9098-exec-1]
> impl.JdbcEntityReaderImpl[62]: Querying: SELECT
> eagle_metadata_topologyoperation.* FROM eagle_metadata_topologyoperation
> WHERE (eagle_metadata_topologyoperation.timestamp>=? AND
> eagle_metadata_topologyoperation.timestamp eagle_metadata_topologyoperation.status=?) FETCH NEXT 2147483647 ROWS ONLY
> Replacements: [1458273833859,1460865833859,PENDING]
> 2016-04-17 12:03:53,886 DEBUG [http-bio-9098-exec-3]
> impl.JdbcEntityReaderImpl[62]: Querying: SELECT
> eagle_metadata_topologyoperation.* FROM eagle_metadata_topologyoperation
> WHERE (eagle_metadata_topologyoperation.timestamp>=? AND
> eagle_metadata_topologyoperation.timestamp eagle_metadata_topologyoperation.status=?) FETCH NEXT 2147483647 ROWS ONLY
> Replacements: [1458273833859,1460865833859,INITIALIZED]
> 2016-04-17 12:03:53,905 ERROR [http-bio-9098-exec-1]
> impl.JdbcEntityReaderImpl[81]: Failed to query by: SELECT
> eagle_metadata_topologyoperation.* FROM eagle_metadata_topologyoperation
> WHERE (eagle_metadata_topologyoperation.timestamp>=? AND
> eagle_metadata_topologyoperation.timestamp eagle_metadata_topologyoperation.status=?) FETCH NEXT 2147483647 ROWS ONLY
> Replacements: [1458273833859,1460865833859,PENDING], due to:
> java.sql.SQLSyntaxErrorException: Comparisons between 'LONG VARCHAR
> (UCS_BASIC)' and 'LONG VARCHAR (UCS_BASIC)' are not supported. Types must be
> comparable. String types must also have matching collation. If collation does
> not match, a possible solution is to cast operands to force them to the
> default collation (e.g. SELECT tablename FROM sys.systables WHERE
> CAST(tablename AS VARCHAR(128)) = 'T1')
> org.apache.torque.TorqueException: java.sql.SQLSyntaxErrorException:
> Comparisons between 'LONG VARCHAR (UCS_BASIC)' and 'LONG VARCHAR (UCS_BASIC)'
> are not supported. Types must be comparable. String types must also have
> matching collation. If collation does not match, a possible solution is to
> cast operands to force them to the default collation (e.g. SELECT tablename
> FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) = 'T1')
> at
> org.apache.torque.util.ExceptionMapperImpl.toTorqueException(ExceptionMapperImpl.java:59)
> at org.apache.torque.util.BasePeerImpl.doSelect(BasePeerImpl.java:1608)
> at org.apache.torque.util.BasePeerImpl.doSelect(BasePeerImpl.java:1152)
> at
> org.apache.eagle.storage.jdbc.entity.impl.JdbcEntityReaderImpl.query(JdbcEntityReaderImpl.java:75)
> at org.apache.eagle.storage.jdbc.JdbcStorage.query(JdbcStorage.java:161)
> at
> org.apache.eagle.storage.operation.QueryStatement.execute(QueryStatement.java:47)
> at
> org.apache.eagle.service.generic.GenericEntityServiceResource.search(GenericEntityServiceResource.java:443)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
> at
> com.sun.jersey.server.im
[jira] [Updated] (EAGLE-261) create jekyll-infra for eagle landing page
[ https://issues.apache.org/jira/browse/EAGLE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-261: - Fix Version/s: (was: v0.4.0) v0.5.0 > create jekyll-infra for eagle landing page > -- > > Key: EAGLE-261 > URL: https://issues.apache.org/jira/browse/EAGLE-261 > Project: Eagle > Issue Type: Sub-task >Reporter: Michael Wu >Assignee: Michael Wu > Fix For: v0.5.0 > > > based on branch "document" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-269) Comparisons between 'LONG VARCHAR (UCS_BASIC)' and 'LONG VARCHAR (UCS_BASIC)' are not supported
[
https://issues.apache.org/jira/browse/EAGLE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Wu resolved EAGLE-269.
--
Resolution: Fixed
waiting for merging PR #222
> Comparisons between 'LONG VARCHAR (UCS_BASIC)' and 'LONG VARCHAR (UCS_BASIC)'
> are not supported
> ---
>
> Key: EAGLE-269
> URL: https://issues.apache.org/jira/browse/EAGLE-269
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Zhao, Qingwen
>Assignee: Michael Wu
> Fix For: v0.4.0
>
>
> {code}
> 2016-04-17 12:03:53,862 DEBUG [http-bio-9098-exec-1]
> operation.CompiledQuery[267]: Output fields: all
> 2016-04-17 12:03:53,886 DEBUG [http-bio-9098-exec-1]
> impl.JdbcEntityReaderImpl[62]: Querying: SELECT
> eagle_metadata_topologyoperation.* FROM eagle_metadata_topologyoperation
> WHERE (eagle_metadata_topologyoperation.timestamp>=? AND
> eagle_metadata_topologyoperation.timestamp eagle_metadata_topologyoperation.status=?) FETCH NEXT 2147483647 ROWS ONLY
> Replacements: [1458273833859,1460865833859,PENDING]
> 2016-04-17 12:03:53,886 DEBUG [http-bio-9098-exec-3]
> impl.JdbcEntityReaderImpl[62]: Querying: SELECT
> eagle_metadata_topologyoperation.* FROM eagle_metadata_topologyoperation
> WHERE (eagle_metadata_topologyoperation.timestamp>=? AND
> eagle_metadata_topologyoperation.timestamp eagle_metadata_topologyoperation.status=?) FETCH NEXT 2147483647 ROWS ONLY
> Replacements: [1458273833859,1460865833859,INITIALIZED]
> 2016-04-17 12:03:53,905 ERROR [http-bio-9098-exec-1]
> impl.JdbcEntityReaderImpl[81]: Failed to query by: SELECT
> eagle_metadata_topologyoperation.* FROM eagle_metadata_topologyoperation
> WHERE (eagle_metadata_topologyoperation.timestamp>=? AND
> eagle_metadata_topologyoperation.timestamp eagle_metadata_topologyoperation.status=?) FETCH NEXT 2147483647 ROWS ONLY
> Replacements: [1458273833859,1460865833859,PENDING], due to:
> java.sql.SQLSyntaxErrorException: Comparisons between 'LONG VARCHAR
> (UCS_BASIC)' and 'LONG VARCHAR (UCS_BASIC)' are not supported. Types must be
> comparable. String types must also have matching collation. If collation does
> not match, a possible solution is to cast operands to force them to the
> default collation (e.g. SELECT tablename FROM sys.systables WHERE
> CAST(tablename AS VARCHAR(128)) = 'T1')
> org.apache.torque.TorqueException: java.sql.SQLSyntaxErrorException:
> Comparisons between 'LONG VARCHAR (UCS_BASIC)' and 'LONG VARCHAR (UCS_BASIC)'
> are not supported. Types must be comparable. String types must also have
> matching collation. If collation does not match, a possible solution is to
> cast operands to force them to the default collation (e.g. SELECT tablename
> FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) = 'T1')
> at
> org.apache.torque.util.ExceptionMapperImpl.toTorqueException(ExceptionMapperImpl.java:59)
> at org.apache.torque.util.BasePeerImpl.doSelect(BasePeerImpl.java:1608)
> at org.apache.torque.util.BasePeerImpl.doSelect(BasePeerImpl.java:1152)
> at
> org.apache.eagle.storage.jdbc.entity.impl.JdbcEntityReaderImpl.query(JdbcEntityReaderImpl.java:75)
> at org.apache.eagle.storage.jdbc.JdbcStorage.query(JdbcStorage.java:161)
> at
> org.apache.eagle.storage.operation.QueryStatement.execute(QueryStatement.java:47)
> at
> org.apache.eagle.service.generic.GenericEntityServiceResource.search(GenericEntityServiceResource.java:443)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
> at
> com.sun.jersey.serve
[jira] [Resolved] (EAGLE-319) java.sql.SQLSyntaxErrorException caught when querying from table topologyExecutionEntity
[ https://issues.apache.org/jira/browse/EAGLE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu resolved EAGLE-319. -- Resolution: Fixed waiting for merging PR #222 > java.sql.SQLSyntaxErrorException caught when querying from table > topologyExecutionEntity > > > Key: EAGLE-319 > URL: https://issues.apache.org/jira/browse/EAGLE-319 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Michael Wu > Fix For: v0.4.0 > > > When querying from table topology_execution, met below error in eagle service > log: > Error log with stacktrace: > *** > [ERROR] [05/27/2016 06:26:34.971] > [application-manager-scheduler-akka.actor.default-dispatcher-19] > [akka://application-manager-scheduler/user/$a/command-worker] Fail to load > any topologyExecutionEntity due to Exception: java.io.IOException: > org.apache.torque.TorqueException: java.sql.SQLSyntaxErrorException: > Comparisons between 'LONG VARCHAR (UCS_BASIC)' and 'LONG VARCHAR (UCS_BASIC)' > are not supported. Types must be comparable. String types must also have > matching collation. If collation does not match, a possible solution is to > cast operands to force them to the default collation (e.g. SELECT tablename > FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) = 'T1') > org.apache.eagle.storage.jdbc.JdbcStorage.query(JdbcStorage.java:179) > org.apache.eagle.storage.operation.QueryStatement.execute(QueryStatement.java:47) > org.apache.eagle.service.generic.GenericEntityServiceResource.search(GenericEntityServiceResource.java:443) > sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source) > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > java.lang.reflect.Method.invoke(Method.java:606) > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288) > *** -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-319) java.sql.SQLSyntaxErrorException caught when querying from table topologyExecutionEntity
[ https://issues.apache.org/jira/browse/EAGLE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-319: - Fix Version/s: v0.4.0 > java.sql.SQLSyntaxErrorException caught when querying from table > topologyExecutionEntity > > > Key: EAGLE-319 > URL: https://issues.apache.org/jira/browse/EAGLE-319 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Michael Wu > Fix For: v0.4.0 > > > When querying from table topology_execution, met below error in eagle service > log: > Error log with stacktrace: > *** > [ERROR] [05/27/2016 06:26:34.971] > [application-manager-scheduler-akka.actor.default-dispatcher-19] > [akka://application-manager-scheduler/user/$a/command-worker] Fail to load > any topologyExecutionEntity due to Exception: java.io.IOException: > org.apache.torque.TorqueException: java.sql.SQLSyntaxErrorException: > Comparisons between 'LONG VARCHAR (UCS_BASIC)' and 'LONG VARCHAR (UCS_BASIC)' > are not supported. Types must be comparable. String types must also have > matching collation. If collation does not match, a possible solution is to > cast operands to force them to the default collation (e.g. SELECT tablename > FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) = 'T1') > org.apache.eagle.storage.jdbc.JdbcStorage.query(JdbcStorage.java:179) > org.apache.eagle.storage.operation.QueryStatement.execute(QueryStatement.java:47) > org.apache.eagle.service.generic.GenericEntityServiceResource.search(GenericEntityServiceResource.java:443) > sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source) > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > java.lang.reflect.Method.invoke(Method.java:606) > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288) > *** -- This message was sent by Atlassian JIRA (v6.3.4#6332)
