[ https://issues.apache.org/jira/browse/HIVE-8183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suhas Satish updated HIVE-8183: ------------------------------- Description: Originally introduced for Tez, ConvertJoinMapJoin heavily uses OptimizeTezProcContext . Although we do have an equivalent OptimizeSparkProcContext, the 2 are not derived from any common ancestor class. We will need some class hierarchy redesign/refactoring to make ConvertJoinMapJoin be more generic to support multiple execution frameworks. For now, I am thinking of proceeding with a cloned SparkConvertJoinMapJoin class using OptimizeSparkProcContext was: Originally introduced for Tez, ConvertJoinMapJoin heavily uses OptimizeTezProcContext . Although we do have an equivalent OptimizeSparkProcContext, the 2 are not derived from any common ancestor class. We will need some class hierarchy redesign/refactoring to make ConvertJoinMapJoin be more generic to support multiple execution frameworks. For now, I am thinking of proceeding with a cloned SparkConvertJoinMapJoin class using OptimizeSparkProcContext We might need to open a jira for this refactoring. > make ConvertJoinMapJoin optimization pluggable for different execution > frameworks > --------------------------------------------------------------------------------- > > Key: HIVE-8183 > URL: https://issues.apache.org/jira/browse/HIVE-8183 > Project: Hive > Issue Type: Improvement > Components: Physical Optimizer > Affects Versions: 0.14.0, 0.13.1, spark-branch > Reporter: Suhas Satish > Labels: spark > > Originally introduced for Tez, ConvertJoinMapJoin heavily uses > OptimizeTezProcContext . Although we do have an equivalent > OptimizeSparkProcContext, the 2 are not derived from any common ancestor > class. We will need some class hierarchy redesign/refactoring to make > ConvertJoinMapJoin be more generic to support multiple execution frameworks. > For now, I am thinking of proceeding with a cloned SparkConvertJoinMapJoin > class using OptimizeSparkProcContext -- This message was sent by Atlassian JIRA (v6.3.4#6332)