[jira] Created: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

classic Classic list List threaded Threaded
35 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
[Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
--------------------------------------------------------------------------------------------

                 Key: HADOOP-2329
                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
             Project: Hadoop
          Issue Type: New Feature
          Components: contrib/hbase
    Affects Versions: 0.16.0
            Reporter: Edward Yoon
            Assignee: Edward Yoon
             Fix For: 0.16.0


A built-in data type is a fundamental data type that the hbase shell defines.
(character strings, scalars, ranges, arrays, ... , etc)

If you need a specialized data type that is not currently provided as a built-in type,
you are encouraged to write your own user-defined data type using UDF(not yet implemented).
(or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Work started: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org

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

Work on HADOOP-2329 started by Edward Yoon.

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDF(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Edward Yoon updated HADOOP-2329:
--------------------------------

    Description:
A built-in data type is a fundamental data type that the hbase shell defines.
(character strings, scalars, ranges, arrays, ... , etc)

If you need a specialized data type that is not currently provided as a built-in type,
you are encouraged to write your own user-defined data type using UDC(not yet implemented).
(or contribute it for distribution in a future release of hbase shell)

  was:
A built-in data type is a fundamental data type that the hbase shell defines.
(character strings, scalars, ranges, arrays, ... , etc)

If you need a specialized data type that is not currently provided as a built-in type,
you are encouraged to write your own user-defined data type using UDF(not yet implemented).
(or contribute it for distribution in a future release of hbase shell)


> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547597 ]

Edward Yoon commented on HADOOP-2329:
-------------------------------------

- { Create, Insert, Update } Syntax will be changed.

Built-In Data Types
||Data Type||Explanation||
|BOOLEAN|Stores the Boolean values for true and false|
|BYTE|Stores binary data that are not random access|
|DECIMAL|Stores numbers with definable scale and precision|
|INT|Is a synonym for INTEGER|
|INT8|Stores an 8-byte integer value These whole numbers can be in the range -(263-1) to 263-1|
|INTEGER|Stores a span of time|
|REAL|Is a synonym for SMALLFLOAT|
|SERIAL|Stores sequential integers; has the same range of values as INTEGER|
|SERIAL8|Stores large sequential integers; has the same range of values as INT8|
|TEXT|Stores text data in chunks that are not random access|

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDF(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Issue Comment Edited: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547597 ]

udanax edited comment on HADOOP-2329 at 12/2/07 2:28 AM:
--------------------------------------------------------------

- { Create, Insert, Update } Syntax will be changed.

Built-In Data Types
||Data Type||Explanation||
|BOOLEAN|Stores the Boolean values for true and false|
|BYTE|Stores binary data that are not random access|
|CHAR(*n*)|Stores single-byte or multibyte sequences of characters, including letters, numbers, and symbols of fixed length Collation is code-set dependent|
|VARCHAR(*m*,*r*)|Stores single-byte or multibyte strings of letters, numbers, and symbols of varying length to a maximum of 255 bytes Collation is code-set dependent|
|DECIMAL|Stores numbers with definable scale and precision|
|INTEGER or INT|Stores a span of time|
|SMALLINT|Stores whole numbers from -(215-1) to 215-1|
|INT8|Stores an 8-byte integer value These whole numbers can be in the range -(263-1) to 263-1|
|SERIAL|Stores sequential integers; has the same range of values as INTEGER|
|SERIAL8|Stores large sequential integers; has the same range of values as INT8|
|TEXT|Stores text data in chunks that are not random access|

      was (Author: udanax):
    - { Create, Insert, Update } Syntax will be changed.

Built-In Data Types
||Data Type||Explanation||
|BOOLEAN|Stores the Boolean values for true and false|
|BYTE|Stores binary data that are not random access|
|DECIMAL|Stores numbers with definable scale and precision|
|INT|Is a synonym for INTEGER|
|INT8|Stores an 8-byte integer value These whole numbers can be in the range -(263-1) to 263-1|
|INTEGER|Stores a span of time|
|REAL|Is a synonym for SMALLFLOAT|
|SERIAL|Stores sequential integers; has the same range of values as INTEGER|
|SERIAL8|Stores large sequential integers; has the same range of values as INT8|
|TEXT|Stores text data in chunks that are not random access|
 

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547703 ]

Edward Yoon commented on HADOOP-2329:
-------------------------------------

Let's see the integer value example.
{code}
int integer = 123456789;

ByteBuffer buff = ByteBuffer.allocate(Integer.SIZE / 8);
buff.putInt(integer);
buff.order(ByteOrder.BIG_ENDIAN);

1: table.put(lockId, column, buff.array());
2: table.put(lockId, column, "123456789".getBytes());
{code}

4 bytes vs 9 bytes.
Nine is the almost double of four.

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Issue Comment Edited: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547597 ]

udanax edited comment on HADOOP-2329 at 12/2/07 4:47 PM:
--------------------------------------------------------------

- { Create, Insert, Update } Syntax will be changed.

Built-In Data Types
||Data Type||Explanation||
|BOOLEAN|Stores the Boolean values for true and false|
|BYTE|Stores binary data that are not random access|
|CHAR(*n*)|Stores single-byte or multibyte sequences of characters, including letters, numbers, and symbols of fixed length Collation is code-set dependent|
|VARCHAR(*m*,*r*)|Stores single-byte or multibyte strings of letters, numbers, and symbols of varying length to a maximum of 255 bytes Collation is code-set dependent|
|DECIMAL|Stores numbers with definable scale and precision|
|INTEGER or INT|Stores whole numbers from -(231-1) to 231-1|
|SMALLINT|Stores whole numbers from -(215-1) to 215-1|
|INT8|Stores an 8-byte integer value These whole numbers can be in the range -(263-1) to 263-1|
|SERIAL|Stores sequential integers; has the same range of values as INTEGER|
|SERIAL8|Stores large sequential integers; has the same range of values as INT8|
|TEXT|Stores text data in chunks that are not random access|

      was (Author: udanax):
    - { Create, Insert, Update } Syntax will be changed.

Built-In Data Types
||Data Type||Explanation||
|BOOLEAN|Stores the Boolean values for true and false|
|BYTE|Stores binary data that are not random access|
|CHAR(*n*)|Stores single-byte or multibyte sequences of characters, including letters, numbers, and symbols of fixed length Collation is code-set dependent|
|VARCHAR(*m*,*r*)|Stores single-byte or multibyte strings of letters, numbers, and symbols of varying length to a maximum of 255 bytes Collation is code-set dependent|
|DECIMAL|Stores numbers with definable scale and precision|
|INTEGER or INT|Stores a span of time|
|SMALLINT|Stores whole numbers from -(215-1) to 215-1|
|INT8|Stores an 8-byte integer value These whole numbers can be in the range -(263-1) to 263-1|
|SERIAL|Stores sequential integers; has the same range of values as INTEGER|
|SERIAL8|Stores large sequential integers; has the same range of values as INT8|
|TEXT|Stores text data in chunks that are not random access|
 

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Issue Comment Edited: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547597 ]

udanax edited comment on HADOOP-2329 at 12/2/07 4:50 PM:
--------------------------------------------------------------

- { Create, Insert, Select } Syntax and Codes will be changed.

Built-In Data Types
||Data Type||Explanation||
|BOOLEAN|Stores the Boolean values for true and false|
|BYTE|Stores binary data that are not random access|
|CHAR(*n*)|Stores single-byte or multibyte sequences of characters, including letters, numbers, and symbols of fixed length Collation is code-set dependent|
|VARCHAR(*m*,*r*)|Stores single-byte or multibyte strings of letters, numbers, and symbols of varying length to a maximum of 255 bytes Collation is code-set dependent|
|DECIMAL|Stores numbers with definable scale and precision|
|INTEGER or INT|Stores whole numbers from -(2 ^31^ -1) to 2 ^31^ -1|
|SMALLINT|Stores whole numbers from -(2 ^15^ -1) to 2 ^15^ -1|
|INT8|Stores an 8-byte integer value These whole numbers can be in the range -(2 ^63^ -1) to 2 ^63^ -1|
|SERIAL|Stores sequential integers; has the same range of values as INTEGER|
|SERIAL8|Stores large sequential integers; has the same range of values as INT8|
|TEXT|Stores text data in chunks that are not random access|

      was (Author: udanax):
    - { Create, Insert, Select } Syntax and Codes will be changed.

Built-In Data Types
||Data Type||Explanation||
|BOOLEAN|Stores the Boolean values for true and false|
|BYTE|Stores binary data that are not random access|
|CHAR(*n*)|Stores single-byte or multibyte sequences of characters, including letters, numbers, and symbols of fixed length Collation is code-set dependent|
|VARCHAR(*m*,*r*)|Stores single-byte or multibyte strings of letters, numbers, and symbols of varying length to a maximum of 255 bytes Collation is code-set dependent|
|DECIMAL|Stores numbers with definable scale and precision|
|INTEGER or INT|Stores whole numbers from -(2^31^-1) to 2^31^-1|
|SMALLINT|Stores whole numbers from -(2^15^-1) to 2^15^-1|
|INT8|Stores an 8-byte integer value These whole numbers can be in the range -(2^63^-1) to 2^63^-1|
|SERIAL|Stores sequential integers; has the same range of values as INTEGER|
|SERIAL8|Stores large sequential integers; has the same range of values as INT8|
|TEXT|Stores text data in chunks that are not random access|
 

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Issue Comment Edited: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547597 ]

udanax edited comment on HADOOP-2329 at 12/2/07 4:49 PM:
--------------------------------------------------------------

- { Create, Insert, Select } Syntax and Codes will be changed.

Built-In Data Types
||Data Type||Explanation||
|BOOLEAN|Stores the Boolean values for true and false|
|BYTE|Stores binary data that are not random access|
|CHAR(*n*)|Stores single-byte or multibyte sequences of characters, including letters, numbers, and symbols of fixed length Collation is code-set dependent|
|VARCHAR(*m*,*r*)|Stores single-byte or multibyte strings of letters, numbers, and symbols of varying length to a maximum of 255 bytes Collation is code-set dependent|
|DECIMAL|Stores numbers with definable scale and precision|
|INTEGER or INT|Stores whole numbers from -(2^31^-1) to 2^31^-1|
|SMALLINT|Stores whole numbers from -(2^15^-1) to 2^15^-1|
|INT8|Stores an 8-byte integer value These whole numbers can be in the range -(2^63^-1) to 2^63^-1|
|SERIAL|Stores sequential integers; has the same range of values as INTEGER|
|SERIAL8|Stores large sequential integers; has the same range of values as INT8|
|TEXT|Stores text data in chunks that are not random access|

      was (Author: udanax):
    - { Create, Insert, Update } Syntax will be changed.

Built-In Data Types
||Data Type||Explanation||
|BOOLEAN|Stores the Boolean values for true and false|
|BYTE|Stores binary data that are not random access|
|CHAR(*n*)|Stores single-byte or multibyte sequences of characters, including letters, numbers, and symbols of fixed length Collation is code-set dependent|
|VARCHAR(*m*,*r*)|Stores single-byte or multibyte strings of letters, numbers, and symbols of varying length to a maximum of 255 bytes Collation is code-set dependent|
|DECIMAL|Stores numbers with definable scale and precision|
|INTEGER or INT|Stores whole numbers from -(231-1) to 231-1|
|SMALLINT|Stores whole numbers from -(215-1) to 215-1|
|INT8|Stores an 8-byte integer value These whole numbers can be in the range -(263-1) to 263-1|
|SERIAL|Stores sequential integers; has the same range of values as INTEGER|
|SERIAL8|Stores large sequential integers; has the same range of values as INT8|
|TEXT|Stores text data in chunks that are not random access|
 

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547710 ]

Edward Yoon commented on HADOOP-2329:
-------------------------------------

I'd like to add the type information to column descriptor.
Let folks add either arbitrary values or built-in data types to Cell.

Any Comments are welcome.

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547728 ]

Edward Yoon commented on HADOOP-2329:
-------------------------------------

I think this option effects all columns in columnfamily.
It make generalizations about columns in columnfamily.
Is it problem?
I don't think so, We can just use the current byte[] type.

{code}
Insert into table (String, String) values ('stirng value', '3');
Insert into table (String, Integer) values ('stirng value', 3);
{code}

So, It doen't matter.

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548012 ]

Jim Kellerman commented on HADOOP-2329:
---------------------------------------

-1

Adding value types to the HBase server side is not a good idea. Since members of a column family can be created on an ad-hoc basis, there would be a lot of bookkeeping to do to determine if the family member should be of a particular type. And if there were no data about a particular family member, what type should it be?

It would be unacceptable to force all members of a column family to be the same type.

Additionally there have been requests to loosen the restrictions on the row key being a Text and instead, accepting any WritableComparable as the row key.

HADOOP-2197 would permit applications to tag columns with arbitrary key/value pairs. Thus an application could store family member/type information using this mechanism.

Bigtable is typeless and I think HBase should be as well.

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548017 ]

Edward Yoon commented on HADOOP-2329:
-------------------------------------

>> HADOOP-2197 would permit applications to tag columns with arbitrary key/value pairs. Thus an application could store family member/type information using this mechanism.

ugh... ok!

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548543 ]

Bryan Duxbury commented on HADOOP-2329:
---------------------------------------

If there's a good alternative already in the works, can we close this issue?

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548546 ]

Edward Yoon commented on HADOOP-2329:
-------------------------------------

I don't think so.
Shell can't handle type even if there's a good alternative already in the works.

This issue is exist for shell.


> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548547 ]

Edward Yoon commented on HADOOP-2329:
-------------------------------------

It will be clarify the scope of various operations.

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548558 ]

Edward Yoon commented on HADOOP-2329:
-------------------------------------

Above comment means... "I didn't said that Hbase should provides built-in data type."

Let's see the example.

Some DB solutions can be provide only byte[] data type.
And then, ... listen to their slogan.. "you can stores own arbitrary data type. look!! this is awesome flexible DB solution. Let's make your own datum and data types. ".....
We can think about why they didn't...

Also, i think it is not makes any problem.
It just makes user can choice, so we can provides convenience.

only byte[] VS { integer or character or byte[] or .... , etc}

It means that each user shouldn't make general built-in data type at everytime.

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Issue Comment Edited: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548558 ]

udanax edited comment on HADOOP-2329 at 12/4/07 11:06 PM:
---------------------------------------------------------------

Above comment means... "I didn't said that Hbase should provides built-in data type."

Let's see the example.

Some DB solutions can be provide only byte[] data type.
And then, ... listen to their slogan.. "you can stores own arbitrary data type. look!! this is awesome flexible DB solution. Let's make your own datum and data types. ".....
We can think about why they didn't...

Also, i think it is not makes any problem.
It just makes user can choice, so we can provides convenience.

only byte[] VS { integer or character or byte[] or .... , etc}

It means that each user needn't develop the exist built-in data type in everytime.

      was (Author: udanax):
    Above comment means... "I didn't said that Hbase should provides built-in data type."

Let's see the example.

Some DB solutions can be provide only byte[] data type.
And then, ... listen to their slogan.. "you can stores own arbitrary data type. look!! this is awesome flexible DB solution. Let's make your own datum and data types. ".....
We can think about why they didn't...

Also, i think it is not makes any problem.
It just makes user can choice, so we can provides convenience.

only byte[] VS { integer or character or byte[] or .... , etc}

It means that each user shouldn't make general built-in data type at everytime.
 

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Issue Comment Edited: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548558 ]

udanax edited comment on HADOOP-2329 at 12/4/07 11:16 PM:
---------------------------------------------------------------

Above comment means... "I didn't said that Hbase should provides built-in data type."

Let's see the example.

Some DB solutions can be provide only byte[] data type.
And then, ... listen to their slogan.. "you can stores own arbitrary data type. look!! this is awesome flexible DB solution. Let's make your own datum and data types. ".....
We can think about why they didn't...

Also, i think it is not makes any problem.
It's just a function for the convenience of users.

# only byte[] VS { integer or character or byte[] or .... , etc}

It means that each user needn't develop for the provided built-in data type in everytime.

      was (Author: udanax):
    Above comment means... "I didn't said that Hbase should provides built-in data type."

Let's see the example.

Some DB solutions can be provide only byte[] data type.
And then, ... listen to their slogan.. "you can stores own arbitrary data type. look!! this is awesome flexible DB solution. Let's make your own datum and data types. ".....
We can think about why they didn't...

Also, i think it is not makes any problem.
It just makes user can choice, so we can provides convenience.

only byte[] VS { integer or character or byte[] or .... , etc}

It means that each user needn't develop the exist built-in data type in everytime.
 

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Issue Comment Edited: (HADOOP-2329) [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548558 ]

udanax edited comment on HADOOP-2329 at 12/4/07 11:47 PM:
---------------------------------------------------------------

Some DB solutions can be provide only byte[] data type.
And then, ... listen to their slogan.. "you can stores own arbitrary data type. look!! this is awesome flexible DB solution. Let's make your own datum and data types. ".....
We can think about why they didn't...

Let's view the matter.
Built-in Data Types does not interrupt the frexible because it's just a function for the convenience of users.

{code}
only byte[] VS { integer or character or byte[] or .... , etc}
{code}

It means that each time users needn't tiresome of develop the provided built-in data types.

      was (Author: udanax):
    Above comment means... "I didn't said that Hbase should provides built-in data type."

Let's see the example.

Some DB solutions can be provide only byte[] data type.
And then, ... listen to their slogan.. "you can stores own arbitrary data type. look!! this is awesome flexible DB solution. Let's make your own datum and data types. ".....
We can think about why they didn't...

Also, i think it is not makes any problem.
It's just a function for the convenience of users.

# only byte[] VS { integer or character or byte[] or .... , etc}

It means that each user needn't develop for the provided built-in data type in everytime.
 

> [Hbase Shell] Addition of Built-In Value Data Types for efficient accessing and stroing data
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2329
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Edward Yoon
>            Assignee: Edward Yoon
>             Fix For: 0.16.0
>
>
> A built-in data type is a fundamental data type that the hbase shell defines.
> (character strings, scalars, ranges, arrays, ... , etc)
> If you need a specialized data type that is not currently provided as a built-in type,
> you are encouraged to write your own user-defined data type using UDC(not yet implemented).
> (or contribute it for distribution in a future release of hbase shell)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

12