[
https://issues.apache.org/jira/browse/CALCITE-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184964#comment-17184964
]
Julian Hyde commented on CALCITE-4193:
--------------------------------------
{quote}Will it work if hide such details under
EnumerableExternalSort.current(), EnumerableExternalSort.next(), etc.?
{quote}
The API will work. But it's not what the architecture was intended for, so the
implementation will have problems (bugs, performance issues).
{quote}In this case, Calcite does not care about how serialize and deserialize
values, etc. is done.
{quote}
Calcite does not know how to serialize values. So this operator will not know
either. The values may not even be serializable.
> Implement new sort operator: EnumerableExternalSort
> ---------------------------------------------------
>
> Key: CALCITE-4193
> URL: https://issues.apache.org/jira/browse/CALCITE-4193
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Ruben Q L
> Priority: Major
>
> Sometimes we need to sort a big volume of data which does not fit into
> memory. In this situation EnumerableSort will cause an OutOfMemoryError.
> The solution for such a scenario will be using a different sorting algorithm:
> [External Sort|https://en.wikipedia.org/wiki/External_sorting].
> The goal of the current ticket is to implement a new operator
> (EnumerableExternalSort) to provide this feature.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
