[
https://issues.apache.org/jira/browse/FLINK-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814349#comment-15814349
]
Fabian Hueske commented on FLINK-2168:
--------------------------------------
Hi [~ram_krish],
* Calcite requires a relational schema. So we cannot support flexible schema.
Nested data is supported, i.e., a field can be of a complex type such as a POJO
and Calcite/Flink can access the fields of the POJO.
* We need unique field names. The user could explicitly specify how fields are
named. We can also use HBase's column names by default and throw an exception
if we observe a name collision and request explicit names.
* The HBase table source should return proper types (primitives or objects),
otherwise it won't be usable. The user should tell the table source which types
are stored in the columns and how they can be deserialized.
> Add HBaseTableSource
> --------------------
>
> Key: FLINK-2168
> URL: https://issues.apache.org/jira/browse/FLINK-2168
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Affects Versions: 0.9
> Reporter: Fabian Hueske
> Assignee: ramkrishna.s.vasudevan
> Priority: Minor
> Labels: starter
>
> Add a {{HBaseTableSource}} to read data from a HBase table. The
> {{HBaseTableSource}} should implement the {{ProjectableTableSource}}
> (FLINK-3848) and {{FilterableTableSource}} (FLINK-3849) interfaces.
> The implementation can be based on Flink's {{TableInputFormat}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
