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

[Feature Request]: [IcebergIO] Allow users to specify a partition spec when creating tables #34117

Open
2 of 17 tasks
ahmedabu98 opened this issue Feb 28, 2025 · 3 comments
Open
2 of 17 tasks

Comments

@ahmedabu98
Copy link
Contributor

What would you like to happen?

Add a new configuration option to pass a Map<String, String> representing columns and their partition transforms

Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@Suvrat1629
Copy link

Hey @ahmedabu98, I was taking a look at this issue. If we added a setPartitionSpec in the IcebergIO.java and then tweaked the WriteToDestination.java file it is also causng a problem in the AutoValue_IcebergIO_WriteRows.java. What does this file do?

@ahmedabu98
Copy link
Contributor Author

Notice that IcebergIO's subclass "WriteRows" is annotated with "@autovalue". It's a nice tool that helps generate boilerplate code, we use it quite a bit in this code base. Nice article here that describes how it works: https://www.baeldung.com/introduction-to-autovalue

@Suvrat1629
Copy link

@ahmedabu98 ok so this will generate the AutoValue_IcebergIO_WriteRows.java automatically so I dont have make any changes in this file; I just need to tweak the "WriteRows" and the "@autovalue" will auto-geherate this file? Is this right? Can I give this issue a shot?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants