Docs: Add rewrite-table-path in spark procedure #12115
Conversation
| ``` | ||
|
|
||
| Lastly, [register_table](#register_table) procedure can be used to register copied table in the target location with catalog. |
There was a problem hiding this comment.
Can we mentioned the validation to make sure table is usable?
There was a problem hiding this comment.
I had some offline discussion with @RussellSpitzer, I think referential integrity validation before table registration is great but it's hard to tell customer to do X without information on how to do X.
My plan is omit this for now in documentation, expand the logic in register_table procedure to allow for optional referential integrity check in another PR and come back to update this.
What do you think @flyrain ?
|
thank you @flyrain @RussellSpitzer for the promptly review, updated per your suggestion! |
Co-authored-by: Russell Spitzer <[email protected]>
Co-authored-by: Russell Spitzer <[email protected]>
|
thank you Russell for the detailed review! This is getting closer and I did a local check to ensure the info and warning section rendered as expected like in following screenshot. |
Co-authored-by: Yufei Gu <[email protected]>
Documentation for #11931 #11555
I took wording and docs with original author of @flyrain and @szehon-ho
Also @manuzhang is interested in this and wondering if @amogh-jahagirdar is ready to take this as part of 1.8