-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Core: Apply correct metric configs in GenericAppenderFactory #12366
base: main
Are you sure you want to change the base?
Conversation
The specific cause of the issue can be referenced in apache/amoro#3273 |
52ed81c
to
c9dfece
Compare
c9dfece
to
d0ac6f4
Compare
d0ac6f4
to
00f3e02
Compare
MetricsConfig metricsConfig; | ||
if (table == null) { | ||
metricsConfig = MetricsConfig.fromProperties(config); | ||
} else { | ||
metricsConfig = MetricsConfig.forTable(table); | ||
} | ||
|
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.
This is a bit questionable for me.
Do we really want to disregard the config properties specifically set by the set
/setAll
method if the table has provided?
We should decide on the expected behavior and make sure that we don't get wrong configuration. Maybe by throwing an exception in the set methods when the table is set?
Please add some tests to ensure that the metrics are honored if the table is set |
5eeeabd
to
27263c1
Compare
The DataWriter created using GenericAppenderFactory in the application does not configure metric writing behavior according to the table's properties.
Based on previous modifications, such as FlinkAppenderFactory, this class should also invoke the correct API to configure the relevant properties