[
https://issues.apache.org/jira/browse/LENS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513941#comment-14513941
]
Rajat Khandelwal commented on LENS-198:
---------------------------------------
Things to watch out for:
* max covering resolver will need changes to incorporate covering range for the
queried part col only
* extra where clause if fallback part column is picked.
* give such storage tables lesser priority when finally forming the HQL.
* queries with multiple time_range_in clauses, where part cols can be same or
different.
> Allow timed dimensions of cube to be non-partitioned columns as well
> --------------------------------------------------------------------
>
> Key: LENS-198
> URL: https://issues.apache.org/jira/browse/LENS-198
> Project: Apache Lens
> Issue Type: Improvement
> Components: cube
> Reporter: Amareshwari Sriramadasu
> Assignee: Rajat Khandelwal
>
> Here is a use case:
> Say cube is having timed dimensions as it and et. If queries come on et and
> no storage partitioned on et, we fail the queries currently. But if there is
> notion of et=it plus or minus 10 and storage is partitioned on it, the
> timerange on et can be resolved to it partitions.
> And if et is direct column along with partition mapping, et filter also needs
> applied along with partition lookup for it.
> The requirement is to accept cube definition with such timed dimensions and
> resolve corresponding partitions in StorageTableResolver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
