[
https://issues.apache.org/jira/browse/DRILL-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated DRILL-672:
---------------------------------
Description:
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.
was:
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. Here
is part of the jstack trace for the sqlline process:
"Finalizer" daemon prio=10 tid=0x00007fa30006e800 nid=0x191d in Object.wait()
[0x00007fa2fcd1d000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000000f4026f48> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
- locked <0x00000000f4026f48> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:189)
"Reference Handler" daemon prio=10 tid=0x00007fa30006a000 nid=0x18d6 in
Object.wait() [0x00007fa2fce1e000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000000f4026b68> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:503)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
- locked <0x00000000f4026b68> (a java.lang.ref.Reference$Lock)
"main" prio=10 tid=0x00007fa30000d000 nid=0x1891 waiting on condition
[0x00007fa307e35000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000ec546e38> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082)
at
java.util.concurrent.LinkedBlockingDeque.pollFirst(LinkedBlockingDeque.java:519)
at
java.util.concurrent.LinkedBlockingDeque.poll(LinkedBlockingDeque.java:682)
at
org.apache.drill.jdbc.DrillResultSet$Listener.getNext(DrillResultSet.java:166)
at org.apache.drill.jdbc.DrillCursor.next(DrillCursor.java:83)
at
net.hydromatic.avatica.AvaticaResultSet.next(AvaticaResultSet.java:172)
at sqlline.SqlLine$IncrementalRows.hasNext(SqlLine.java:2503)
at sqlline.SqlLine$TableOutputFormat.print(SqlLine.java:2148)
at sqlline.SqlLine.print(SqlLine.java:1809)
at sqlline.SqlLine$Commands.execute(SqlLine.java:3766)
at sqlline.SqlLine$Commands.sql(SqlLine.java:3663)
at sqlline.SqlLine.dispatch(SqlLine.java:889)
at sqlline.SqlLine.begin(SqlLine.java:763)
at sqlline.SqlLine.start(SqlLine.java:498)
at sqlline.SqlLine.main(SqlLine.java:460)
> 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
>
> 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)
