@Julian,

Your comment makes sense to me. I put a short doc describing the
expected behavior for this feature. The doc link is put in
CALCITE-1150. Please take a look.


Jinfeng


On Wed, Apr 20, 2016 at 1:06 PM, Julian Hyde (JIRA) <[email protected]> wrote:
>
>     [ 
> https://issues.apache.org/jira/browse/CALCITE-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250601#comment-15250601
>  ]
>
> Julian Hyde commented on CALCITE-1150:
> --------------------------------------
>
> This feature will be useful, and as I have said to [~jnadeau] would fit well 
> within Calcite, but it’s a bit shapeless to me right now. I would like to see 
> some validator tests (any maybe one or two sql-to-rel converter tests) so I 
> get a feel for how it would work. When you have some tests can you post a 
> link to the github branch? I don’t think you should charge ahead with the 
> implementation because I might not agree with the specification (i.e. the 
> test cases).
>
>> Create the a new DynamicRecordType, avoiding star expansion when working 
>> with this type
>> ---------------------------------------------------------------------------------------
>>
>>                 Key: CALCITE-1150
>>                 URL: https://issues.apache.org/jira/browse/CALCITE-1150
>>             Project: Calcite
>>          Issue Type: Improvement
>>            Reporter: Jacques Nadeau
>>            Assignee: Julian Hyde
>>
>> DynamicRecordType can be used to leverage user-provided field implications 
>> to avoid schema analysis until execution.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)

Reply via email to