-
Notifications
You must be signed in to change notification settings - Fork 395
Update delta-optimization-and-v-order.md #2352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Added prerequisite for the ALTER command when setting V-Order on a delta table
|
@basland : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 65c0f4d: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the Delta optimization and V-Order documentation to clarify prerequisites for altering table properties. Specifically, it adds a note that the spark.databricks.delta.allowArbitraryProperties.enabled configuration must be set to true before using the ALTER command to modify V-Order settings on a delta table.
Key changes:
- Added prerequisite information for the ALTER command in the V-Order configuration section
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Co-authored-by: Copilot <[email protected]>
|
Learn Build status updates of commit 37e5844: ✅ Validation status: passed
For more details, please refer to the build report. |
|
This pull request has been inactive for 14 days, and an |
|
#sign-off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @eric-urban |
|
@eric-urban Hi Eric, where is this PR hanging, is it waiting for my input? |
|
Hi @basland - Thanks for your review. In the public repo, pull requests should be signed off by the author, another member of the content team, or a PM. @eric-urban Could you take a look? Thanks! |
Added prerequisite for the ALTER command when setting V-Order on a delta table
Thank you for contributing to Microsoft Fabric documentation
Fill out these items before submitting your pull request:
If you are working internally at Microsoft:
Provide a link to an Azure DevOps Boards work item that tracks this feature/update.
Who is your primary Skilling team contact? @mention them individually tag them and let them review the PR before signing off.
For internal Microsoft contributors, check off these quality control items as you go
1. Check the Acrolinx report: Make sure your Acrolinx Total score is above 80 minimum (higher is better) and with no spelling issues. Acrolinx ensures we are providing consistent terminology and using an appropriate voice and tone, and helps with localization.
2. Successful build with no warnings or suggestions: Review the build status to make sure all files are green (Succeeded).
3. Preview the pages:: Click each Preview URL link to view the rendered HTML pages on the review.learn.microsoft.com site to check the formatting and alignment of the page. Scan the page for overall formatting, and look at the parts you edited in detail.
4. Check the Table of Contents: If you are adding a new markdown file, make sure it is linked from the table of contents.
5. #sign-off to request PR review and merge: Once the pull request is finalized and ready to be merged, indicate so by typing
#sign-offin a new comment in the Pull Request. If you need to cancel that sign-off, type#hold-offinstead. Signing off means the document can be published at any time. Note, this is a formatting and standards review, not a technical review.Merge and publish
#sign-off, there is a separate PR Review team that will review the PR and describe any necessary feedback before merging.#sign-offagain. The PR Review team reviews and merges the pull request into the specified branch (usually the main branch or a release- branch).