[ https://issues.apache.org/jira/browse/EAGLE-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122869#comment-15122869 ]
ASF GitHub Bot commented on EAGLE-95: ------------------------------------- Github user RalphSu commented on the pull request: https://github.com/apache/incubator-eagle/pull/71#issuecomment-176549583 @yonzhang @murkrishn The AlertDefinitionDAOImpl could be replaced by PolicyDefinitionDAOImpl. The last time refactor doesn't remove alertdefinition dao impl. I filed https://issues.apache.org/jira/browse/EAGLE-142 to do this. For this pull request, you might go ahead and leave it there, i will clean up it. > DAM HDFS topology fails to start, if there is invalid policy. > ------------------------------------------------------------- > > Key: EAGLE-95 > URL: https://issues.apache.org/jira/browse/EAGLE-95 > Project: Eagle > Issue Type: Bug > Reporter: hemanth dendukuri > Assignee: Senthilkumar > Priority: Critical > > Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') > and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) > Step 2 : Deploy Dam HDFS topology. > Actual : The HDFS topology could not start because of the invalid policy. > 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor > AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] > Async loop interrupted! > Expected: Topology should start ignoring the invalid policy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)