[
https://issues.apache.org/jira/browse/FALCON-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069473#comment-15069473
]
Ajay Yadava commented on FALCON-1640:
-------------------------------------
Thanks for clarifying [~pallavi.rao], I also suspected same reasons. It's just
that I felt that it's better to have all the historic and current data in same
place, querying from graph database is another pain, querying for both history
and current will also be another pain point. Anyhow I don't think there are any
strong use cases for this. I was just thinking out loud.
> 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)
