Joseph Koshakow
Joseph Koshakow
By the way, I'm using version 1.78 for this.
I don't think we can just special case some scenarios and we will have to handle it gracefully. For example consider the following scenarios: - 1 day > 24 hrs...
@mjibson In case you already started reviewing, I just changed the name of the added user from "mz_system_external" to "http_default_user" because I thought the old name was really non-descriptive.
> @mjibson In case you already started reviewing, I just changed the name of the added user from "mz_system_external" to "http_default_user" because I thought the old name was really non-descriptive....
Quick update, I closed #14092 and @frankmcsherry is planning on pushing a fix for this.
FYI for anyone reading this. At one point this was passing every test but a single flaky test: https://buildkite.com/materialize/tests/builds/38774. Although I've been force pushing you can get to the code...
The biggest question for me was how to drop and recreate an introspection source in an already running COMPUTE cluster? I don't think we have the APIs needed for this....
@pH14 are you referring to #13967 or the current behavior? I'm not exactly familiar with the what will trigger a `downgrade_since` call. The Coordinator never needs to force compaction on...
This is correct under serializable, maybe undesirable, but correct.
I just pushed a commit that should have sped up reads under strict serializability (https://github.com/MaterializeInc/materialize/pull/13967). I'm not sure if it fixed this, but it might be worth retesting.