Max Englander

After feedback from @harshit-gangal and @systay in #11875 am amending the proposal slightly. Initially RFC intended to route joins to reference tables to the optimal keyspace _only_ when the reference...

Some more adjustments based on feedback: * Send INSERT/DELETE/UPDATE back to source table, even if the reference table was qualified in the query. * Don't limit the optimization to identically...

I won't be able to work on this anymore, un-assigning myself.

Hey @harshit-gangal thanks for the feedback 🤗 * Understood! * Agreed, will make sure we don't mirror DML. * I think it's OK for mirrored queries to target an out-of-sync...

In discussions with @rohit-nayak-ps, we agreed that if we go forward with this it should use a new topology record type, and not try to fit this into the routing...

Met with members of the Vitess team yesterday to gather feedback on the proposal and the demo implementation. Some notes: * @mattlord pointed out that instrumenting differences in latency in...

I will no longer be able to work on this. If someone else wants to take this over feel free to re-open. Thanks everyone for the feedback and discussions on...

Returning this to draft status until there's more clarity around next steps for https://github.com/vitessio/vitess/pull/11938

@Wolfy87 Not sure I follow. This PR would allow the bower user to use whatever `mustache` and `requirejs-text` versions they wanted, as long as they are above (the pretty generous)...

@harshit-gangal can do!