[TAJO-1360] VALUES_ field in OPTIONS table of catalog store should be longer.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.11.0, 0.10.1
• Component/s: Catalog
• Assignee: DaeMyung Kang
• Reporter: Hyunsik Choi
• Created: 27/Feb/15 05:54
• Updated: 03/Apr/15 02:41
• Resolved: 03/Apr/15 02:41

Description

Table properties for each table are maintained in OPTIONS table in catalog store. Each key and value for each table property use KEY_ and VALUE_ fields as follows:

CREATE TABLE OPTIONS (
  TID INT NOT NULL,
  KEY_ VARCHAR(255) BINARY NOT NULL,
  VALUE_ VARCHAR(255) NOT NULL,
  PRIMARY KEY (TID, KEY_),
  FOREIGN KEY (TID) REFERENCES TABLES (TID) ON DELETE CASCADE
)

Newly adopted Hbase storage uses the table property columns to maintain the column map between a HBase table and Tajo table. VALUE_ is likely to cause 'Data too long' exception because its maximum length is just 256.

So, we need to increase the maximum size. I think that 8000 would be proper because some RDBMSs supports VARCHAR types up to 8000 chars as far as I know.