[
https://issues.apache.org/jira/browse/LENS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274844#comment-14274844
]
Rajat Khandelwal commented on LENS-198:
---------------------------------------
suppose events come as late as 10 days and on an hourly basis. Then a partition
of pt can have upto 240 sub partitions of et. If the contents of those
partitions are not very large then the design decision might be to not
partition on et at all. That's a generic enough case and should be supported.
> 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
>
> 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)
