[
https://issues.apache.org/jira/browse/OOZIE-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172054#comment-14172054
]
Jaydeep Vishwakarma commented on OOZIE-1803:
--------------------------------------------
I feel most of the piece of code what I have added or worked is related to
query optimization of purge service. Which can be added in any case. Even
current purge service logic where [~shwethags] raised the question on
recursion, in practical will not go to deeper than 3 level. So that recursion
cannot impact much on performance.
Any how we can deal with separate jira to handle frequency based coordinator.
> Improvement in Purge service
> ----------------------------
>
> Key: OOZIE-1803
> URL: https://issues.apache.org/jira/browse/OOZIE-1803
> Project: Oozie
> Issue Type: Improvement
> Components: core
> Reporter: Jaydeep Vishwakarma
> Assignee: Jaydeep Vishwakarma
> Attachments: OOZIE-1803-v1.patch, OOZIE-1803-v2.patch,
> OOZIE-1803-v3.patch, OOZIE-1803.patch, purgeservice-1.patch,
> purgeservice.patch
>
>
> Current purge service of oozie have some performance issues and it might help
> to look at the queries and indexes to improve the the purge service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
