timestamp logical types from numerical types
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 232
- PR merge metrics
- No merged PRs in 30d
Description
Currently, if I try to convert an `int` in a native golang type to a `timestamp-millis` in AVRO, I get an error. It seems like only `time.Time` can be converted to `timestamp-millis`. This seems quite restrictive, as all the numeric types should be able to be coerced to `int64` and then to `timestamp-millis`.
I have a fix for this, would you be amenable to a PR for this behaviour?
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 locating the AVRO logical-type conversion path for timestamp-millis and the handling of time.Time versus numeric native Go values. Review any nearby conversion tests, then confirm that the supported numeric types are accepted and that existing timestamp behavior remains covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100