[
https://issues.apache.org/jira/browse/IMPALA-9294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154695#comment-17154695
]
ASF subversion and git services commented on IMPALA-9294:
---------------------------------------------------------
Commit 55099517b059eadb064674768488bfd3287f649a in impala's branch
refs/heads/master from wzhou-code
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=5509951 ]
IMPALA-9294: Support DATE for min-max runtime filter
Implemented Date min-max filter and applied it to Kudu as other
min-max runtime filters.
Added new test cases for Date min-max filters.
Testing:
Passed all core tests.
Change-Id: Ic2f6e2dc6949735d5f0fcf317361cc2969a5e82c
Reviewed-on: http://gerrit.cloudera.org:8080/16103
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Support DATE for min-max runtime filters
> ----------------------------------------
>
> Key: IMPALA-9294
> URL: https://issues.apache.org/jira/browse/IMPALA-9294
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 3.4.0
> Reporter: Vladimir Verjovkin
> Assignee: Wenzhe Zhou
> Priority: Critical
> Labels: kudu
>
> Since min-max runtime filters are only supported for Kudu, and since at the
> time they were implemented Kudu didn't support DATE, we didn't implement DATE
> min-max runtime filters.
> There's ongoing work to add support for DATE on Kudu (KUDU-2632). To start,
> min-max runtime filters will just be disabled for DATE targets, but we should
> extend MinMaxFilter to support it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
