[
https://issues.apache.org/jira/browse/OOZIE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743413#comment-13743413
]
Rohini Palaniswamy commented on OOZIE-1499:
-------------------------------------------
Summarizing the work being done here:
1) We are updating the whole object in most places including columns not
modified. This has serious performance problems when CLOB columns are involved.
We have had DB getting deadlocked with this case when there are too many
updates. So we want to look at all places where there are updates and only
update subset of modified columns. This is already being done in some cases
like coord action input check.
2) em.merge does a select query and then does a update. We are getting rid
of it as it requires 2 DB calls to do a update and doing direct UPDATE queries.
3) We are getting rid of the multiple JPAExecutor classes. It is growing a
lot and becoming unmanageable. Also a new object is instantiated every time
adding to GC load. So have defined a new interface with implementing singleton
classes to execute queries.
4) We are trying to reuse the Query objects and reset parameters on it for
speeding up performance.
> Update only necessary columns and consolidate JPA Executors
> -----------------------------------------------------------
>
> Key: OOZIE-1499
> URL: https://issues.apache.org/jira/browse/OOZIE-1499
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Ryota Egashira
> Assignee: Ryota Egashira
>
> In some commands, unchanged/unnecessary columns are updated using em.merge.
> only necessary ones should be updated.
> also there are many JPA Executors (one for each query) now, and these can be
> consolidated.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
