You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2009/09/01 21:02:32 UTC
[jira] Created: (HBASE-1808) [stargate] fix how columns are
specified for scanners
[stargate] fix how columns are specified for scanners
-----------------------------------------------------
Key: HBASE-1808
URL: https://issues.apache.org/jira/browse/HBASE-1808
Project: Hadoop HBase
Issue Type: Improvement
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.21.0
The XSD for Scanner is:
{code}
<complexType name="Scanner">
<attribute name="startRow" type="base64Binary"/>
<attribute name="endRow" type="base64Binary"/>
<attribute name="columns" type="base64Binary"/>
<attribute name="batch" type="int"/>
<attribute name="startTime" type="int"/>
<attribute name="endTime" type="int"/>
</complexType>
{code}
The semantics of 'columns' is a space separated list of columns, which is then Base64 encoded. This doesn't actually make much sense, a partial effort to support binary keys but with a fixed delimiter which defeats the purpose. Rework the Scanner specification so 'columns' is an array.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1808) [stargate] fix how columns are
specified for scanners
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754352#action_12754352 ]
stack commented on HBASE-1808:
------------------------------
+1 on patch. Didn't try code but it looks right. The change in schema is distinct improvement I'd say.
> [stargate] fix how columns are specified for scanners
> -----------------------------------------------------
>
> Key: HBASE-1808
> URL: https://issues.apache.org/jira/browse/HBASE-1808
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.20.0
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.20.1, 0.21.0
>
> Attachments: HBASE-1808.patch
>
>
> The XSD for Scanner is:
> {code}
> <complexType name="Scanner">
> <attribute name="startRow" type="base64Binary"/>
> <attribute name="endRow" type="base64Binary"/>
> <attribute name="columns" type="base64Binary"/>
> <attribute name="batch" type="int"/>
> <attribute name="startTime" type="int"/>
> <attribute name="endTime" type="int"/>
> </complexType>
> {code}
> The semantics of 'columns' is a space separated list of columns, which is then Base64 encoded. This doesn't actually make much sense, a partial effort to support binary keys but with a fixed delimiter which defeats the purpose. Rework the Scanner specification so 'columns' is an array.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1808) [stargate] fix how columns are
specified for scanners
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-1808:
----------------------------------
Fix Version/s: 0.20.1
Affects Version/s: 0.20.0
Status: Patch Available (was: Open)
The XSD for Scanner is now
{code}
<complexType name="Scanner">
<sequence>
<element name="column" type="base64Binary" minoccurs="0" maxOccurs="unbounded" />
</sequence>
<attribute name="startRow" type="base64Binary"/>
<attribute name="endRow" type="base64Binary"/>
<attribute name="batch" type="int"/>
<attribute name="startTime" type="int"/>
<attribute name="endTime" type="int"/>
</complexType>
{code}
The protobuf encoding option is unaffected.
> [stargate] fix how columns are specified for scanners
> -----------------------------------------------------
>
> Key: HBASE-1808
> URL: https://issues.apache.org/jira/browse/HBASE-1808
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.20.0
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.20.1, 0.21.0
>
> Attachments: HBASE-1808.patch
>
>
> The XSD for Scanner is:
> {code}
> <complexType name="Scanner">
> <attribute name="startRow" type="base64Binary"/>
> <attribute name="endRow" type="base64Binary"/>
> <attribute name="columns" type="base64Binary"/>
> <attribute name="batch" type="int"/>
> <attribute name="startTime" type="int"/>
> <attribute name="endTime" type="int"/>
> </complexType>
> {code}
> The semantics of 'columns' is a space separated list of columns, which is then Base64 encoded. This doesn't actually make much sense, a partial effort to support binary keys but with a fixed delimiter which defeats the purpose. Rework the Scanner specification so 'columns' is an array.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1808) [stargate] fix how columns are
specified for scanners
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-1808:
----------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Committed to branch and trunk.
> [stargate] fix how columns are specified for scanners
> -----------------------------------------------------
>
> Key: HBASE-1808
> URL: https://issues.apache.org/jira/browse/HBASE-1808
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.20.0
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.20.1, 0.21.0
>
> Attachments: HBASE-1808.patch
>
>
> The XSD for Scanner is:
> {code}
> <complexType name="Scanner">
> <attribute name="startRow" type="base64Binary"/>
> <attribute name="endRow" type="base64Binary"/>
> <attribute name="columns" type="base64Binary"/>
> <attribute name="batch" type="int"/>
> <attribute name="startTime" type="int"/>
> <attribute name="endTime" type="int"/>
> </complexType>
> {code}
> The semantics of 'columns' is a space separated list of columns, which is then Base64 encoded. This doesn't actually make much sense, a partial effort to support binary keys but with a fixed delimiter which defeats the purpose. Rework the Scanner specification so 'columns' is an array.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1808) [stargate] fix how columns are
specified for scanners
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-1808:
----------------------------------
Attachment: HBASE-1808.patch
> [stargate] fix how columns are specified for scanners
> -----------------------------------------------------
>
> Key: HBASE-1808
> URL: https://issues.apache.org/jira/browse/HBASE-1808
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.20.0
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.20.1, 0.21.0
>
> Attachments: HBASE-1808.patch
>
>
> The XSD for Scanner is:
> {code}
> <complexType name="Scanner">
> <attribute name="startRow" type="base64Binary"/>
> <attribute name="endRow" type="base64Binary"/>
> <attribute name="columns" type="base64Binary"/>
> <attribute name="batch" type="int"/>
> <attribute name="startTime" type="int"/>
> <attribute name="endTime" type="int"/>
> </complexType>
> {code}
> The semantics of 'columns' is a space separated list of columns, which is then Base64 encoded. This doesn't actually make much sense, a partial effort to support binary keys but with a fixed delimiter which defeats the purpose. Rework the Scanner specification so 'columns' is an array.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.