[ https://issues.apache.org/jira/browse/IMPALA-10248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216418#comment-17216418 ]
Quanlong Huang commented on IMPALA-10248: ----------------------------------------- IMPALA-10225 bumps the impyla version to 0.17a1 which contains [https://github.com/cloudera/impyla/pull/411] (Fix DATE, VARCHAR handling: #410). So now in the test, we should expect impyla to return a datetime.date instead of a string. > TestKuduOperations.test_column_storage_attributes on exhaustive tests > --------------------------------------------------------------------- > > Key: IMPALA-10248 > URL: https://issues.apache.org/jira/browse/IMPALA-10248 > Project: IMPALA > Issue Type: Bug > Reporter: Quanlong Huang > Assignee: Quanlong Huang > Priority: Blocker > > This is a reverse issue of IMPALA-9513. The failure is > {code:java} > query_test/test_kudu.py:472: in test_column_storage_attributes > assert cursor.fetchall() == \ > E assert [(0, True, 0, 0, 0, 0, ...)] == [(0, True, 0, 0, 0, 0, ...)] > E At index 0 diff: (0, True, 0, 0, 0, 0, 0.0, 0.0, '0', > datetime.datetime(2009, 1, 1, 0, 0), Decimal('0'), datetime.date(2010, 1, 1), > '') != (0, True, 0, 0, 0, 0, 0.0, 0.0, '0', datetime.datetime(2009, 1, 1, 0, > 0), 0, '2010-01-01', '') > E Use -v to get the full diff{code} > The difference to IMPALA-9513 is that it's expected to get a string > '2020-01-01' instead of the actual {{datetime.date(2010, 1, 1)}}. Maybe due > to the recent bumping of impyla version in IMPALA-10225. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org