Feature request: Option to relax name validation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 232
- PR merge metrics
- No merged PRs in 30d
Description
Currently, I can't process in goavro data produced by an old Java application that uses Avro 1.8 library, because schema validation dies with:
Record ought to have valid name: schema name ought to have second and remaining characters contain only [A-Za-z0-9_]: Event$
Indeed, schema begins with:
{
"type": "record",
"name": "CreateEvent",
"namespace": "org.apache.hadoop.hdfs.inotify.Event$",
Would it be possible to relax name validation via an option? I see there is an exported variable RelaxedNameValidation, but that one only applies for the first component, and only when the first component is empty.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the schema name-validation path and reviewing the exported RelaxedNameValidation variable. Confirm how validation currently handles namespace components and define the option's intended scope from the reported Event$ example. Done means callers can opt into the relaxed behavior without changing default validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100