RussellSpitzer commented on issue #4217: URL: https://github.com/apache/iceberg/issues/4217#issuecomment-1050935112
Could you paste what q7-v2.4 is? My guess would be if the join types are swapped then the size estimation is occurring differently in the Hive and Iceberg code *or* the pushdown is not working correctly. Spark should be planning the same logical join in both cases, the only difference should be the transition to a physical plan which would be dependent on the source responding with how much information is on each side of the join. If the predicate pushdown isn't working that would happen, or it could be that our size estimate code has a bug with certain predicates. A full Spark EXPLAIN of the query should show the predicate portion at least, the Spark UI should have the input sizes reported. On Fri, Feb 25, 2022 at 2:31 AM andrey-mindrin ***@***.***> wrote: > Additional information. Total size of data is about 300 Gb in parquet, > tried different options for iceberg tables including vectorization, > distributed by hash and range. Iceberg tables created with a query like > > create table ice_table using iceberg partition by (column) location > ‘hdfs://location’ > tblproperties(‘vectorization-enabled’=true,’write.parquet.compression-codec’=’snappy’,’ > write.distribution-mode’=’hash’) as select * from hive_table > > Analyzing query plans in Spark for query q7-v2.4 shows different join > types – SortMergeJoin in Iceberg and BroadcastHashJoin in Hive tables. > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/iceberg/issues/4217#issuecomment-1050642335>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AADE2YNQSKOPTIUWGU2ZQ63U44473ANCNFSM5PG44ZUQ> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
