You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Krystal (JIRA)" <ji...@apache.org> on 2014/06/03 18:25:02 UTC

[jira] [Reopened] (DRILL-672) Queries against hbase table do not close after the data is returned.

     [ https://issues.apache.org/jira/browse/DRILL-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krystal reopened DRILL-672:
---------------------------


git.commit.id.abbrev=8490d74
git.build.time=02.06.2014 @ 10\:11\:56 PDT

Certain query still hangs against split hbase tables.  The rows are returned but query does not close.

0: jdbc:drill:schema=hbase> select cast(onecf['name'] as varchar(25)) name from voter limit 2;
+------------+
|    name    |
+------------+
| ulysses white |
|   jessica xylophone     |

The following query also behaves the same way:
select * from voter limit 5;


> Queries against hbase table do not close after the data is returned. 
> ---------------------------------------------------------------------
>
>                 Key: DRILL-672
>                 URL: https://issues.apache.org/jira/browse/DRILL-672
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - HBase
>    Affects Versions: 1.0.0-milestone-1
>            Reporter: Krystal
>            Assignee: Aditya Kishore
>         Attachments: DRILL-672-Queries-against-HBase-table-do-not-close-a.patch, DRILL-672-Queries-against-HBase-table-do-not-close-a.patch, DRILL-672-Queries-against-HBase-table-do-not-close-a.patch
>
>
> Ran the following query via sqlline against an hbase table that spans multiple regions:
> select * from voter limit 5;
> +------------+-------------+------------+---------------+------------+------------+--------------+
> |  row_key   | create_date |    name    | contributions | voterzone  |    age     | registration |
> +------------+-------------+------------+---------------+------------+------------+--------------+
> | [B@32cb56e6 | [B@43b63017 | [B@6e0f58bb | [B@318a9570   | [B@1590579 | [B@7b764b9f | [B@135ef30c  |
> | [B@3ea6a2c3 | [B@2e07d057 | [B@2ff175d | [B@3956dc34   | [B@7592f754 | [B@3abe81a | [B@b1304d8   |
> | [B@da30696 | [B@4a0568d8 | [B@292662df | [B@17253394   | [B@b5d456b | [B@187879a1 | [B@d794594   |
> | [B@14c6fe75 | [B@146bbdfb | [B@2d85b436 | [B@24fa5c93   | [B@30d3c9dc | [B@2069a38f | [B@777111e8  |
> | [B@204ed39b | [B@172675af | [B@5df84008 | [B@5533fd6a   | [B@484265d9 | [B@7f2cae9e | [B@4e7c484c  |
> It displays the 5 rows but then just hang without returning to the sqlline prompt.  This could be due to this table spans multiple regions.  Select against different table that resides in 1 partition does not this problem.



--
This message was sent by Atlassian JIRA
(v6.2#6252)