substrait icon indicating copy to clipboard operation
substrait copied to clipboard

docs: clarify advanced extensions

Open wackywendell opened this issue 5 months ago • 2 comments

The Advanced Extensions section of the docs seemed somewhat mismatched from what was in the protobufs, so I tried to clarify it, based on what was in the protobuf definitions.

Thoughts welcome! Also could use some sanity-checking on the details!

Naming

I also included custom relations (ExtensionLeafRel, …) and custom reads and writes (ExtensionTable, …) all under the heading "Advanced Extensions", even though there is an AdvancedExtension message that doesn't cover those. The name "Advanced Extension" seems a bit ambiguous here - does it cover all of the above, or only the enhancements and optimizations in the AdvancedExtension message? - but it seems to be what we have, so I went with it. Thoughts?

Guidance

This is a bit low on guidance on when to use which - e.g. ExtensionLeafRel, ExtensionTable, or ReadRel.advanced_extension.enhancement could potentially all be used for an unusual kind of read. I'm not sure what the guidance here should be, or if there should be any, so I left it out; I'm not sure any guidance here would be that helpful.

wackywendell avatar Jul 25 '25 20:07 wackywendell

@yongchul - thanks for the review! Good comments - I've updated to address them. Can you give them a look?

Thanks!

wackywendell avatar Jul 30 '25 20:07 wackywendell

Thanks again! Incorporated. I also realized I had the !!! note sections incorrect (they needed indenting), so I fixed that, and ran mkdocs locally to verify it worked - and it did!

wackywendell avatar Jul 31 '25 19:07 wackywendell

^ Thanks, @yongchul for the merge! I'm wondering - what do we need to do next to advance this? Do we need additional reviewers so we can get it approved and merged?

wackywendell avatar Nov 18 '25 19:11 wackywendell

^ Thanks, @yongchul for the merge! I'm wondering - what do we need to do next to advance this? Do we need additional reviewers so we can get it approved and merged?

Thank you for your patience! We will need another SMC review I believe. I'll bring this up in the sync up.

yongchul avatar Nov 19 '25 00:11 yongchul

@yongchul @wackywendell As I understand it, the governance rules dictate that only one SMC approval is necessary to get documentation changes in.

Since @yongchul is an SMC, do we have to wait for any other approvals? Or can we just merge it?

benbellick avatar Nov 20 '25 16:11 benbellick

@yongchul @wackywendell As I understand it, the governance rules dictate that only one SMC approval is necessary to get documentation changes in.

Since @yongchul is an SMC, do we have to wait for any other approvals? Or can we just merge it?

I'm going to merge after re-reading the changes one last time. :smile

yongchul avatar Nov 20 '25 20:11 yongchul

@wackywendell thank you for the changes and sorry about taking it so long! Please resolve the two minor changes and it looks good to me to go!

yongchul avatar Nov 21 '25 04:11 yongchul

Thanks, @yongchul! I updated, let me know how it looks to you - especially the sorting example, clustering was unclear as you noted!

wackywendell avatar Nov 21 '25 15:11 wackywendell

The one issue I see with the extensions updates here is that they act like the only way to express something is using protobuf. Our goal was to spec first, with proto being an implementation. That being said, the reality is a bit different than that.

jacques-n avatar Dec 03 '25 18:12 jacques-n