[jira] [Updated] (OOZIE-809) MySQL TEXT columns should be MEDIUMTEXT

["Robert Kanter (JIRA)" <ji...@apache.org>]

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

Robert Kanter updated OOZIE-809:
--------------------------------

    Attachment: OOZIE-809.patch

I added a "mysql_mediumtext" argument to the upgrade subcommand of the db tool.  When used, it will upgrade the database to use MEDIUMTEXT in all columns that use TEXT.  It will also add a flag "mysql.mediumtxt" to the OOZIE_SYS table to denote that we've done this upgrade.  If you create a new database or upgrade from Oozie 2.x, it will always use MEDIUMTEXT instead of TEXT; the mysql_mediumtext argument really only matters if you want to use MEDIUMTEXT on an already upgraded database.  This also only affects MySQL databases, not the other kinds.  

There are no tests for the db tool, but I manually verified the following situations:
{code}
- Create MySQL DB
	- Should work; have MEDIUMTEXT
- Upgrade MySQL DB from existing 3.x DB with MEDIUMTEXT and without mysql_mediumtext argument
	- Should fail; print already upgraded error message
- Upgrade MySQL DB from existing 3.x DB with MEDIUMTEXT and with mysql_mediumtext argument
	- Should fail; print already upgraded error message

- Upgrade MySQL DB from existing 3.x DB without MEDIUMTEXT and without mysql_mediumtext argument
	- Should fail; print already upgraded error message
- Upgrade MySQL DB from existing 3.x DB without MEDIUMTEXT and with mysql_mediumtext argument
	- Should work; have MEDIUMTEXT

- Create non-MySQL DB
	- Should work; not have MEDIUMTEXT
- Upgrade non-MySQL DB from existing 3.x DB without mysql_mediumtext argument
	- Should fail; print already upgraded error message
- Upgrade non-MySQL DB from existing 3.x DB with mysql_mediumtext argument
	- Should fail; print wrong DB vendor error message

- Upgrade MySQL DB from existing 2.x DB without mysql_mediumtext argument
	- Should work; have MEDIUMTEXT
- Upgrade MySQL DB from existing 2.x DB with mysql_mediumtext argument
	- Should work; have MEDIUMTEXT
{code}
                
> MySQL TEXT columns should be MEDIUMTEXT
> ---------------------------------------
>
>                 Key: OOZIE-809
>                 URL: https://issues.apache.org/jira/browse/OOZIE-809
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Shwetha G S
>            Assignee: Robert Kanter
>         Attachments: OOZIE-809.patch
>
>
> When working with large number of inputs and outputs, there is data truncation error in the following fields - COORD_ACTIONS.action_xml, COORD_ACTIONS.missing_dependencies, COORD_ACTIONS.run_conf, WF_JOBS.conf.
> In general, all TEXT fields should be changed to MEDIUMTEXT in MySQL

--
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