Spark 3.5: Support RewriteManifestsProcedure with a target size parameter #11959
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Limitations: The rewrite manifest currently has limited parameters. To set or change the manifest size, you must go through the table config, which restricts flexibility. We wish for rewriting and setting the target size to be a unified operation that only impacts that particular rewrite. During tuning, we test various sizes for the manifest. In contrast, when rewriting data files, we can specify files directly without altering table properties, and other files remain unaffected by the target size.
Consideration for Options: I initially considered using options to specify parameters, but since few are needed for rewriting the manifest, adding just one parameter for the target size seems sufficient. This approach is open to further discussion.