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
I have searched in the issues and found no similar issues.
What would you like to be improved?
We invoked table statistics in #1344 by applying native Iceberg's implementation to both the base and change store and merging them.
When calculating the change store, the native iceberg implementation cannot sense the max transaction of the mix-format change store, so the statistics calculated are wrong.
Two tables with almost the same amount of data:
Mix-format:
Iceberg-format:
Mix-format's 'row count' is twice as long as Iceberg's. This may have some impact on performance.
How should we improve?
Two options:
Only calculate the base store and ignore the change store's statistics.
Implement the 'TableStatisticsReader' by using Mix-format's plan to get the most accurate statistics(May increase maintenance costs for upgraded versions).
zhoujinsong
changed the title
[Improvement]: Mix-format Table stats for Trino engine need to be calculated individually
[Improvement]: Mixed-format Table stats for Trino engine need to be calculated individually
Jun 26, 2024
Search before asking
What would you like to be improved?
We invoked table statistics in #1344 by applying native Iceberg's implementation to both the base and change store and merging them.
When calculating the change store, the native iceberg implementation cannot sense the max transaction of the mix-format change store, so the statistics calculated are wrong.
Two tables with almost the same amount of data:

Mix-format:
Iceberg-format:

Mix-format's 'row count' is twice as long as Iceberg's. This may have some impact on performance.
How should we improve?
Two options:
Are you willing to submit PR?
Subtasks
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: