You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Sandhya Sundaresan (JIRA)" <ji...@apache.org> on 2016/05/12 20:34:12 UTC
[jira] [Assigned] (TRAFODION-1864) LONGWVARCHAR column support have
problems with storage of the column in hbase
[ https://issues.apache.org/jira/browse/TRAFODION-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandhya Sundaresan reassigned TRAFODION-1864:
---------------------------------------------
Assignee: Sandhya Sundaresan
> LONGWVARCHAR column support have problems with storage of the column in hbase
> -----------------------------------------------------------------------------
>
> Key: TRAFODION-1864
> URL: https://issues.apache.org/jira/browse/TRAFODION-1864
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-cmp, sql-exe
> Reporter: Selvaganesan Govindarajan
> Assignee: Sandhya Sundaresan
> Fix For: 2.0-incubating
>
>
> The LONGWVARCHAR is stored in hbase table as
> xF26S0\xB4VP\xE3 column=#1:\x02, timestamp=1456841088934, value=\x00t\x00o\x00d\x00a\x00y\x00
> But the omitted default value for this column would have 2 byte varchar indicator length prefix.
> I would think how the LONGWVARCHAR is stored in hbase table might be wrong because it can't be null terminated.
> The test case charsets/TEST012 now has a known diff file when this issue was exposed after merging PR 340
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)