[jira] [Updated] (HIVE-12309) TableScan should colStats when available for better data size estimate
[ https://issues.apache.org/jira/browse/HIVE-12309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-12309: Attachment: HIVE-12309.2.patch [~prasanth_j] Would you like to take a look? > TableScan should colStats when available for better data size estimate > -- > > Key: HIVE-12309 > URL: https://issues.apache.org/jira/browse/HIVE-12309 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: HIVE-12309.2.patch, HIVE-12309.patch > > > Currently, all other operators use column stats to figure out data size, > whereas TableScan relies on rawDataSize. This inconsistency can result in an > inconsistency where TS may have lower Datasize then subsequent operators. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-12309) TableScan should colStats when available for better data size estimate
[ https://issues.apache.org/jira/browse/HIVE-12309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-12309: Attachment: HIVE-12309.patch > TableScan should colStats when available for better data size estimate > -- > > Key: HIVE-12309 > URL: https://issues.apache.org/jira/browse/HIVE-12309 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: HIVE-12309.patch > > > Currently, all other operators use column stats to figure out data size, > whereas TableScan relies on rawDataSize. This inconsistency can result in an > inconsistency where TS may have lower Datasize then subsequent operators. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
