[
https://issues.apache.org/jira/browse/PHOENIX-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127685#comment-14127685
]
James Taylor commented on PHOENIX-1239:
---------------------------------------
Ah, yes, I agree. The intent was to move everything from the HAVING to the
WHERE when possible (ANDed expression with no aggregate functions). My theory
is that this will outperform doing it client side, post aggregation but be
semantically equivalent. Do you think that's the case?
> IN clause (and some others) cannot get moved from HAVING clause to WHERE
> clause when qualified
> ----------------------------------------------------------------------------------------------
>
> Key: PHOENIX-1239
> URL: https://issues.apache.org/jira/browse/PHOENIX-1239
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0, 4.0.0, 5.0.0
> Reporter: Maryann Xue
> Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> {code}
> @Test
> public void testInListHavingToWhere() throws SQLException {
> String query = "select count(1) from atable group by a_string having
> a_string in ('foo', 'bar')";
> List<Object> binds = Collections.emptyList();
> Expressions expressions = compileStatement(query,binds);
> Expression w = TestUtil.in(A_STRING,"foo","bar");
> assertEquals(w, expressions.whereClause);
> assertNull(expressions.havingClause);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
