it encodes columns before writing them to hbase so they could be used by hbase to compare as bytes. Helps with pushdown of preds. If this option is not specified, then column values are written as it. Default is SERIALIZATION ON.
On read, we decode it back to its original value. Same kind of encoding that we do for key columns. Code is in exp/exp_function.cpp where it deals with encoding and decoding. anoop -----Original Message----- From: Eric Owhadi [mailto:[email protected]] Sent: Tuesday, October 27, 2015 10:23 AM To: [email protected] Subject: RE: SERIALIZED option on columns And what is the semantic? Is it just to say that this should not be in aligned format in a mix format mode? Or is there more to it? Eric -----Original Message----- From: Anoop Sharma [mailto:[email protected]] Sent: Tuesday, October 27, 2015 12:17 PM To: [email protected] Subject: RE: SERIALIZED option on columns Yes, it is a new option in trafodion. It was just enabled as default. We can update documentation about it. anoop -----Original Message----- From: Eric Owhadi [mailto:[email protected]] Sent: Tuesday, October 27, 2015 10:15 AM To: [email protected] Subject: SERIALIZED option on columns Hi all, I am trying to understand predicate push down code. There is reference to columns tagged “serialized”. So I went on the SQL reference manual looking for what was the semantic of this tag. Could not find a single hit on “Serialized” keyword. Is that a new feature? Or is the documentation needing an update? I can open a Jira on documentation if needed? Eric
