[
https://issues.apache.org/jira/browse/CALCITE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428210#comment-17428210
]
Viliam Durina commented on CALCITE-4337:
----------------------------------------
1. They say "may not be partitioned", but what they actually mean is what I
said, that is, each row is its own partition. The engine is also free to assign
partitions in any way; if each row is a partition, then it assigns each row
arbitrarily. I think there's no contradiction. My intention was to come up with
a generalized notion of partitioning that covers each option.
2. Copartitioning means that the tables are partitioned using the exact same
key. My idea was actually more general - it would be possible to execute a call
where partitioning keys of one argument are a prefix or partitioning keys of
another argument.
> Support PARTITION BY clause in table function call
> --------------------------------------------------
>
> Key: CALCITE-4337
> URL: https://issues.apache.org/jira/browse/CALCITE-4337
> Project: Calcite
> Issue Type: New Feature
> Components: core
> Affects Versions: 1.26.0
> Reporter: Danny Chen
> Assignee: Danny Chen
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2021-09-30-11-04-33-474.png,
> image-2021-09-30-11-05-12-400.png, image-2021-09-30-11-05-42-033.png,
> image-2021-10-13-20-19-55-855.png, image-2021-10-13-20-22-42-675.png,
> image-2021-10-13-20-23-26-890.png
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> An example from the SQL standard 2016 Polymorphic Table Functions:
> {code:sql}
> SELECT W.wstart, W.wend, OI.customer, SUM(OI.price)
> FROM TABLE(SESSION(
> data => TABLE(order_item) AS OI PARTITION BY customer,
> timecol => DESCRIPTOR(order_time),
> timeout => INTERVAL '10' MINUTE)) W
> GROUP BY 1, 2, 3
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
