You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Aman Raj (Jira)" <ji...@apache.org> on 2023/03/25 06:24:00 UTC

[jira] [Created] (HIVE-27174) Disable sysdb.q test

Aman Raj created HIVE-27174:
-------------------------------

             Summary: Disable sysdb.q test
                 Key: HIVE-27174
                 URL: https://issues.apache.org/jira/browse/HIVE-27174
             Project: Hive
          Issue Type: Sub-task
            Reporter: Aman Raj
            Assignee: Aman Raj


h3. What changes were proposed in this pull request?

Disabled sysdb.q test. The test is failing because of diff in BASIC_COLUMN_STATS json string.
Client Execution succeeded but contained differences (error code = 1) after executing sysdb.q
3803,3807c3803,3807
< COLUMN_STATS_ACCURATE org.apache.derby.impl.jdbc.EmbedClob@125b285b
< COLUMN_STATS_ACCURATE org.apache.derby.impl.jdbc.EmbedClob@471246f3
< COLUMN_STATS_ACCURATE org.apache.derby.impl.jdbc.EmbedClob@57c013
< COLUMN_STATS_ACCURATE org.apache.derby.impl.jdbc.EmbedClob@59f1d7ac
< COLUMN_STATS_ACCURATE org.apache.derby.impl.jdbc.EmbedClob@717777a0
—
{quote}COLUMN_STATS_ACCURATE \{"BASIC_STATS":"true","COLUMN_STATS":{"c_boolean":"true","c_float":"true","c_int":"true","key":"true","value":"true"}}
COLUMN_STATS_ACCURATE \{"BASIC_STATS":"true","COLUMN_STATS":{"c_boolean":"true","c_float":"true","c_int":"true","key":"true","value":"true"}}
COLUMN_STATS_ACCURATE \{"BASIC_STATS":"true","COLUMN_STATS":{"key":"true","value":"true"}}
COLUMN_STATS_ACCURATE \{"BASIC_STATS":"true","COLUMN_STATS":{"key":"true","value":"true"}}
COLUMN_STATS_ACCURATE {"BASIC_STATS":"true","COLUMN_STATS":
{quote}
h3. Why are the changes needed?

There is no issue in the test. The current code prints the COL_STATS as an Object instead of a json string. Not sure why is this case. Tried a lot of ways but seems like this is not fixable at the moment. So, disabling it for now. Note that, in Hive 3.1.3 release this test was disabled so there should not be any issue in disabling it here.

 

 

Created a followup ticket to fix this test that can be taken up later - 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)