You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Cheng Hao (JIRA)" <ji...@apache.org> on 2014/06/11 05:09:02 UTC
[jira] [Commented] (SPARK-2106) Unify the HiveContext
[ https://issues.apache.org/jira/browse/SPARK-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027360#comment-14027360 ]
Cheng Hao commented on SPARK-2106:
----------------------------------
[~marmbrus], let me know if you have some input, and I don't mind if you assign the task to me. :)
> Unify the HiveContext
> ---------------------
>
> Key: SPARK-2106
> URL: https://issues.apache.org/jira/browse/SPARK-2106
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Reporter: Cheng Hao
>
> I've been working on CLI for Catalyst, and from the CLI point of view, HiveContext may be required some changes as:
> - SessionState management
> `SessionState` instance creation & initialization should be done within the wrappers, e.g. in `SharkCliDriver` or `CLIService` etc. cause they know better how to load the user configuration and logger redirection etc. And in HiveContext, it can retrieve SessionState by calling `SessionState.get()`.
> - HiveContext API may not be enough for CLI
> 1) Retrieving the schema from the output of `SELECT`; but the internal class `QueryExecution` is hidden for CLI.
> 2) Retriveing the HQL result in CLI, besides the string based result, CLI also need to know the error code, as well as the call stack if exceptions thrown.
--
This message was sent by Atlassian JIRA
(v6.2#6252)