[
https://issues.apache.org/jira/browse/HIVE-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780592#comment-13780592
]
Sergey Shelukhin commented on HIVE-4888:
----------------------------------------
it looks like derby is evaluating a cast before it filters the values by join,
or something like that.
All the values it should test via cast are numbers and can be cast if the
queries are issued for this specific set of values via separate queries, but in
filter form it doesn't work. Let me verify if it works in real databases, if it
does I will disable sql for this test, or do some workaround for derby.
> listPartitionsByFilter doesn't support lt/gt/lte/gte
> ----------------------------------------------------
>
> Key: HIVE-4888
> URL: https://issues.apache.org/jira/browse/HIVE-4888
> Project: Hive
> Issue Type: Improvement
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: D13101.1.patch, D13101.2.patch, HIVE-4888.00.patch,
> HIVE-4888.01.patch, HIVE-4888.on-top-of-4914.patch
>
>
> Filter pushdown could be improved. Based on my experiments there's no
> reasonable way to do it with DN 2.0, due to DN bug in substring and
> Collection.get(int) not being implemented.
> With version as low as 2.1 we can use values.get on partition to extract
> values to compare to. Type compatibility is an issue, but is easy for strings
> and integral values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
