[
https://issues.apache.org/jira/browse/OOZIE-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175427#comment-14175427
]
Robert Kanter commented on OOZIE-1803:
--------------------------------------
{quote}Why not make it part of oozie and provide it as an alternative purging
logic. Users can choose depend on their usecase.{quote}
This sounds like a good idea to me. I haven't had a chance to look through the
patch, but from the comments, it sounds like the behavior is somewhat different
from the current behavior. I'd say we should include this as another
implementation of the PurgeService, and users can switch to it if they want (we
should keep the current one for backwards compatibility; if the new one is so
much better, we can make it the default later). Trying to maintain a lot of
different options and behaviors in a single PurgeService is just going to make
things confusing both code-wise and for the user. Luckily, PurgeService is a
Service, so it can easily be overwritten with a new one and we can provide one
with this different behavior.
> 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)
