[
https://issues.apache.org/jira/browse/FLINK-21782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21782:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Lookup Table based on rowkey ranges
> -----------------------------------
>
> Key: FLINK-21782
> URL: https://issues.apache.org/jira/browse/FLINK-21782
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / HBase, Table SQL / Ecosystem
> Reporter: Felipe Lolas
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> Hi,
> Currently in a HBase table we model the data for a fast prefix filter scan,
> would be nice that we can use a lookup join as:
>
> {code:java}
> SELECT
> *
> FROM
> tbl
> LEFT JOIN
> hbaseTbl
> ON
> hbaseTbl.rowkey between tbl.field1 AND tbl.field2{code}
> In HBase we can traduce that as a RANGE SCAN operator with startRow =
> tbl.field1 and endRow = tbl.field2
> Maybe too (same as Apache phoenix behaviour)
>
> {code:java}
> SELECT
> *
> FROM
> tbl
> LEFT JOIN
> hbaseTbl
> ON
> hbaseTbl.rowkey LIKE tbl.field1 || '%'{code}
>
> traduced as RANGE SCAN with startRow=tbl.field1 - 1 (replacing the last
> character with lexicographical order -1) and endRow=tbl.field1 or simply a
> RowPrefixFilter (does the same)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
