falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1640) Cascading Delete for instances in Native Scheduler
Date Wed, 23 Dec 2015 09:59:46 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069449#comment-15069449
] 

Ajay Yadava commented on FALCON-1640:
-------------------------------------

Ideally I would prefer that the database maintains the entire history and old instances are
not deleted but I suspect that the way we are generating the id will prohibit it.

> Cascading Delete for instances in Native Scheduler  
> ----------------------------------------------------
>
>                 Key: FALCON-1640
>                 URL: https://issues.apache.org/jira/browse/FALCON-1640
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: scheduler
>    Affects Versions: 0.9
>            Reporter: pavan kumar kolamuri
>            Assignee: pavan kumar kolamuri
>            Priority: Blocker
>             Fix For: 0.9
>
>         Attachments: FALCON-1640.patch
>
>
> Whenever entity is deleted, all instances should be deleted from state store cascadingly
during Native Scheduler.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message