[DISCUSS] Spec update to cover compressed JSON metadata files

Hi Ryan, Thank you for the feedback. I responded on the PR let's try to close out the conversation there. Thanks, Micah On Thursday, May 1, 2025, Ryan Blue wrote: > I just commented on the PR, but I don't think that file naming should be > part of the spec requirements. This is informational a

Re: [DISCUSS] Finalizing the v3 spec

Thanks, everyone! Looks like there are a few points to discuss. [JB] Maybe a release with the core updated before announcing spec v3 officially would be a good idea ? [Manu] Agree with Russell and JB that we make a “RC” release for V3 spec to test implementations, compatibility, etc before finaliz

Re: [DISCUSS] Spec update to cover compressed JSON metadata files

I just commented on the PR, but I don't think that file naming should be part of the spec requirements. This is informational and there are lots of ways to determine file compression, including magic bytes and catalog metadata. There isn't a need for this to be required by the spec so I think it sh

Re: Discuss proposal - IRC APIs for Multi-Statement Multi-Table Transactions

Thanks for starting the discussion! I wanted to discuss more about the "Catalog GlobalSequenceNumber". I think we not only need to order the snapshots across tables but also assign them some timestamp so that time travel queries also work consistently across tables. In other words, "Catalog Global