tanjialiang created FLINK-35233:
-----------------------------------

             Summary: HBase lookup result is wrong when lookup cache is enabled
                 Key: FLINK-35233
                 URL: https://issues.apache.org/jira/browse/FLINK-35233
             Project: Flink
          Issue Type: Bug
          Components: Connectors / HBase
    Affects Versions: hbase-3.0.0
            Reporter: tanjialiang


HBase table
||rowkey||name||age||
|1|ben|18|
|2|ken|19|
|3|mark|20|

 
FlinkSQL lookup join with lookup cahce
{code:java}
CREATE TABLE dim_user (
  rowkey STRING,
  info ROW<name STRING, age STRING>,
  PRIMARY KEY (rowkey) NOT ENFORCED
) WITH (
  'connector' = 'hbase-2.2',
  'zookeeper.quorum' = 'localhost:2181',
  'zookeeper.znode.parent' = '/hbase',
  'table-name' = 'default:test',
  'lookup.cache' = 'PARTIAL',
  'lookup.partial-cache.max-rows' = '1000',
  'lookup.partial-cache.expire-after-write' = '1h'
);

CREATE VIEW user_click AS 
SELECT user_id, proctime() AS proc_time
FROM (
  VALUES('1'), ('2'), ('3'), ('1'), ('2')
) AS t (user_id);

SELECT 
    user_id, 
    info.name, 
    info.age
FROM user_click INNER JOIN dim_user
FOR SYSTEM_TIME AS OF user_click.proc_time
ON dim_user.rowkey = user_click.user_id;{code}
 
Expect Result
||rowkey||name||age||
|1|ben|18|
|2|ken|19|
|3|mark|20|
|1|ben|18|
|2|ken|19|

 

Actual Result
||rowkey||name||age||
|1|ben|18|
|2|ken|19|
|3|mark|20|
|1|mark|20|
|2|mark|20|

 
Wrong result when we lookup user_id 1 and 2 the second time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to