Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Fri, 15 May 2015 22:24:59 +0000 (UTC)
From: "Deneche A. Hakim (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12766942.1421098915000.131910.1431728699951@Atlassian.JIRA>
In-Reply-To: <JIRA.12766942.1421098915000@Atlassian.JIRA>
References: <JIRA.12766942.1421098915000@Atlassian.JIRA>
 <JIRA.12766942.1421098915643@arcas>
Subject: [jira] [Commented] (DRILL-1984) Drillbit does not send the last RPC
 message when "limit" is appended to queries on hbase voter table
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DRILL-1984?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1454=
6283#comment-14546283 ]=20

Deneche A. Hakim commented on DRILL-1984:
-----------------------------------------

[~alzarei] could you try to reproduce this using the latest master ? after =
DRILL-2498 this may not be a problem anymore. Thanks

> Drillbit does not send the last RPC message when "limit" is appended to q=
ueries on hbase voter table
> -------------------------------------------------------------------------=
---------------------------
>
>                 Key: DRILL-1984
>                 URL: https://issues.apache.org/jira/browse/DRILL-1984
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - RPC
>    Affects Versions: 0.7.0
>         Environment: Windows/OS X
>            Reporter: Alexander Zarei
>            Assignee: Deneche A. Hakim
>             Fix For: 1.2.0
>
>         Attachments: drillbit.log, drillbit.out, drillclient20150109T1550=
28.log, driver.log
>
>
> . When using =E2=80=9Climit=E2=80=9D in queries on hbase =E2=80=9Cvoter=
=E2=80=9D table, drill server does not return the very last RPC message. Th=
e very last RPC message is the one translated by DrillClient to a null reco=
rd batch to notify the ODBC driver of the completion/failure of a query.
> This problem is only with the voter table; I tested other hbase multi-reg=
ion and non-multi-region tables  and  they worked fine.=20
> It is only queries such as=20
> ------------------------------------------------------------
> SELECT * FROM (select cast(row_key as integer) voter_id, cast(voter.onecf=
.name as varchar(30)) name, cast(voter.twocf.age as integer) age, cast(vote=
r.twocf.registration as varchar(20)) registration, cast(voter.threecf.contr=
ibutions as decimal(6,2)) contributions, cast(voter.threecf.voterzone as in=
teger) voterzone,cast(voter.fourcf.create_date as timestamp) create_date fr=
om hbase.voter) T LIMIT 0
> select cast(row_key as integer) voter_id, cast(voter.onecf.name as varcha=
r(30)) name, cast(voter.twocf.age as integer) age, cast(voter.twocf.registr=
ation as varchar(20)) registration, cast(voter.threecf.contributions as dec=
imal(6,2)) contributions, cast(voter.threecf.voterzone as integer) voterzon=
e,cast(voter.fourcf.create_date as timestamp) create_date from hbase.voter =
limit 5
> that fail because the very last RPC message is not sent from the server t=
o the DrillClient and as a result the driver keeps waiting for it.


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