You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Shwetha G S (Created) (JIRA)" <ji...@apache.org> on 2012/04/11 11:42:44 UTC

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

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


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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446512#comment-13446512 ] 

Hadoop QA commented on OOZIE-809:
---------------------------------

Testing JIRA OOZIE-809

Cleaning local svn workspace

{code}
----------------------------

+1 PATCH_APPLIES
   CLEAN cleaned target directories
-1 RAW_PATCH_ANALYSIS
    +1 the patch does not introduce any @author tags
    +1 the patch does not introduce any tabs
    +1 the patch does not introduce any trailing spaces
    +1 the patch does not introduce any line longer than 132
    -1 the patch does not add/modify any testcase
+1 RAT
    +1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
    +1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
    +1 HEAD compiles
    +1 patch compiles
    +1 the patch does not seem to introduce new javac warnings
-1 BACKWARDS_COMPATIBILITY
    +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
    -1 the patch modifies 1 JPA file(s), persistence.xml or *-orm.xml
+1 TESTS
   Tests run: 904
   Tests failures: 1
   Tests errors: 0
+1 DISTRO
    +1 distro tarball builds with the patch 

----------------------------
{code}

The full output of the test-patch run is available at

   https://builds.apache.org/job/oozie-trunk-precommit-build/78/
                
> 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

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

Posted by "Shwetha G S (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OOZIE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shwetha G S reassigned OOZIE-809:
---------------------------------

    Assignee: Shwetha G S
    
> 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: Shwetha G S
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449913#comment-13449913 ] 

Alejandro Abdelnur commented on OOZIE-809:
------------------------------------------

+1. The schema change is OK because it does not break DBs created with 3.2 if not done.
                
> 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

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

Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276843#comment-13276843 ] 

Alejandro Abdelnur commented on OOZIE-809:
------------------------------------------

As mentioned in the review, the code in the patch is dead code.

Still, I've seen this as an issue in some deployments where config size goes beyond 64k (we are storing XML, so lot of padding there).

We should look at how to configure OpenJPA to use MEDIUMTEXT for @Lob fields for MySQL (and the corresponding large text container types for Oracle, Derby, Postgres).
                
> 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: Shwetha G S
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251472#comment-13251472 ] 

jiraposter@reviews.apache.org commented on OOZIE-809:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4697/#review6839
-----------------------------------------------------------


Swetha,

The Schema class is dead code from Oozie 1, Oozie 2 & 3 use OpenJPA for DB access. So this change may have to be done in Oozie JPA configuration for mysql.

Also, we'll have to see verify how this change affects the ooziedb migration command. 

thxs


- Alejandro


On 2012-04-11 09:45:02, shwethags wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/4697/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2012-04-11 09:45:02)
bq.  
bq.  
bq.  Review request for oozie.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  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.
bq.  
bq.  In general, all TEXT fields should be changed to MEDIUMTEXT in MySQL
bq.  
bq.  
bq.  This addresses bug OOZIE-809.
bq.      https://issues.apache.org/jira/browse/OOZIE-809
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    trunk/core/src/main/java/org/apache/oozie/util/db/Schema.java 1324665 
bq.  
bq.  Diff: https://reviews.apache.org/r/4697/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  shwethags
bq.  
bq.


                
> 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
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251437#comment-13251437 ] 

jiraposter@reviews.apache.org commented on OOZIE-809:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4697/
-----------------------------------------------------------

Review request for oozie.


Summary
-------

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 addresses bug OOZIE-809.
    https://issues.apache.org/jira/browse/OOZIE-809


Diffs
-----

  trunk/core/src/main/java/org/apache/oozie/util/db/Schema.java 1324665 

Diff: https://reviews.apache.org/r/4697/diff


Testing
-------


Thanks,

shwethags


                
> 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
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450211#comment-13450211 ] 

Alejandro Abdelnur commented on OOZIE-809:
------------------------------------------

+1
                
> 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
>             Fix For: trunk
>
>         Attachments: OOZIE-809.patch, 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

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

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450190#comment-13450190 ] 

Hadoop QA commented on OOZIE-809:
---------------------------------

Testing JIRA OOZIE-809

Cleaning local svn workspace

{code}
----------------------------

+1 PATCH_APPLIES
   CLEAN cleaned target directories
-1 RAW_PATCH_ANALYSIS
    +1 the patch does not introduce any @author tags
    +1 the patch does not introduce any tabs
    +1 the patch does not introduce any trailing spaces
    +1 the patch does not introduce any line longer than 132
    -1 the patch does not add/modify any testcase
+1 RAT
    +1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
    +1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
    +1 HEAD compiles
    +1 patch compiles
    +1 the patch does not seem to introduce new javac warnings
-1 BACKWARDS_COMPATIBILITY
    +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
    -1 the patch modifies 1 JPA file(s), persistence.xml or *-orm.xml
+1 TESTS
   Tests run: 908
   Tests failures: 0
   Tests errors: 0
+1 DISTRO
    +1 distro tarball builds with the patch 

----------------------------
{code}

The full output of the test-patch run is available at

   https://builds.apache.org/job/oozie-trunk-precommit-build/87/
                
> 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, 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

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

Posted by "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

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

Posted by "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

New patch changes the CLI argument to "mysqlmediumtext" and has a minor update to the help text
                
> 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, 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

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

Posted by "Robert Kanter (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449926#comment-13449926 ] 

Robert Kanter commented on OOZIE-809:
-------------------------------------

We can't do mysql-mediumtext because it doesn't allow options/arguments with a "-" in them.  
                
> 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

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

Posted by "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 reassigned OOZIE-809:
-----------------------------------

    Assignee: Robert Kanter  (was: Shwetha G S)
    
> 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
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449916#comment-13449916 ] 

Alejandro Abdelnur commented on OOZIE-809:
------------------------------------------

Robert, one minor NIT (mysql_mediumtext should be mysql-mediumtext).
                
> 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