[
https://issues.apache.org/jira/browse/FLINK-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833042#comment-15833042
]
ASF GitHub Bot commented on FLINK-2168:
---------------------------------------
Github user wuchong commented on the issue:
https://github.com/apache/flink/pull/3149
Hi @fhueske ,
Regarding to the field type serialization, I think maybe we can provide
default deserialization for basic types (int,long,String...) if users do use
the `Bytes.toBytes(...)` to serialize the basic types. If not, users can ask
this field to return raw bytes in this way: `htableSchame.add("column_family",
"qualifier", byte[].class)` and then use an user defined scalar function to
deserialize the value.
regarding to the rowkeys, I agree with you. It would be great if we can set
scan range by WHERE clause. But FLINK-3849 (FilterableTableSource) is still a
pending PR, I would suggest to break this issue into two. 1. add
HBaseTableSource, provide access to HBase tables and support nested schema. 2.
extend HBaseTableSource to support FilterableTableSource.
> 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)
