[TRAFODION-1864] LONGWVARCHAR column support have problems with storage of the column in hbase

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-incubating
• Component/s: sql-cmp, sql-exe
• Assignee: Sandhya Sundaresan
• Reporter: Selvaganesan Govindarajan
• Created: 01/Mar/16 19:18
• Updated: 15/Sep/18 07:31
• Resolved: 12/May/16 20:34

Description

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