[
https://issues.apache.org/jira/browse/OOZIE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682328#comment-13682328
]
Alejandro Abdelnur commented on OOZIE-1398:
-------------------------------------------
got it. So we should take care of the 3rd one then, may be introducing a
constant in JPAService that defines the DB version and the DB tool checks/sets
to it. So when we do a DB change we change the constant value and the DB tool
will just do the check for the new version. In the JPAService we should check
the value of that DB version using direct JDBC not to have mapping conflict if
the DB is of an earlier version (I'm not sure but JPA could fail to initialize).
> [Scale] Reduce the number of CLOB columns used
> ----------------------------------------------
>
> Key: OOZIE-1398
> URL: https://issues.apache.org/jira/browse/OOZIE-1398
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: trunk, 3.3.2
> Reporter: Rohini Palaniswamy
> Assignee: Ryota Egashira
> Fix For: trunk
>
> Attachments: OOZIE-1398-v4.patch, OOZIE-1398-v5.patch,
> OOZIE-1398-v7.patch, OOZIE-1398-v8.patch, OOZIE-1398-v8.patch
>
>
> When the number of concurrent submissions on Oozie increased to 100-200 per
> minute, it was not able to scale and we hit Oracle issues as there were lot
> of CLOB columns and DB became a bottle neck.
--
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
