danny0405 commented on issue #11568: [FLINK-16779][table] Add RAW type support in DDL and functions URL: https://github.com/apache/flink/pull/11568#issuecomment-610717631 > Thanks for your feedback @danny0405. We had these discussions last year while introducing FLIP-37 [1]. I hope that the description on top of all `LogicalType` classes could help clarify things as well. The RAW type is a complete black box type for Flink; thus `my_raw_object.abc` is not supported. This is available via row types, and user-defined structured types in the future. > > The object type that you linked is what the SQL standard calls "structured type". A type DDL for Flink is on the roadmap and it's great to see that Calcite added support for them recently. > > The RAW type is similar to a regular VARBINARY type, however, because this is Flink we still need to include Flink's serializer capabilities. A user should be able to define custom serialization logic. I think Oracle doesn't have this problem as they are fully in control how stuff is serialized. > > [1] https://docs.google.com/document/d/1a9HUb6OaBIoj9IRfbILcMFPrOL7ALeZ3rVI66dvA2_U/edit#heading=h.5qoorezffk0t Serialize/Deserialize is a point to support `RAW` type, but i still confused why we have to make the functionality into a SQL type, couldn't we also support all kinds of common se/de builtin functions or through UDF written by user to do the SE/DE thing ? I didn't see much difference and does not see strong reason why we have to roll in a SE/DE into a data type.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
