-
Notifications
You must be signed in to change notification settings - Fork 602
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
Iceberg custom partitioning: use configured spec when creating the table #24952
Conversation
CI test resultstest results on build#61260
test results on build#61380
|
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.
Looking good
@@ -249,19 +249,31 @@ checked<ss::gate::holder, coordinator::errc> coordinator::maybe_gate() { | |||
return gate_.hold(); | |||
} | |||
|
|||
struct coordinator::table_schema_provider { |
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.
nit: just a thought, this file is getting a bit crowded to read through with the different implementations of this schema provider sprinkled throughout. Might be easier on the eyes to separate it out into its own header and cc
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.
I kind of like it being close to the respective functions as the only reason for existence of these classes is to factor out differences in those functions
@@ -251,13 +251,9 @@ redpanda_cc_library( | |||
hdrs = [ | |||
"table_definition.h", | |||
], | |||
implementation_deps = [ |
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.
🔥
# key to ensure that all partitions get some records | ||
key=str(uuid4()), | ||
value=record) | ||
producer.flush() |
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.
Is it possible for us to get very unlucky and for the records in this batch to also be in different hours?
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.
good catch, I was intending to have the same timestamp_us
value for all records and partition based on that, but forgot to change the spec expression.
No functional changes.
As we now set the partition spec from config property values, we don't need a hardcoded spec in the main binary.
7cbce89
to
b434da9
Compare
Backports Required
Release Notes
Features
redpanda.iceberg.partition.spec
topic property.