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

ASF GitHub Bot commented on TRAFODION-2819:
-------------------------------------------

GitHub user DaveBirdsall opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/1312

    [TRAFODION-2819] Fix 4247 error on drop table when certain CQDs are present

    When CQD TRAF_MAX_CHARACTER_COL_LENGTH is set to a value lower than '500', 
then DROP TABLE will fail when it tries to do a DELETE under the covers on the 
SB_HISTOGRAMS table. The latter fails with error 4247, raised in 
CmpSeabaseDDL::getColInfo (sqlcomp/CmpSeabaseDDLcommon.cpp).
    
    The fix is to change CmpSeabaseDDL::getColInfo to exempt metadata, 
histogram and repository tables from the maximum column length check.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/DaveBirdsall/incubator-trafodion Trafodion2819

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/1312.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1312
    
----
commit d96f3c7c136eab380acbd3f481ff1f738e16306d
Author: Dave Birdsall <dbirds...@apache.org>
Date:   2017-11-27T21:35:35Z

    [TRAFODION-2819] Fix 4247 error on drop table when certain CQDs are present

----


> Drop table fails with error 4247 when certain CQDs are set
> ----------------------------------------------------------
>
>                 Key: TRAFODION-2819
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2819
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: sql-cmp
>    Affects Versions: 2.3-incubating
>            Reporter: David Wayne Birdsall
>            Assignee: David Wayne Birdsall
>
> Drop table fails with error 4247 in the following scenario:
> >>cqd HIVE_MAX_STRING_LENGTH_IN_BYTES '200';
> --- SQL operation complete.
> >>cqd TRAF_MAX_CHARACTER_COL_LENGTH '200';
> --- SQL operation complete.
> >>
> >>create table my_traf_line (
> +>l_orderkey int not null not droppable,
> +>l_partkey int not null not droppable,
> +>l_suppkey int not null not droppable,
> +>l_linenumber int not null not droppable,
> +>l_quantity numeric(12,2) not null not droppable,
> +>l_extendedprice numeric(12,2) not null not droppable,
> +>l_discount numeric(12,2) not null not droppable,
> +>l_tax numeric(12,2) not null not droppable,
> +>l_returnflag char(1) not null not droppable,
> +>l_linestatus char(1) not null not droppable,
> +>l_shipdate date not null not droppable,
> +>l_commitdate date not null not droppable,
> +>l_receiptdate date not null not droppable,
> +>l_shipinstruct char(25) not null not droppable,
> +>l_shipmode char(10) not null not droppable,
> +>l_comment varchar(44) not null not droppable,
> +>primary key (l_shipdate asc, l_orderkey asc, l_linenumber asc) not 
> droppable)
> +>salt using 8 partitions;
> --- SQL operation complete.
> >>
> >>drop table my_traf_line cascade;
> *** ERROR[4247] Specified size in bytes (500) exceeds the maximum size 
> allowed (200) for column LOW_VALUE.
> *** ERROR[4082] Object TRAFODION.SCH.SB_HISTOGRAMS does not exist or is 
> inaccessible.
> *** ERROR[8822] The statement was not prepared.
> --- SQL operation failed with errors.
> >>



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to