You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@paimon.apache.org by "Aitozi (via GitHub)" <gi...@apache.org> on 2024/01/03 02:24:13 UTC

[I] [Bug] Lookup Join should respect the sequence.filed option of primary key table [incubator-paimon]

Aitozi opened a new issue, #2621:
URL: https://github.com/apache/incubator-paimon/issues/2621

   ### Search before asking
   
   - [X] I searched in the [issues](https://github.com/apache/incubator-paimon/issues) and found nothing similar.
   
   
   ### Paimon version
   
   0.6
   
   ### Compute Engine
   
   Flink
   
   ### Minimal reproduce step
   
   ```java
           sql(
                   "CREATE TABLE DIM_2 (i INT PRIMARY KEY NOT ENFORCED, j INT, k1 INT, k2 INT) WITH"
                           + " ('continuous.discovery-interval'='1 ms', 'sequence.field' = 'j')");
           sql("INSERT INTO DIM_2 VALUES (1, 11, 111, 1111), (2, 22, 222, 2222)");
   
           String query =
                   "SELECT T.i, D.j, D.k1, D.k2 FROM T LEFT JOIN DIM_2 for system_time as of T.proctime AS D ON T.i = D.i";
           BlockingIterator<Row, Row> iterator = BlockingIterator.of(sEnv.executeSql(query).collect());
   
           sql("INSERT INTO T VALUES (1), (2), (3)");
           List<Row> result = iterator.collect(3);
           assertThat(result)
                   .containsExactlyInAnyOrder(
                           Row.of(1, 11, 111, 1111),
                           Row.of(2, 22, 222, 2222),
                           Row.of(3, null, null, null));
   
           sql("INSERT INTO DIM_2 VALUES (2, 11, 444, 4444), (3, 33, 333, 3333)");
           Thread.sleep(2000); // wait refresh
           sql("INSERT INTO T VALUES (1), (2), (3), (4)");
           result = iterator.collect(4);
           assertThat(result)
                   .containsExactlyInAnyOrder(
                           Row.of(1, 11, 111, 1111),
                           Row.of(2, 22, 222, 2222), // not change
                           Row.of(3, 33, 333, 3333),
                           Row.of(4, null, null, null));
   
           iterator.close()
   ```
   
   when we refresh with data of old sequence, the date in rocksdb cache should not be refreshed, otherwise, the join result is unstable.
   
   ### What doesn't meet your expectations?
   
   .
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] I'm willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@paimon.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug] Lookup Join should respect the sequence.field option of primary key table [incubator-paimon]

Posted by "JingsongLi (via GitHub)" <gi...@apache.org>.
JingsongLi closed issue #2621: [Bug] Lookup Join should respect the sequence.field option of primary key table
URL: https://github.com/apache/incubator-paimon/issues/2621


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@paimon.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org