You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "David Wayne Birdsall (JIRA)" <ji...@apache.org> on 2018/07/09 21:40:00 UTC

[jira] [Issue Comment Deleted] (TRAFODION-3128) INTERVAL SECOND(m,n) in multi-column key results in 6003 warnings

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

David Wayne Birdsall updated TRAFODION-3128:
--------------------------------------------
    Comment: was deleted

(was: This problem was fixed by [https://github.com/apache/trafodion/pull/1630|https://github.com/apache/trafodion/pull/1630.] . (I'm not sure why the pull request wasn't automatically logged to this JIRA.))

> INTERVAL SECOND(m,n) in multi-column key results in 6003 warnings
> -----------------------------------------------------------------
>
>                 Key: TRAFODION-3128
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-3128
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: sql-cmp
>    Affects Versions: 2.3
>            Reporter: David Wayne Birdsall
>            Assignee: David Wayne Birdsall
>            Priority: Major
>             Fix For: 2.3
>
>
> The following script reproduces the problem:
> drop table if exists tproblem;
> create table tproblem (a interval second(2,6) not null, b int not null, c int,
>  primary key (a,b));
> insert into tproblem values (interval '12.345678' second(2,6),7,7),
>  (interval '23.456789' second(2,6),8,8);
> update statistics for table tproblem on every column;
> -- give RMS a little time to invalidate cached stats for tproblem
> sh sleep 20;
> select * from tproblem where b = 8;
> When run, the select statement gets a 6003 warning:
> >>select * from tproblem where b = 8;
> *** WARNING[6003] The metadata table HISTOGRAM_INTERVALS contains invalid boundary value (INTERVAL '12.345678' SECOND(2, 6),7) for column TRAFODION.SCH.TPROBLEM.A. If you have manually modified the metadata table, then you should undo your changes using the CLEAR option in UPDATE STATISTICS and regenerate the statistics.
> A B C 
> ---------- ----------- -----------
> 23.456789 8 8
> --- 1 row(s) selected.
> >>
> The warning happens because EncodedValue::constructorFunction (optimizer/EncodedValue.cpp) is not handling the INTERVAL literal in the histogram intervals correctly.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)