OK, what I will do is implement custom byte array comparators that are Trafodion types aware and align format aware. Anyway I need these custom comparators to indicate from where to where to compare, and deal with several level of indirection and null logic. That is a better solution that shot gunning serialization deserialization when it is just overhead (when no predicate is being used for example). Eric
-----Original Message----- From: Anoop Sharma [mailto:[email protected]] Sent: Tuesday, April 12, 2016 11:27 AM To: [email protected] Subject: RE: align format and serialization It will be better to encode(serialize) the data, if needed, at the point where it is to be compared during pushdown. You will need to know the datatype and can call or use the code in encode function in exp_function.cpp. For simple types, encoding is straightforward. If not, data will have to be serialized during aligned row creation and deserialized after that. It would need some work to handle that properly. anoop -----Original Message----- From: Eric Owhadi [mailto:[email protected]] Sent: Tuesday, April 12, 2016 9:01 AM To: [email protected] Subject: align format and serialization Hi Trafodioneers, Investigating align format pushdown, I found that even if you ask to create columns serialized, in align format, the statement is ignored and forced to non serialized. I am assuming this is because we don’t support pushdown yet, so the code is smart enough to see that user is not using the serialized keyword appropriately. If we implement pushdown with align format, can we store data serialized inside align format? Or there are some things that will have problems? Eric
