[
https://issues.apache.org/jira/browse/CALCITE-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359322#comment-14359322
]
Julian Hyde commented on CALCITE-606:
-------------------------------------
Re 1. Yes. Because collation is a trait Calcite can deduce the same thing via
another path.
Re 2. My patch is close to minimal. If specify getStatistic but if you don't
use EnumerableTableScan.create, or if you don't override RelOptTable.unwrap, it
will not be able to deduce collations for the table and therefore will still
need the sort.
[~pipfiddle] Let me know ASAP whether this patch meets your needs. It is the
only thing preventing me from moving to a release vote.
> Fix Trait Propagation and add test case
> ---------------------------------------
>
> Key: CALCITE-606
> URL: https://issues.apache.org/jira/browse/CALCITE-606
> Project: Calcite
> Issue Type: Bug
> Reporter: Jacques Nadeau
> Assignee: Jacques Nadeau
> Fix For: next
>
>
> Per my email to the dev list, it seems like we need to have a Trait
> propagation test case. Some things also seem broken. Dev list email:
> http://mail-archives.apache.org/mod_mbox/incubator-calcite-dev/201503.mbox/browser
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
