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 "Michael Ho (JIRA)" <ji...@apache.org> on 2018/07/23 21:00:00 UTC
[jira] [Updated] (IMPALA-7338) Test coverage for codegen with CHAR
type
[ https://issues.apache.org/jira/browse/IMPALA-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Ho updated IMPALA-7338:
-------------------------------
Issue Type: Sub-task (was: Task)
Parent: IMPALA-3207
> Test coverage for codegen with CHAR type
> ----------------------------------------
>
> Key: IMPALA-7338
> URL: https://issues.apache.org/jira/browse/IMPALA-7338
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Affects Versions: Impala 3.0, Impala 2.12.0
> Reporter: Michael Ho
> Assignee: Bikramjeet Vig
> Priority: Major
> Labels: codegen
>
> Until IMPALA-3207 is fixed, we will disable codegen for operators if CHAR is involved. Our test coverage for these cases is not very comprehensive. For instance, we still hit cases such as IMPALA-7032, IMPALA-7288. This Jira aims to track the effort to boost the test coverage for these cases.
> Some ideas:
> * augment existing test cases to make sure we cover all built-in expressions which can take char type as argument or return type. This should help catch cases such as IMPALA-7032
> * exercise the bail out path in codegen functions (e.g. hash tables, exec nodes, expressions) by injecting faults in expression codegen functions to fail codegen. This should help catch cases such as IMPALA-7288.
> * Make sure our query generator will generate all possible combination of built-in expressions (with CHAR type) and all exec nodes which may codegen.
> cc'ing [~mikesbrown] for query generator idea
--
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