ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myroslav Papirkovskyy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-4237) Allow unlimited size for request_body of the RequestSchedule entity
Date Thu, 09 Jan 2014 18:25:05 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866879#comment-13866879
] 

Myroslav Papirkovskyy commented on AMBARI-4237:
-----------------------------------------------

I think we can create additional getter and setter for request body in entity to make work
with it easier and reduce amount of checks. Other looks good.

> Allow unlimited size for request_body of the RequestSchedule entity
> -------------------------------------------------------------------
>
>                 Key: AMBARI-4237
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4237
>             Project: Ambari
>          Issue Type: Task
>          Components: controller
>    Affects Versions: 1.5.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-4237.patch
>
>
> Currently the RequestSchedule entity stores the request body as a varchar with max size
of 4000 bytes. This is because of Oracle's restriction on the column size.
> *Objectives*:
> - Change request_body datatype to blob.
> - Allow for conversion to String and back
> - Modify the RequestSchedule ResourceProvider to not send request_body on every get call.
(only send if requesting specific resource)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message