You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:57:09 UTC
[jira] [Commented] (OOZIE-267) GH-383: Create a set of JPA
executors to replace part of old store service
[ https://issues.apache.org/jira/browse/OOZIE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099931#comment-13099931 ]
Hadoop QA commented on OOZIE-267:
---------------------------------
brookwc remarked:
Note this issue depends on GH-0377.
> GH-383: Create a set of JPA executors to replace part of old store service
> --------------------------------------------------------------------------
>
> Key: OOZIE-267
> URL: https://issues.apache.org/jira/browse/OOZIE-267
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> This issue is to create a set of JPA executors to replace part of old store service.
> Note this is a small portion of the whole effort of the transition from store service to JPA executor acess pattern.
> More specifically, this issue covers:
> CoordActionGetForExternalIdJPAExecutor
> CoordJobGetActionForNominalTimeJPAExecutor
> CoordJobGetActionsForDatesJPAExecutor
> CoordJobGetActionsJPAExecutor
> CoordJobGetActionsSubsetJPAExecutor
> CoordJobGetReadyActionsJPAExecutor
> CoordJobGetRunningActionsCountJPAExecutor
> WorkflowJobGetActionsJPAExecutor
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira