influxdata / influxdata/influxdb-java

Using InfluxDBMapper w/o Annotations

Open
#802 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.2k
Forks
469
PR merge metrics
No merged PRs in 30d

Description

Hi,

We are in the situation where our POJOs get dynamically built. There can be 100's of them. It wouldn't be feasible to annotate them all. Also, when they get dynamically rebuilt we would have to re-annotate....

Is it possible to fallback to the class/field names if there are no annotations? FWIW Spring can do it via their WebClient object. Here is example code shown from https://www.baeldung.com/spring-webflux .

````
WebClient client = WebClient.create("http://localhost:8080");
Flux employeeFlux = client.get()
.uri("/employees")
.retrieve()
.bodyToFlux(Employee.class);
````

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating InfluxDBMapper and reading how it currently handles annotations for POJOs. Determine whether the requested fallback for dynamically built classes and fields can fit the existing mapping behavior, and identify where focused tests would belong. Done means the expected behavior for unannotated POJOs is defined and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.