[
https://issues.apache.org/jira/browse/FALCON-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069460#comment-15069460
]
Pallavi Rao commented on FALCON-1640:
-------------------------------------
Me, [~pavan kumar], and [~sriksun] had discussed this offline. A few reasons to
delete instances:
1. The state store has to be lean for queries to be fast. Just keep what is
required.
2. We have metadata API to cater to querying on history (yes, it has to be
enabled).
3. And, as you stated, the IDs have no versioning yet, which makes it difficult
restore the correct state.
> 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)
