Adjustment of InfluxDBWriter to Support Version 3
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 616
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Is your feature request related to a problem? Please describe.
With the new release of InfluxDB 3 and Enterprise there might be the need for some adjustments in both writers or maybe to create a new one.
Describe the solution you'd like
As InfluxDB 3 is going back to the InfluxQL Model it might be more suitable to update the InfluxDB Writer v1 then to rely on the backward compatibility to use the influxdbwriter v2.
As i guess a lot has changed with the release of version 3 it might be useful to update those as well.
Describe alternatives you've considered
Create a new feature for Version 3 ?
This depends more on how heavy the updates on Version 1/2 are or if it is more feasable to write a new exporter.
More Context
This stems from customer requests which are requesting an up2date influxdb 3 support.
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
No files, tests, or entry points are named. Start by locating the InfluxDB Writer v1 and v2 implementations and reviewing InfluxDB 3 and Enterprise compatibility requirements; done requires deciding whether to update an existing writer or create a new exporter, then implementing and validating that support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100