You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "David Villegas (JIRA)" <ji...@apache.org> on 2014/08/04 22:12:11 UTC

[jira] [Updated] (OOZIE-1889) Convert NamedNativeQueries to JPQL

     [ https://issues.apache.org/jira/browse/OOZIE-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Villegas updated OOZIE-1889:
----------------------------------

    Attachment: OOZIE-1889.patch

Two test failures are unrelated. The other one actually uncovered an incorrect field name in the query. Fixing in new patch.

With this patch, all tests pass in my side, the new code is more readable, and there are no more native queries in Oozie's code.

> Convert NamedNativeQueries to JPQL
> ----------------------------------
>
>                 Key: OOZIE-1889
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1889
>             Project: Oozie
>          Issue Type: Improvement
>    Affects Versions: trunk
>            Reporter: David Villegas
>            Assignee: David Villegas
>             Fix For: trunk
>
>         Attachments: OOZIE-1889.patch, OOZIE-1889.patch
>
>
> Currently, there is only one JPA NamedNativeQuery (GET_READY_ACTIONS_GROUP_BY_JOBID). By converting it to a regular NamedQuery in JPQL, it can take advantage of JPA capabilities, such as configuring the DB schema as a property (Required for issues such as OOZIE-814 and OOZIE-80)



--
This message was sent by Atlassian JIRA
(v6.2#6252)