hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Boudnik (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-80) Add testcases for concurrent query execution
Date Tue, 15 Nov 2011 02:26:51 GMT

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

Konstantin Boudnik commented on HIVE-80:
----------------------------------------

Perhaps my question is bigger than this issue or shall be asked somewhere else, but looking
at Hive code I couldn't help noticing that it is essentially build as a singleton i.e. only
a single instance of Hive object is allowed to exist. 

What was/is a design motivation behind of this? Why Hive can't be instantiated at will by
the client so different instances can be independently for query analysis, job submissions,
etc.? This will make Hive much more flexible and extendable from Hive client applications
perspective, won't it?
                
> Add testcases for concurrent query execution
> --------------------------------------------
>
>                 Key: HIVE-80
>                 URL: https://issues.apache.org/jira/browse/HIVE-80
>             Project: Hive
>          Issue Type: Test
>          Components: Query Processor, Server Infrastructure
>            Reporter: Raghotham Murthy
>            Assignee: Carl Steinbach
>            Priority: Critical
>              Labels: concurrency
>         Attachments: hive_input_format_race-2.patch
>
>
> Can use one driver object per query.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message