Support for "custom" types after CASSANDRA-10365

Description

After CASSANDRA-10365, schema column types are expressed as CQL types and parsed with DataTypeCqlNameParser.

As it happens, this doesn't work if a column is created with a "custom" type, e.g.:

In this case, the column type for c is still expressed as Cassandra internal class names.

Environment

None

Pull Requests

None
Fixed

Assignee

Unassigned

Reporter

Alexandre Dutra

Labels

None

PM Priority

None

Reproduced in

None

Affects versions

Fix versions

Pull Request

None

Doc Impact

None

Size

S

External issue ID

None

External issue ID

None

Priority

Minor
Configure