You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/10/05 22:27:00 UTC

[jira] [Commented] (DRILL-5743) Using order by clause in a select * query on hbase table returns only the row_key and order by field(s)

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

ASF GitHub Bot commented on DRILL-5743:
---------------------------------------

GitHub user prasadns14 opened a pull request:

    https://github.com/apache/drill/pull/975

    DRILL-5743: Handling column family and column scan for hbase

    This PR handles the scenario where the projected column list contains both a column family and a column within the same family.
    
    @paul-rogers please review

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/prasadns14/drill DRILL-5743

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/975.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #975
    
----
commit 0469197e18b466dcfbb26b4c95c47c22b683416e
Author: Prasad Nagaraj Subramanya <pr...@gmail.com>
Date:   2017-10-05T22:18:43Z

    DRILL-5743: Handling column family and column scan for hbase

----


> Using order by clause in a select * query on hbase table returns only the row_key and order by field(s)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-5743
>                 URL: https://issues.apache.org/jira/browse/DRILL-5743
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - HBase
>    Affects Versions: 1.11.0
>            Reporter: Prasad Nagaraj Subramanya
>            Assignee: Prasad Nagaraj Subramanya
>
> 1) Consider a hbase table 'part' having column family 'data', which contains columns related to tpch part table
> {code}
> select * from hbase.`part`;
> {code}
> Result
> {code}
> +-------------+--+
> | row_key | data |
> +-------------+--+
> | [B@381ea162 | {"p_brand":"QnJhbmQjNDU=","p_comment":"aW5hbCBkZXBvc2l0cy4gY2FyZWY=","p_container":"TEcgQk9Y","p_mfgr":"TWFudWZhY3R1cmVyIzQ=","p_name":"cG93ZGVyIGJyb3duIHNhbG1vbiBzZWFzaGVsbCBkaW0=","p_partkey":"OTk5OQ==","p_retailprice":"MTkwOC45OQ==","p_size":"OA==","p_type":"TEFSR0UgUE9MSVNIRUQgU1RFRUw="} |
> {code}
> 3) Consider the following query -
> {code}
> select * from hbase.`part` as t order by t.data.p_name;
> {code}
> Expected
> The query should return row_key, and all the columns in 'data' column family ordered by column 'data.p_name'
> Actual
> {code}
> +--------------+--------------------------------------------------------+
> |   row_key    |                          data                          |
> +--------------+--------------------------------------------------------+
> | [B@1bfcb7b6  | {"p_name":"eWVsbG93IHdoaXRlIHRhbiBraGFraSBzYWRkbGU="}  |
> +--------------+--------------------------------------------------------+
> {code}
> Result contains only the row_key and column data.p_name, order by data.p_name



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)