Sam Kleinman

> Could you explain a bit more about atomicity and multi-threading here? I guess, more specifically, how does this case differ from, say, two people trying to write the same...

> Could you also explain why creating the directory changes the outcome here? Is it that it takes two steps instead of one (creating the directory and then creating the...

Where do you think we should be logging or noting this (and do we have other logging like this that people might expected to look at?

> There may need to be a bit of logic to rephrase based on whether this is local (Directory created) vs Cloud storage (Prefix created). We can't do this for...

> I'm not quite following here. Could you explain with a bit more detail? From the perspective of user's there isn't really anything/anywhere _to_ log during successful operations, or at...

These results are rendered [here](https://github.com/glaredb/glaredb/blob/main/crates/sqlexec/src/session.rs#L62) and while we could have a different message, it'd be a bit of a bodge. Also, I think it would be good if this operation...

current state: benchmarks fail in CI despite running locally; though they are flaky. For running with larger scale we'd need a custom runner. @universalmind303 can you take a look this...

It seems to me, based on the message, and looking at the implementation of `dispatch_access` (and the discussion here!) that "we have a big file that's slow to download, hits...

As discussed on the dev call today: - [ ] turn this panic into an error message: "upstream http service returned unexpected results, contact your provider" - [ ] retry...

I think we'd want to have this be a mode or flag that we set on a table. The term of art for this might be "wide column store". Obviously,...