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

ASF subversion and git services commented on IMPALA-10655:
----------------------------------------------------------

Commit dfc1b549687bf78226af8701bd67325b88c4ff69 in impala's branch 
refs/heads/master from Kurt Deschler
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=dfc1b54 ]

IMPALA-10655: Add ImpalaServer interface to Initialize TQueryCtx for external 
frontends

This patch adds a new interface that returns an initialized TQueryCtx
for use in requests submitted by external frontends. This is necessary
to ensure that the query context in an externally generated TExecRequest
has appropriate coordinator metadata.

Testing: External frontend regression tests

Change-Id: I59cebcf087e703a4ab49fb44f6f5ba1044f26546
Reviewed-by: Aman Sinha <[email protected]>
Reviewed-on: http://gerrit.cloudera.org:8080/17312
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Add ImpalaServer interface to Initialize TQueryCtx for external frontends
> -------------------------------------------------------------------------
>
>                 Key: IMPALA-10655
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10655
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Backend
>            Reporter: Kurt Deschler
>            Assignee: Kurt Deschler
>            Priority: Major
>
> During query initialization, the backend populates the TQueryCtx thrift 
> structure based on parameter settings, startup flags and other metadata. A 
> new interface needs to be added so that external frontends can share this 
> logic by retrieving an initialized TQueryCtx structure. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to