[
https://issues.apache.org/jira/browse/CALCITE-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rui Wang updated CALCITE-4176:
------------------------------
Description:
In [1], people mentioned key descriptor might not be required for use cases in
SESSION table function. For example, the SESSION table function can directly be
applied on a data from a website. Technically there is still a key, but just
all data have the same website key.
There are three options to make key descriptor "optional"
1) make key descriptor optional.
2) accept empty descriptor.
3) descriptor becomes nullable.
I am planning to try 1) first.
[1]:
https://issues.apache.org/jira/browse/CALCITE-3780?focusedCommentId=17166086&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17166086
> Key descriptor can be optional in SESSION table function
> --------------------------------------------------------
>
> Key: CALCITE-4176
> URL: https://issues.apache.org/jira/browse/CALCITE-4176
> Project: Calcite
> Issue Type: Sub-task
> Reporter: Rui Wang
> Assignee: Rui Wang
> Priority: Major
>
> In [1], people mentioned key descriptor might not be required for use cases
> in SESSION table function. For example, the SESSION table function can
> directly be applied on a data from a website. Technically there is still a
> key, but just all data have the same website key.
> There are three options to make key descriptor "optional"
> 1) make key descriptor optional.
> 2) accept empty descriptor.
> 3) descriptor becomes nullable.
> I am planning to try 1) first.
> [1]:
> https://issues.apache.org/jira/browse/CALCITE-3780?focusedCommentId=17166086&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17166086
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
