You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Risingwave currently supports process time Temporal Join which requires its stream side to be an append-only stream which is quite restrictive to use. Users have to use some tricky ways to work around this restriction (e.g. using sink into an append-only table). To resolve this issue, we can materialize the temporal join result for non-append-only temporal join, as discussed with @st1page and @TennyZhuang . With materialization, when deletion messages arrive, we can retrieve the join result sent downstream previously, so the whole stream remains consistent. Furthermore, the non-append-only temporal join could be used to workaround the join amplification caused by dimension table updates if users could accept that the dimension updates don't need to be reflected downstream.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Risingwave currently supports process time Temporal Join which requires its stream side to be an append-only stream which is quite restrictive to use. Users have to use some tricky ways to work around this restriction (e.g. using sink into an append-only table). To resolve this issue, we can materialize the temporal join result for non-append-only temporal join, as discussed with @st1page and @TennyZhuang . With materialization, when deletion messages arrive, we can retrieve the join result sent downstream previously, so the whole stream remains consistent. Furthermore, the non-append-only temporal join could be used to workaround the join amplification caused by dimension table updates if users could accept that the dimension updates don't need to be reflected downstream.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: