You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error occurs when access to table files of a non-partitioned table
Affects Versions
master
What engines are you seeing the problem on?
AMS
How to reproduce
create an internal catalog
create iceberg table without partition filed
access data file from dashboard
Relevant log output
java.lang.IllegalArgumentException: Invalid partition data, too many fields (expecting 0): null
at org.apache.iceberg.relocated.com.google.common.base.Preconditions.checkArgument(Preconditions.java:326) ~[iceberg-bundled-guava-1.3.0.jar:?]
at com.netease.arctic.utils.ArcticDataFiles.data(ArcticDataFiles.java:89) ~[amoro-core-0.7.0-SNAPSHOT.jar:?]
at com.netease.arctic.server.dashboard.MixedAndIcebergTableDescriptor.collectFileInfo(MixedAndIcebergTableDescriptor.java:503) ~[amoro-ams-server-0.7.0-SNAPSHOT.jar:?]
at com.netease.arctic.server.dashboard.MixedAndIcebergTableDescriptor.getTableFilesInternal(MixedAndIcebergTableDescriptor.java:491) ~[amoro-ams-server-0.7.0-SNAPSHOT.jar:?]
at com.netease.arctic.server.dashboard.MixedAndIcebergTableDescriptor.getTableFiles(MixedAndIcebergTableDescriptor.java:396) ~[amoro-ams-server-0.7.0-SNAPSHOT.jar:?]
at com.netease.arctic.server.dashboard.ServerTableDescriptor.getTableFile(ServerTableDescriptor.java:110) ~[amoro-ams-server-0.7.0-SNAPSHOT.jar:?]
at com.netease.arctic.server.dashboard.controller.TableController.getPartitionFileListInfo(TableController.java:461) ~[amoro-ams-server-0.7.0-SNAPSHOT.jar:?]
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
The text was updated successfully, but these errors were encountered:
What happened?
Error occurs when access to table files of a non-partitioned table
Affects Versions
master
What engines are you seeing the problem on?
AMS
How to reproduce
Relevant log output
Anything else
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: