[ https://issues.apache.org/jira/browse/SPARK-9357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654350#comment-14654350 ]
Apache Spark commented on SPARK-9357: ------------------------------------- User 'hvanhovell' has created a pull request for this issue: https://github.com/apache/spark/pull/7942 > Remove JoinedRow > ---------------- > > Key: SPARK-9357 > URL: https://issues.apache.org/jira/browse/SPARK-9357 > Project: Spark > Issue Type: Umbrella > Components: SQL > Reporter: Reynold Xin > > JoinedRow was introduced to join two rows together, in aggregation (join key > and value), joins (left, right), window functions, etc. > It aims to reduce the amount of data copied, but incurs branches when the row > is actually read. Given all the fields will be read almost all the time > (otherwise they get pruned out by the optimizer), branch predictor cannot do > anything about those branches. > I think a better way is just to remove this thing, and materializes the row > data directly. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org