[
https://issues.apache.org/jira/browse/OOZIE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694557#comment-13694557
]
Virag Kothari commented on OOZIE-1398:
--------------------------------------
Good point. But shouldn't be a problem for now as this column will be reverted
back from varchar to clob due to a recent issue we faced (OOZIE-1436)
As <capture-output> should only be used for control data, one thing that can
be done is to make the code override the settings of the data length property
defined in oozie-site if greater than some reasonable value, lets say 4k. In
that case when converting to varchar(4000) shoudn't be an issue. But probably
if we are compressing this columns, then we dont even need to do this.
> [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
