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

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

Commit 09454cea7900df72a4285b3fd7ac78444587d951 in impala's branch 
refs/heads/master from Steve Carlin
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=09454ce ]

IMPALA-10750: Impala-shell changes for HS2 compatibility

Need some changes to impala-shell to make the client more HS2
compatible, including:

- when the fetch returns the bitset containing nulls, the lack of
  presence of bits means it is not null.  Currently it will fail
  the query.

- adding fetchType to TCLIServiceThrift structure (though unused
  currently in Impala)

Also a small refactor was done to put the functionality that retrieves
all query options into its own function.

Change-Id: Id3a4c4ce8a5d60db136df1743f32dba22172ee13
Reviewed-on: http://gerrit.cloudera.org:8080/17590
Reviewed-by: Csaba Ringhofer <[email protected]>
Tested-by: Csaba Ringhofer <[email protected]>


> Changes needed for impala-shell to make it more HS2 compatible
> --------------------------------------------------------------
>
>                 Key: IMPALA-10750
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10750
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Clients
>            Reporter: Steve Carlin
>            Priority: Major
>
> Need some changes to impala-shell to make the client more HS2 compatible, 
> including:
>  * when the fetch returns the bitset containing nulls, the lack of presence 
> of bits means it is not null.  Currently it will fail the query.
>  * adding fetchType to TCLIServiceThrift structure (though unused currently 
> in Impala)



--
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