[
https://issues.apache.org/jira/browse/FLINK-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848046#comment-15848046
]
ASF GitHub Bot commented on FLINK-2168:
---------------------------------------
Github user ramkrish86 commented on the issue:
https://github.com/apache/flink/pull/3149
To understand better
> We could make flat schema an optional mode or implement it as a separate
TableSource as well.
and this one
> This could be solved if we use a flat schema and encode the nesting as
columnFamily$column
Are you talking about using seperators for it? May be am not getting your
concern here. Ya I agree that nested schema is better API but if we go with
flat schema then maintaining the family to qualifier relation may not be easy.
As you said a seperate TableSource where we define such things would be better.
Regarding HBaseTableSchema I think that is better so that we could modify
that class for better serialization and deserialization by adding more logic
for different types of classes. Even when we go with flat schema I think this
type of class would help us to maintain the logic of family to qualifier
mapping?
> 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.15#6346)
