Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 24 Feb 2015 07:46:12 +0000 (UTC)
From: "Steven Phillips (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12754635.1415752209000.119932.1424763972233@Atlassian.JIRA>
In-Reply-To: <JIRA.12754635.1415752209000@Atlassian.JIRA>
References: <JIRA.12754635.1415752209000@Atlassian.JIRA>
 <JIRA.12754635.1415752209601@arcas>
Subject: [jira] [Updated] (DRILL-1690) Issue with using HBase plugin to
 access row_key only
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Steven Phillips updated DRILL-1690:
-----------------------------------
    Fix Version/s:     (was: 0.8.0)
                   0.9.0

> Issue with using HBase plugin to access row_key only
> ----------------------------------------------------
>
>                 Key: DRILL-1690
>                 URL: https://issues.apache.org/jira/browse/DRILL-1690
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - HBase
>            Reporter: Chun Chang
>            Assignee: Aditya Kishore
>            Priority: Critical
>             Fix For: 0.9.0
>
>
> #Thu Nov 06 11:38:17 PST 2014
> git.commit.id.abbrev=eeb7160
> Configure an HBase plugin to access MapRDB table. When, select the row key only, we return two columns:
> 0: jdbc:drill:schema=M7> select row_key, fivecf from m7student limit 2;
> +------------+------------+
> |  row_key   |   fivecf   |
> +------------+------------+
> | [B@31966bd8 | {"create_date":"MjAxNC0wNS0yNyAwMDoyNjowNw=="} |
> | [B@a824b57 | {"create_date":"MjAxNC0wMy0yNCAyMTo1NzozMw=="} |
> +------------+------------+
> 2 rows selected (0.128 seconds)
> 0: jdbc:drill:schema=M7> select row_key from m7student limit 2;
> +------------+------------+
> |  row_key   |   fivecf   |
> +------------+------------+
> | [B@2560bab1 | {"create_date":"MjAxNC0wNS0yNyAwMDoyNjowNw=="} |
> | [B@7180cda2 | {"create_date":"MjAxNC0wMy0yNCAyMTo1NzozMw=="} |
> +------------+------------+
> 2 rows selected (0.107 seconds)
> Here is the plan:
> 0: jdbc:drill:schema=M7> explain plan for select row_key from m7student limit 2;
> +------------+------------+
> |    text    |    json    |
> +------------+------------+
> | 00-00    Screen
> 00-01      SelectionVectorRemover
> 00-02        Limit(fetch=[2])
> 00-03          Scan(groupscan=[HBaseGroupScan [HBaseScanSpec=HBaseScanSpec [tableName=m7student, startRow=null, stopRow=null, filter=null], columns=[SchemaPath [`row_key`]]]])
>  | {
>   "head" : {
>     "version" : 1,
>     "generator" : {
>       "type" : "ExplainHandler",
>       "info" : ""
>     },
>     "type" : "APACHE_DRILL_PHYSICAL",
>     "options" : [ ],
>     "queue" : 0,
>     "resultMode" : "EXEC"
>   },
>   "graph" : [ {
>     "pop" : "hbase-scan",
>     "@id" : 3,
>     "hbaseScanSpec" : {
>       "tableName" : "m7student",
>       "startRow" : "",
>       "stopRow" : "",
>       "serializedFilter" : null
>     },
>     "storage" : {
>       "type" : "hbase",
>       "config" : {
>         "hbase.table.namespace.mappings" : "*:/test/tables"
>       },
>       "size.calculator.enabled" : false,
>       "enabled" : true
>     },
>     "columns" : [ "`row_key`" ],
>     "cost" : 1048576.0
>   }, {
>     "pop" : "limit",
>     "@id" : 2,
>     "child" : 3,
>     "first" : 0,
>     "last" : 2,
>     "initialAllocation" : 1000000,
>     "maxAllocation" : 10000000000,
>     "cost" : 1048576.0
>   }, {
>     "pop" : "selection-vector-remover",
>     "@id" : 1,
>     "child" : 2,
>     "initialAllocation" : 1000000,
>     "maxAllocation" : 10000000000,
>     "cost" : 1048576.0
>   }, {
>     "pop" : "screen",
>     "@id" : 0,
>     "child" : 1,
>     "initialAllocation" : 1000000,
>     "maxAllocation" : 10000000000,
>     "cost" : 1048576.0
>   } ]
> } |
> +------------+------------+
> Drill should strip out the second column.


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