Sasha Syrotenko
Sasha Syrotenko
In https://github.com/hazelcast/hazelcast/pull/21575 we introduced keyed watermark mechanism which helps to determine the watermark input origin. But, some processors like `SessionWindowP` and `SlidingWindowP` required additional tuning to fully support keyed watermarks....
Blocked by: #21170 Checklist: - [x] Labels (`Team:`, `Type:`, `Source:`, `Module:`) and Milestone set - [x] Label `Add to Release Notes` or `Not Release Notes content` set - [x] Request...
Recently, I notice that sometimes we have a final query plan which contains two physical `Calc` consequently, after the physical opt phase. This change open an optimization for such queries...
Now `countOrderingFunctions` just count all `IMPOSE_ORDER` in query, which is not correct. Consider such correct query will throw validation error. ``` SELECT * FROM TABLE(IMPOSE_ORDER(TABLE stream1, DESCRIPTOR(a), INTERVAL '0.001' SECOND))...
Got this test failure in [my PR](https://github.com/hazelcast/hazelcast/pull/22134#issuecomment-1238139461), and it's unrelated to PR changes. ``` [ERROR] KinesisIntegrationTest.restart_dynamicStream_graceful:359->restart_dynamicStream:397->assertMessages:580->AbstractKinesisTest.assertMessages:159->HazelcastTestSupport.assertTrueEventually:1338->HazelcastTestSupport.assertTrueEventually:1236->AbstractKinesisTest.lambda$assertMessages$3:160 Key sets differ! expected: but was: ```
Failed: https://github.com/hazelcast/hazelcast/pull/26064#issuecomment-1835942201
https://github.com/hazelcast/hazelcast/pull/19162/files/01a320d45abae66f52bbe6bb0920c3f80e05817c#diff-458a6ae63767f39e577c6667abc51bedca464966cc9aa6ad4ec1b9c053bb60eaR104 https://github.com/hazelcast/hazelcast-enterprise/issues/4198