Hi all,
I've opened a PR [1] to add REST spec changes for a new protocol around table
scan planning. For context around the design discussions, see the original
google doc proposal [2], the dev list discussion thread [3], and finally the
discussion that has happened on the spec change PR.
Plea
Hi Jan,
I think we need further discussion for a few reasons:
* Semantic issues are significant, especially in a spec. They could create
gaps that are very hard to fix in the future. I would rather spend more
time designing them properly than fix the gaps with band-aid solutions in
the future.
*
Hi Walaa,
in my opinion the UUID vs table identifier discussion comes down to the
question: do we introduce table identifiers in an opaque struct in the
table snapshot summary or do we accept technical drawbacks?
Using UUIDs with a lineage struct in the view metadata leads to one of
the foll
