[jira] [Updated] (HIVE-14208) Outer MapJoin uses key data of outer input and Converter
[ https://issues.apache.org/jira/browse/HIVE-14208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-14208: --- Issue Type: Improvement (was: Bug) > Outer MapJoin uses key data of outer input and Converter > > > Key: HIVE-14208 > URL: https://issues.apache.org/jira/browse/HIVE-14208 > Project: Hive > Issue Type: Improvement > Components: Query Processor >Affects Versions: 2.2.0 >Reporter: Jesus Camacho Rodriguez > > Consider an left outer MapJoin operator. OI for the outputs are created from > outer and inner side from their inputs. However, when there is a match in the > join, the data for the key is always taken from the outer side (as it is done > currently). Thus, we need to apply the Converter logic on the data to get the > correct type. > This issue is to explore whether a better solution would be to use the key > from correct inputs of the join to eliminate need of Converters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-14208) Outer MapJoin uses key data of outer input and Converter
[ https://issues.apache.org/jira/browse/HIVE-14208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-14208: --- Priority: Minor (was: Major) > Outer MapJoin uses key data of outer input and Converter > > > Key: HIVE-14208 > URL: https://issues.apache.org/jira/browse/HIVE-14208 > Project: Hive > Issue Type: Improvement > Components: Query Processor >Affects Versions: 2.2.0 >Reporter: Jesus Camacho Rodriguez >Priority: Minor > > Consider an left outer MapJoin operator. OI for the outputs are created from > outer and inner side from their inputs. However, when there is a match in the > join, the data for the key is always taken from the outer side (as it is done > currently). Thus, we need to apply the Converter logic on the data to get the > correct type. > This issue is to explore whether a better solution would be to use the key > from correct inputs of the join to eliminate need of Converters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-14208) Outer MapJoin uses key data of outer input and Converter
[ https://issues.apache.org/jira/browse/HIVE-14208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-14208: --- Component/s: Query Processor > Outer MapJoin uses key data of outer input and Converter > > > Key: HIVE-14208 > URL: https://issues.apache.org/jira/browse/HIVE-14208 > Project: Hive > Issue Type: Improvement > Components: Query Processor >Affects Versions: 2.2.0 >Reporter: Jesus Camacho Rodriguez >Priority: Minor > > Consider an left outer MapJoin operator. OI for the outputs are created from > outer and inner side from their inputs. However, when there is a match in the > join, the data for the key is always taken from the outer side (as it is done > currently). Thus, we need to apply the Converter logic on the data to get the > correct type. > This issue is to explore whether a better solution would be to use the key > from correct inputs of the join to eliminate need of Converters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
