ajantha-bhat commented on PR #12629: URL: https://github.com/apache/iceberg/pull/12629#issuecomment-2868722899
> Could you clarify the concern around keeping the API to trigger full partition stats recompute? Clients have to rely on workarounds, even though Iceberg internally supports this through a private method. There are no strong concern. We felt it is redundant to have many APIs. Plus the reason for full compute again is very rare (maybe only during corruption). Plus there are ways to achieve full compute with the single API by clearing stats. > PS: what's the iceberg view on the fact that we are changing the behavior of the existing API (full recompute -> incremental)? From a client's perspective, it might be considered a breaking change. Still the full stats available for the user. The way it compute internally has changed. No difference in the output for the user. > I just checked the Impala docs (https://impala.apache.org/docs/build/html/topics/impala_compute_stats.html) and they mentions support for both options: This is little different. Per partition or whole table. (Not based on the snapshot) @deniskuzZ: I have a question for hive users, if the user calls incremental first time (table without previous stats) are you expecting it to throw error or do full compute? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
