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 2026/03/02 18:19:00 UTC
[jira] [Commented] (IMPALA-14793) Replace row regex with aggregation tests
[ https://issues.apache.org/jira/browse/IMPALA-14793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18062233#comment-18062233 ]
ASF subversion and git services commented on IMPALA-14793:
----------------------------------------------------------
Commit 90389331a09f3d27dffa1566506b56bb930afa71 in impala's branch refs/heads/master from Surya Hebbar
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=90389331a ]
IMPALA-14793: Replace row regex with aggregation tests
In the end-to-end python tests, there are many 'row_regex' searches
that can instead be treated as 'aggregation()' tests.
Rewriting these tests as aggregations can make the syntax easier,
while providing compatibility for both the traditional profile
and the new aggregated profile.
In many cases this results in better efficiency as the regex pattern to
search for is less complex than the original.
This is a split change associated with IMPALA-9846, in order to enable
the aggegated profile.
This reduces the number of lines from the large change IMPALA-9846
by a little, in order to aid the reviewer.
Change-Id: Ied342a3b89eb922137f0c1a7d3b2978b813de381
Reviewed-on: http://gerrit.cloudera.org:8080/24058
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> Replace row regex with aggregation tests
> ----------------------------------------
>
> Key: IMPALA-14793
> URL: https://issues.apache.org/jira/browse/IMPALA-14793
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Surya Hebbar
> Assignee: Surya Hebbar
> Priority: Major
>
> There are many row_regex searches that can instead be treated as aggregations to make the syntax easier and aggregations can provide better compatibility for both the traditional profile and the new aggregated profile. Also, they can result in better efficiency in certain cases.
> This is a split change associated with [IMPALA-9846|http://issues.apache.org/jira/browse/IMPALA-9846] to enable the aggegated profile.
> It is in order reduce the load from the large change, in order to make it a little easier to review.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org