spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Armbrust (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-6674) Use different types to represent rows used inside and outside Catalyst
Date Wed, 20 May 2015 19:15:00 GMT

     [ https://issues.apache.org/jira/browse/SPARK-6674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Armbrust resolved SPARK-6674.
-------------------------------------
    Resolution: Duplicate

> Use different types to represent rows used inside and outside Catalyst
> ----------------------------------------------------------------------
>
>                 Key: SPARK-6674
>                 URL: https://issues.apache.org/jira/browse/SPARK-6674
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.1.1, 1.2.1, 1.3.0
>            Reporter: Cheng Lian
>
> Within Catalyst, we use more efficient classes to represent objects in rows. For example,
we use {{o.a.s.sql.types.Decimal}} instead of Java {{BigDecimal}}. When row objects are passed
to / from user space, these object get converted by {{ScalaReflection.convertToScala}} / {{ScalaReflection.converToCatalyst}}.
> This approach is error prone because we may occasionally forget to add necessary conversions.
It would be better to have a dedicated row type to represent row objects used within Catalyst,
thus enforce this convention via type system.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message