hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-9376) Add back some APIs which changed from 0.13 for Spark SQL
Date Wed, 14 Jan 2015 19:37:35 GMT

    [ https://issues.apache.org/jira/browse/HIVE-9376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277530#comment-14277530
] 

Thejas M Nair commented on HIVE-9376:
-------------------------------------

Isn't it better to deal with this using some shims in spark-sql, similar to hadoop shims used
in hive ?

Thanks for marking the api's added back as deprecated and unstable. But what does it really
mean ? :) I am not sure what precedent we are setting by modifying the internal classes to
support deprecated/unstable apis.
The Context class was never meant/expected to be an external facing class, unlike classes
say in the metastore layer. 


> Add back some APIs which changed from 0.13 for Spark SQL
> --------------------------------------------------------
>
>                 Key: HIVE-9376
>                 URL: https://issues.apache.org/jira/browse/HIVE-9376
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Brock Noland
>            Assignee: Brock Noland
>             Fix For: 0.15.0
>
>         Attachments: HIVE-9376.1.patch
>
>
> As [discussed on HIVE-9364|https://issues.apache.org/jira/browse/HIVE-9364?focusedCommentId=14276100&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14276100]
some APIs were changed which broke SparkSQL. This change adds them back, marks them as Deprecated,
Unstable, and in-use by SparkSQL.



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

Mime
View raw message