Skip to content
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

write.wap.enabled / spark.wap.branch behavior isn't really documented #11528

Open
1 of 3 tasks
wimlewis-amazon opened this issue Nov 12, 2024 · 0 comments
Open
1 of 3 tasks
Labels
improvement PR that improves existing functionality

Comments

@wimlewis-amazon
Copy link

Feature Request / Improvement

It's unclear from reading the doc what the effect of setting write.wap.enabled actually is. I can make some assumptions based on the write-audit-publish example, but those assumptions are almost certainly incomplete (for example, there are edge cases and failure conditions that I would need to understand before applying this in production, but the example only shows the "happy path".). As a user of the Iceberg libraries, I would like the documentation to be more explicit about what changes if I set either of these configuration options.

Query engine

Spark

Willingness to contribute

  • I can contribute this improvement/feature independently
  • I would be willing to contribute this improvement/feature with guidance from the Iceberg community
  • I cannot contribute this improvement/feature at this time
@wimlewis-amazon wimlewis-amazon added the improvement PR that improves existing functionality label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement PR that improves existing functionality
Projects
None yet
Development

No branches or pull requests

1 participant