[
https://issues.apache.org/jira/browse/SQOOP-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254859#comment-14254859
]
Veena Basavaraj commented on SQOOP-1875:
----------------------------------------
[~abec] the patch does not change the limit, I have fixed the code to not throw
an exception when the exception trace reaches more than 750. i have added unit
tests that verifies that the code now works as expected.
> Rename the SQ_SUBMISSION fields to reflect MSubmission changes and add tests
> for the max limit handling for submission fields
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: SQOOP-1875
> URL: https://issues.apache.org/jira/browse/SQOOP-1875
> Project: Sqoop
> Issue Type: Bug
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
> Attachments: SQOOP-1875-v1.patch, SQOOP-1875-v2.patch,
> SQOOP-1875.patch
>
>
> Rename the
> * | SQS_EXCEPTION: VARCHAR(150) |
> * | SQS_EXCEPTION_TRACE: VARCHAR(750) |
> to ERROR_SUMMARY and ERROR_DETAILS
> See SQOOP-1839 for more details on why generic names were chosen
> - make sure add the upgrade code as well.
> original commit that increased to 750!
> http://mail-archives.apache.org/mod_mbox/sqoop-commits/201211.mbox/%[email protected]%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
