[
https://issues.apache.org/jira/browse/FLINK-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811535#comment-15811535
]
ramkrishna.s.vasudevan commented on FLINK-2168:
-----------------------------------------------
Thanks [~fhueske].
I was going thro the related JIRAs. I was just following how CSVTableSource
works here.
Initial questions
- Should we see the HBase tables as NOSQL table or like a normal table with a
proper schema which defines the set of columns per row?
- In HBase the columns can have same name but may come under different column
families. So how we bring that abstracted view?
- Next is that, we do scan of an hbase table and the result that we get is in
the form of bytes. Where can we do the type conversion to String, double, long
etc? Or may be that is not needed for now? Or may be calcite is of help here?
Sorry if my questions are naive here - after some discussion I think we can
discuss on the design part.
> 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)
