drill-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bridg...@apache.org
Subject [3/4] drill git commit: hide rowkey filter pushdown
Date Tue, 08 Sep 2015 23:44:11 GMT
hide rowkey filter pushdown


Project: http://git-wip-us.apache.org/repos/asf/drill/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/da949f12
Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/da949f12
Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/da949f12

Branch: refs/heads/gh-pages
Commit: da949f12b658542fbf2f8a961ce38797d51d3154
Parents: dae0b0c
Author: Kristine Hahn <khahn@maprtech.com>
Authored: Fri Sep 4 17:53:10 2015 -0700
Committer: Kristine Hahn <khahn@maprtech.com>
Committed: Fri Sep 4 18:32:28 2015 -0700

----------------------------------------------------------------------
 _docs/query-data/030-querying-hbase.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/drill/blob/da949f12/_docs/query-data/030-querying-hbase.md
----------------------------------------------------------------------
diff --git a/_docs/query-data/030-querying-hbase.md b/_docs/query-data/030-querying-hbase.md
index 8b4009f..da7cb85 100644
--- a/_docs/query-data/030-querying-hbase.md
+++ b/_docs/query-data/030-querying-hbase.md
@@ -2,7 +2,7 @@
 title: "Querying HBase"
 parent: "Query Data"
 ---
-To use Drill to query HBase data, you need to understand how to work with the HBase byte
arrays. If you want Drill to interpret the underlying HBase row key as something other than
a byte array, you need to know the encoding of the data in HBase. By default, HBase stores
data in little endian and Drill assumes the data is little endian, which is unsorted. The
following table shows the sorting of typical rowkey IDs in bytes, encoded in little endian
and big endian, respectively:
+<!-- To use Drill to query HBase data, you need to understand how to work with the HBase
byte arrays. If you want Drill to interpret the underlying HBase row key as something other
than a byte array, you need to know the encoding of the data in HBase. By default, HBase stores
data in little endian and Drill assumes the data is little endian, which is unsorted. The
following table shows the sorting of typical rowkey IDs in bytes, encoded in little endian
and big endian, respectively:
 
 | IDs in Byte Notation Little Endian Sorting | IDs in Decimal Notation | IDs in Byte Notation
Big Endian Sorting | IDs in Decimal Notation |
 |--------------------------------------------|-------------------------|-----------------------------------------|-------------------------|
@@ -76,7 +76,7 @@ By taking advantage of ordered byte encoding, Drill 1.2 and later can performant
 
 ## Querying Little Endian-Encoded Data
 
-As mentioned earlier, HBase stores data in little endian by default and Drill assumes the
data is encoded in little endian. This exercise involves working with data that is encoded
in little endian. First, you create two tables in HBase, students and clicks, that you can
query with Drill. You use the CONVERT_TO and CONVERT_FROM functions to convert binary text
to/from typed data. You use the CAST function to convert the binary data to an INT in step
4 of [Query HBase Tables]({{site.baseurl}}/docs/querying-hbase/#query-hbase-tables). When
converting an INT or BIGINT number, having a byte count in the destination/source that does
not match the byte count of the number in the binary source/destination, use CAST.
+As mentioned earlier,  -->HBase stores data in little endian by default and Drill assumes
the data is encoded in little endian. This exercise involves working with data that is encoded
in little endian. First, you create two tables in HBase, students and clicks, that you can
query with Drill. You use the CONVERT_TO and CONVERT_FROM functions to convert binary text
to/from typed data. You use the CAST function to convert the binary data to an INT in step
4 of [Query HBase Tables]({{site.baseurl}}/docs/querying-hbase/#query-hbase-tables). When
converting an INT or BIGINT number, having a byte count in the destination/source that does
not match the byte count of the number in the binary source/destination, use CAST.
 
 ### Create the HBase tables
 


Mime
View raw message