[
https://issues.apache.org/jira/browse/SPARK-7186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584151#comment-14584151
]
Apache Spark commented on SPARK-7186:
-------------------------------------
User 'davies' has created a pull request for this issue:
https://github.com/apache/spark/pull/6792
> Decouple internal Row from external Row
> ---------------------------------------
>
> Key: SPARK-7186
> URL: https://issues.apache.org/jira/browse/SPARK-7186
> Project: Spark
> Issue Type: New Feature
> Components: SQL
> Reporter: Reynold Xin
> Assignee: Davies Liu
> Priority: Blocker
>
> Currently, we use o.a.s.sql.Row both internally and externally. The external
> interface is wider than what the internal needs because it is designed to
> facilitate end-user programming. This design has proven to be very error
> prone and cumbersome for internal Row implementations.
> As a first step, we should just create an InternalRow interface in the
> catalyst module, which is identical to the current Row interface. And we
> should switch all internal operators/expressions to use this InternalRow
> instead. When we need to expose Row, we convert the InternalRow
> implementation into Row for users.
> After this, we can start removing methods that don't make sense for
> InternalRow (in a separate ticket). This is probably one of the most
> important refactoring in Spark 1.5.
--
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
