Compatibility with Influx 3 API
Open
Nobody has claimed this yet.
Compatibility
ILP
New feature
REST API
- Dominant language
- Java
- Stars
- 17.3k
- Forks
- 1.6k
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 28
Description
Is your feature request related to a problem?
Influxdb3 uses all these endpoints for ingesting ILP
/write?db=mydb&precision=ns
/api/v2/write?bucket=mydb&precision=ns
/api/v3/write_lp?db=mydb&precision=ns&accept_partial=true
We should probably expose our current /api/v2/write endpoint also under /api/v3/write_lp. Also, if we receive now precision=auto on the endpoint, it fails
Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Full Name:
javier ramirez
Affiliation:
questdb
Additional context
No response
Contributor guide
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 handler and tests for the existing /api/v2/write endpoint. Compare its behavior with the InfluxDB 3 /api/v3/write_lp examples, including precision=auto and accept_partial=true. Done means the compatible endpoint is exposed and the supported precision behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100