[
https://issues.apache.org/jira/browse/FLINK-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657432#comment-15657432
]
Anton Solovev edited comment on FLINK-3848 at 11/14/16 9:13 AM:
----------------------------------------------------------------
I have a question about type info, it looks like one int calcite mail,
but I catch CodeGenException when checking predefinde table field types with
output from source
Flink cannot generate conversion because of row arity. We cannot reduce number
of table fields,
but we can create a new code generation
or let nulls come from csvInputFormt
any ideas?
was (Author: tonycox):
I have a question about type info, it looks like one int calcite mail,
but I catch CodeGenException when checking predefinde table field types with
output from source
Flink cannot generate conversion because of row arity. We cannot reduce number
of table fields,
but we can create a new code generation
or let nulls come from csvInputFormt ->
https://github.com/apache/flink/compare/master...tonycox:FLINK-3848
any ideas?
> Add ProjectableTableSource interface and translation rule
> ---------------------------------------------------------
>
> Key: FLINK-3848
> URL: https://issues.apache.org/jira/browse/FLINK-3848
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Reporter: Fabian Hueske
> Assignee: Anton Solovev
>
> Add a {{ProjectableTableSource}} interface for {{TableSource}} implementation
> that support projection push-down.
> The interface could look as follows
> {code}
> def trait ProjectableTableSource {
> def setProjection(fields: Array[String]): Unit
> }
> {code}
> In addition we need Calcite rules to push a projection into a TableScan that
> refers to a {{ProjectableTableSource}}. We might need to tweak the cost model
> as well to push the optimizer in the right direction.
> Moreover, the {{CsvTableSource}} could be extended to implement
> {{ProjectableTableSource}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
