You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Edward Zhang (JIRA)" <ji...@apache.org> on 2015/12/17 01:48:46 UTC
[jira] [Commented] (EAGLE-95) DAM HDFS topology fails to start, if
there is invalid policy.
[ https://issues.apache.org/jira/browse/EAGLE-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061236#comment-15061236 ]
Edward Zhang commented on EAGLE-95:
-----------------------------------
We should introduce policy markdown feature. Eagle framework can mark down policy which has compilation issue either because of wrong syntax or schema change. Markdown can be manual or programmatically by topology in runtime.
User can fix those markdown polices and tune them to be passing compilation.
Markdown is different from enabled field though they have similar functionality.
Markdown can have markdown reasons.
> 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
> 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)