Another example of SQL mapping for portable serialization

A prospect suggests that we should add second example to https://docs.hazelcast.com/hazelcast/5.1/sql/mapping-to-maps with create mapping for portable - if you create mapping from a client with current example you are missing columns list. It is mentioned later in the documentation:
> If you omit a column list from the CREATE MAPPING statement, Hazelcast will resolve the column names and types by looking at the ClassDefinition with the given factory ID, class ID, and version.
> If the ClassDefinition with the given IDs is not known to the cluster, you must provide a column list so that Hazelcast can use it to create the ClassDefinition.

but another example would be nice.