-
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
Remove generated alerts #1385
Remove generated alerts #1385
Conversation
1eea84f
to
282a3fb
Compare
282a3fb
to
d94727e
Compare
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.
Thanks for cleaning some these up! When we upgraded the static checks a lot more things were detected but we decided to clean them up in follow-ups.
@@ -127,7 +126,7 @@ private FlinkFileAppenderFactory(Schema schema, RowType flinkSchema, Map<String, | |||
@Override | |||
public FileAppender<RowData> newAppender(OutputFile outputFile, FileFormat format) { | |||
// TODO MetricsConfig will be used for building parquet RowData writer. | |||
MetricsConfig metricsConfig = MetricsConfig.fromProperties(props); | |||
// MetricsConfig metricsConfig = MetricsConfig.fromProperties(props); |
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.
My only question here is why not just delete the line and todo if we aren't using them and just have a github issue instead?
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 agree here. A github issue is more likely to be picked up and worked on over a TODO in the codebase.... though I'm not opposed to keeping the TODO so people don't accidentally overly refactor away from the possibility (if that's a potential concern).
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 point, and I fully agree. I've created a Github issue: #1402
Looks like this is failing Java tests. |
this.nameMapping = NameMappingParser.fromJson(nameMappingString); | ||
} | ||
return nameMapping; | ||
} |
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 think there might be a PR open related to this. However, I don't see this particular function used: https://github.com/apache/iceberg/pull/1399/files
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 think we can remove this for now.
…into fd-remove-alerts
While working on upgrading the Avro dependency, I've noticed that there are a lot of warning, that can easily be resolved:
Makes the output a bit less verbose :)