[ 
https://issues.apache.org/jira/browse/IMPALA-13901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17984983#comment-17984983
 ] 

ASF subversion and git services commented on IMPALA-13901:
----------------------------------------------------------

Commit 060432595886bc9660cdea1a7c0c615f24f44017 in impala's branch 
refs/heads/master from Joe McDonnell
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=060432595 ]

IMPALA-13901: Make histogram/sample/group_concat ineligible for tuple caching

"histogram" and "sample" rely on the same code as "appx_median"
and incorporate randomness. "group_concat" is entirely dependent
on the order of inputs. This expands tuple caching's list of
ineligible functions to include these variable aggregate functions.

Testing:
 - Added test cases to TupleCacheTest for these functions

Change-Id: Ibb017dd4297a3bb219ffed2bd9abc94e6c5b2605
Reviewed-on: http://gerrit.cloudera.org:8080/22668
Reviewed-by: Michael Smith <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Yida Wu <[email protected]>


> Make "histogram","sample", and "group_concat" ineligible for tuple caching
> --------------------------------------------------------------------------
>
>                 Key: IMPALA-13901
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13901
>             Project: IMPALA
>          Issue Type: Task
>          Components: Frontend
>    Affects Versions: Impala 5.0.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Major
>
> "histogram" and "sample" use the same infrastructure as "appx_median", which 
> includes randomness. These functions should be marked ineligible for tuple 
> caching. This came up in some test cases when running with tuple cache 
> verification.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to