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

[Bug]: Get incorrect partition field name when refresh tables #2165

Closed
2 tasks done
Tracked by #1847
XBaith opened this issue Oct 21, 2023 · 2 comments · Fixed by #2166
Closed
2 tasks done
Tracked by #1847

[Bug]: Get incorrect partition field name when refresh tables #2165

XBaith opened this issue Oct 21, 2023 · 2 comments · Fixed by #2166
Labels
type:bug Something isn't working

Comments

@XBaith
Copy link
Contributor

XBaith commented Oct 21, 2023

What happened?

Some tables have customized partition aliases, but in ArcticDataFiles#genericRecord they are extracted based on the default partition aliases, which can lead to throwing NPE errors for not getting the correct fields

Affects Versions

master/0.5.x

What engines are you seeing the problem on?

Core

How to reproduce

  1. create a table with custom partition alias
  2. enable self-optimizing
  3. throw NPE when refresh table

Relevant log output

Refreshing table dls_sjc_iceberg.diag.matsparticipantquality(tableId=1050840) failed.
java.lang.ArrayIndexOutOfBoundsException: null

Uploading image.png…

Anything else

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

  • I agree to follow this project's Code of Conduct
@shidayang
Copy link
Contributor

Could you provide the complete error log stack trace? Perhaps we should consider the implementation logic of the ArcticDataFiles class comprehensively.

@XBaith
Copy link
Contributor Author

XBaith commented Oct 23, 2023

Could you provide the complete error log stack trace? Perhaps we should consider the implementation logic of the ArcticDataFiles class comprehensively.

The full log stacks were dropped since JVM deault optimize stacks if there are too many same exception stacks, refer to https://stackoverflow.com/questions/58696093/when-does-jvm-start-to-omit-stack-traces

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants