Anusha Jayasundara
Anusha Jayasundara
In Incremental aggregation(aka [named aggregation](https://siddhi.io/en/v5.1/docs/query-guide/#named-aggregation) the out-of-order event handling is embedded into the implementation. All the events will be aggregated according to the event timestamp if the aggregation is defined...
@angel-aam It seems like in your delays_tables_join siddhi app, on the "insert table 2" query you are filling the table1 rather filling table2. I believe that's why you are observing...
I have tested this on [Streaming Integrator](https://wso2.com/integration/streaming-integrator/#) which is based on siddhi 5.1.12 and couldn't observe the above behavior.
You can try this on [Streaming Integrator](https://hub.docker.com/r/wso2/streaming-integrator/tags) docker image
Streaming Integrator 1.x.x is a part of Enterprise Integrator 7.x.x offering and SI is the one which is based on Siddhi.
Fixed by https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/2400
This PR will fix the mentioned issue https://github.com/wso2/carbon-apimgt/pull/12442
Tested this on the latest version and couldn't reproduce the behaviour
Yes, observed the behaviour in Firefox 124.0.1 in the latest(Post alpha2) pack
This issue is there in API Manager 4.2.0 version as well,