You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/11/06 21:37:00 UTC
[jira] [Commented] (IMPALA-7809) test_concurrent_schema_change
incompatible with Kudu 1.9
[ https://issues.apache.org/jira/browse/IMPALA-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677321#comment-16677321 ]
ASF subversion and git services commented on IMPALA-7809:
---------------------------------------------------------
Commit 3792a749923f7490b239e451d6500f1e946821ff in impala's branch refs/heads/master from [~leto]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=3792a74 ]
IMPALA-7809: support Kudu 1.9 in test_concurrent_schema_change
This patch extends the match of allowable errors in
test_concurrent_schema_change to work with Kudu 1.9.
Testing: Local with a Kudu 1.9 minicluster environment.
Change-Id: I7fc24bb6a18aecc0cb726b8d66f0aeccf56bbb9b
Reviewed-on: http://gerrit.cloudera.org:8080/11882
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> test_concurrent_schema_change incompatible with Kudu 1.9
> --------------------------------------------------------
>
> Key: IMPALA-7809
> URL: https://issues.apache.org/jira/browse/IMPALA-7809
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 3.2.0
> Reporter: Michael Brown
> Assignee: Michael Brown
> Priority: Blocker
> Labels: broken-build
>
> With Kudu 1.9, test_concurrent_schema_change incompatible fails because the message format is slightly different.
> {noformat}
> query_test/test_kudu.py:442: in test_concurrent_schema_change assert "has fewer columns (1) than the SELECT / VALUES clause returns (2)" in msg \ E assert ('has fewer columns (1) than the SELECT / VALUES clause returns (2)' in 'ImpalaBeeswaxException:\n Query aborted:Kudu error(s) reported, first error: Invalid argument: Failed to write batch ...redacted.com:31201): Client provided column col1 INT64 NULLABLE not present in tablet (1 of 2 similar)\n\n' or "(type: TINYINT) is not compatible with column 'col1' (type: STRING)" in 'ImpalaBeeswaxException:\n Query aborted:Kudu error(s) reported, first error: Invalid argument: Failed to write batch ...redacted.com:31201): Client provided column col1 INT64 NULLABLE not present in tablet (1 of 2 similar)\n\n' or 'has fewer columns than expected.' in 'ImpalaBeeswaxException:\n Query aborted:Kudu error(s) reported, first error: Invalid argument: Failed to write batch ...redacted.com:31201): Client provided column col1 INT64 NULLABLE not present in tablet (1 of 2 similar)\n\n' or 'Column col1 has unexpected type.' in 'ImpalaBeeswaxException:\n Query aborted:Kudu error(s) reported, first error: Invalid argument: Failed to write batch ...redacted.com:31201): Client provided column col1 INT64 NULLABLE not present in tablet (1 of 2 similar)\n\n' or 'Client provided column col1[int64 NULLABLE] not present in tablet' in 'ImpalaBeeswaxException:\n Query aborted:Kudu error(s) reported, first error: Invalid argument: Failed to write batch ...redacted.com:31201): Client provided column col1 INT64 NULLABLE not present in tablet (1 of 2 similar)\n\n')
> Stacktrace
> query_test/test_kudu.py:442: in test_concurrent_schema_change
> assert "has fewer columns (1) than the SELECT / VALUES clause returns (2)" in msg \
> E assert ('has fewer columns (1) than the SELECT / VALUES clause returns (2)' in 'ImpalaBeeswaxException:\n Query aborted:Kudu error(s) reported, first error: Invalid argument: Failed to write batch ...redacted.com:31201): Client provided column col1 INT64 NULLABLE not present in tablet (1 of 2 similar)\n\n' or "(type: TINYINT) is not compatible with column 'col1' (type: STRING)" in 'ImpalaBeeswaxException:\n Query aborted:Kudu error(s) reported, first error: Invalid argument: Failed to write batch ...redacted.com:31201): Client provided column col1 INT64 NULLABLE not present in tablet (1 of 2 similar)\n\n' or 'has fewer columns than expected.' in 'ImpalaBeeswaxException:\n Query aborted:Kudu error(s) reported, first error: Invalid argument: Failed to write batch ...redacted.com:31201): Client provided column col1 INT64 NULLABLE not present in tablet (1 of 2 similar)\n\n' or 'Column col1 has unexpected type.' in 'ImpalaBeeswaxException:\n Query aborted:Kudu error(s) reported, first error: Invalid argument: Failed to write batch ...redacted.com:31201): Client provided column col1 INT64 NULLABLE not present in tablet (1 of 2 similar)\n\n' or 'Client provided column col1[int64 NULLABLE] not present in tablet' in 'ImpalaBeeswaxException:\n Query aborted:Kudu error(s) reported, first error: Invalid argument: Failed to write batch ...redacted.com:31201): Client provided column col1 INT64 NULLABLE not present in tablet (1 of 2 similar)\n\n')
> {noformat}
> We see that the message returned includes {{Client provided column col1 INT64 NULLABLE not present in tablet}} and the code is looking for:
> {noformat}
> 437 for error in insert_thread.errors:
> 438 msg = str(error)
> 439 # The first two are AnalysisExceptions, the next two come from KuduTableSink::Open()
> 440 # if the schema has changed since analysis, the last comes from the Kudu server if
> 441 # the schema changes between KuduTableSink::Open() and when the write ops are sent.
> 442 assert "has fewer columns (1) than the SELECT / VALUES clause returns (2)" in msg \
> 443 or "(type: TINYINT) is not compatible with column 'col1' (type: STRING)" in msg \
> 444 or "has fewer columns than expected." in msg \
> 445 or "Column col1 has unexpected type." in msg \
> 446 or "Client provided column col1[int64 NULLABLE] not present in tablet" in msg
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org