You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/10/27 22:40:01 UTC
[jira] [Updated] (FLINK-21782) Lookup Table based on rowkey ranges
[ 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 stale-minor (was: auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)