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
what's the target release for this feature? should we target it at 3.0?
We will achieve the enhancement with following step.
The step one will merge in 2.5 openning in standalone or mixcoord without break change.
Other break changes will merge in 3.0.
After step one, we can design new feature without considering distribution issues between coords.
what's the target release for this feature? should we target it at 3.0?
The task will progress through three stages:
In version 2.5.x, we will eliminate the RPC layer among coordinators, allowing mixcoord deployment to rely solely on internal process communication, without affecting rolling upgrades.
In version 3.0, only one coordinator component will be permitted to start, requiring the cluster to be stopped before upgrading from 2.x.x.
In version 3.0.x, we will merge and streamline the coordinators, including the meta manager and task scheduler, into a single unit, while maintaining compatibility for rolling upgrades from 3.0 to 3.x.
Additionally, the next task will focus on enhancing support for streaming queries in streaming services, targeting a release with version 3.0.
Is there an existing issue for this?
What would you like to be added?
Why is this needed?
Anything else?
No response
The text was updated successfully, but these errors were encountered: