flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ramkrish86 <...@git.apache.org>
Subject [GitHub] flink issue #3149: FLINK-2168 Add HBaseTableSource
Date Wed, 01 Feb 2017 05:57:15 GMT
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?



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message