[jira] [Commented] (FLINK-7179) ProjectableTableSource interface doesn't compatible with BoundedOutOfOrdernessTimestampExtractor

["Fabian Hueske (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087056#comment-16087056 ] 

Fabian Hueske commented on FLINK-7179:
--------------------------------------

Can you describe the issue in more detail?

The {{ProjectableTableSource}} receives the fields that it needs to emit. 
A {{TableSource}} knows from which field the timestamps must be extracted can read this field in addition to the selected fields.
Then it can apply the apply the {{TimestampExtractor}} and also possible remove the timestamp field if it is not requested by the {{ProjectableTableSource}}.

This is a bit cumbersome, but it should be possible. 
IMO, it makes sense to think about how this could be improved.



> ProjectableTableSource interface doesn't compatible with BoundedOutOfOrdernessTimestampExtractor
> ------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-7179
>                 URL: https://issues.apache.org/jira/browse/FLINK-7179
>             Project: Flink
>          Issue Type: Bug
>          Components: Table API & SQL
>    Affects Versions: 1.3.1
>            Reporter: Zhenqiu Huang
>
> In the implementation of window of stream sql, BoundedOutOfOrdernessTimestampExtractor is designed to extract row time from each row. It assumes the ts field is in the data stream by default. On the other hand, ProjectableTableSource is designed to help projection push down. If there is no row time related field in a query, the extractor can't function well. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)