[ https://issues.apache.org/jira/browse/FLINK-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828370#comment-15828370 ]
Fabian Hueske commented on FLINK-5554: -------------------------------------- The Table API uses Calcite to translate queries into executable plans. So this syntax would need to be understood by Calcite. Calcite uses a relational data model, so I am not sure how well this integrates with HBase's column family model. I would also be a bit hesitant to add data source specific features into the API which should work well with any other data source. What should work straightforward is to have a TableSource which maps the schema of an HBase table into a relational schema. > Add sql operator to table api for getting columns from HBase > ------------------------------------------------------------ > > Key: FLINK-5554 > URL: https://issues.apache.org/jira/browse/FLINK-5554 > Project: Flink > Issue Type: Improvement > Components: Table API & SQL > Reporter: Anton Solovev > > example of select query > {code} > table.select("f1:q1, f1:q2, f1:q3"); > {code} > or/and > {code} > table.select('f1:'q1, 'f1:'q2, 'f1:'q3); > {code} > let's discuss how to provide better api for selecting from HBase -- This message was sent by Atlassian JIRA (v6.3.4#6332)