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:
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.