apache / apache/cassandra-gocql-driver
metadata: handle UDT types correctly
Open
enhancement
- Dominant language
- Go
- Stars
- 2.7k
- Forks
- 658
- PR merge metrics
- No merged PRs in 30d
Description
Currently UDT's will be parsed into NativeType{typ: TypeCustom} which is wrong, we should read the types from system_schemas.types and then create a UDTType from that.
Contributor guide
Research direction
Start by tracing the metadata parsing path that currently produces NativeType{typ: TypeCustom}, then read system_schemas.types and the existing UDTType representation. Verify the change with coverage for UDT metadata, ensuring UDTs are represented as UDTType rather than NativeType.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100