[ https://issues.apache.org/jira/browse/OOZIE-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579627#comment-16579627 ]
Hadoop QA commented on OOZIE-3229: ---------------------------------- Testing JIRA OOZIE-3229 Cleaning local git workspace ---------------------------- {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:red}-1 RAW_PATCH_ANALYSIS{color} . {color:green}+1{color} the patch does not introduce any @author tags . {color:green}+1{color} the patch does not introduce any tabs . {color:green}+1{color} the patch does not introduce any trailing spaces . {color:red}-1{color} the patch contains 1 line(s) longer than 132 characters . {color:green}+1{color} the patch adds/modifies 3 testcase(s) {color:green}+1 RAT{color} . {color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} {color:green}+1 JAVADOC{color} . {color:green}+1{color} the patch does not seem to introduce new Javadoc warning(s) . {color:green}+1{color} the patch does not seem to introduce new Javadoc error(s) . {color:red}ERROR{color}: the current HEAD has 2 Javadoc error(s) {color:green}+1 COMPILE{color} . {color:green}+1{color} HEAD compiles . {color:green}+1{color} patch compiles . {color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. {color:green}+1 BACKWARDS_COMPATIBILITY{color} . {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations . {color:green}+1{color} the patch does not modify JPA files {color:green}+1 TESTS{color} . Tests run: 2963 . {color:orange}Tests failed at first run:{color} TestCoordActionsKillXCommand#testActionKillCommandActionNumbers TestCoordMaterializeTriggerService#testCoordMaterializeTriggerService3 . For the complete list of flaky tests, see TEST-SUMMARY-FULL files. {color:green}+1 DISTRO{color} . {color:green}+1{color} distro tarball builds with the patch ---------------------------- {color:red}*-1 Overall result, please check the reported -1(s)*{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/754/ > Improved filtering options in V2SLAServlet > ------------------------------------------ > > Key: OOZIE-3229 > URL: https://issues.apache.org/jira/browse/OOZIE-3229 > Project: Oozie > Issue Type: New Feature > Components: client > Affects Versions: 5.0.0, 4.3.1 > Reporter: Andras Piros > Assignee: Andras Salamon > Priority: Major > Fix For: 5.1.0 > > Attachments: OOZIE-3229-1.patch, OOZIE-3229-2.patch, > OOZIE-3229-3.patch, OOZIE-3229-4.patch, OOZIE-3229-5.patch > > > Currently we can apply a range of filters on top of {{V2SLAServlet}} that can > be used in a rich but undocumented set of ways: > * {{id}} > * {{parent_id}} > * {{event_status}} > * {{app_name}} > * {{nominal_start}} > * {{nominal_end}} > Need to refactor {{V2SLAServlet}} to feature: > * a richer set of {{SLAEvent}}, {{SLARegistration}}, and {{SLASummary}} > filtering based on their attributes > * filter options will always be {{AND}}-ed, never {{OR}}-ed to each other > * maintain compatibility with the parameter names and behavior used thus far > * remove {{SLASummaryFilter}} and refactor > {{SLASummaryGetForFilterJPAExecutor}} as just another possibility for > confusion > * document new functionality with rich use case / example library so that > users can leverage -- This message was sent by Atlassian JIRA (v7.6.3#76005)