[
https://issues.apache.org/jira/browse/FLINK-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814435#comment-15814435
]
ramkrishna.s.vasudevan commented on FLINK-2168:
-----------------------------------------------
The timing was perfect. I was reading thro some more examples here in Table
APIs and was about to ping here.
bq.Calcite requires a relational schema. So we cannot support flexible schema.
Ok. For now we can assume the HBase table to have a fixed schema - say read
from a table that was loaded using a flat file (like CSV).
bq.We need unique field names. The user could explicitly specify how fields are
named.
Ok. Suppose we say
{code}
select * from table where 'col' = 10
{code}
So we need to implement the way this SQL is going to be implemented. Something
like what Apache Phoenix-Calcite integration does? Calcite can take care of the
grammer parsing but we need to convert what Calcite model gives us to actual
queries on hbase and in this case include some filters etc. So this JIRA will
be doing that big stuff also?
And coming to the data type - say the user wants the table 'col' to be integer
so once the data is written to this col we would convert the int to an byte[]
and store it. So on retrieval we should use the exact serde format that Flink
is aware of right?
> 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)
