influxdata / influxdata/influxdb-client-java

Wrong column type when use wildcard with @Measurement

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

Nobody has claimed this yet.

Dominant language
Java
Stars
477
Forks
129
PR merge metrics
No merged PRs in 30d

Description

Steps to reproduce:

@Getter
public abstract class InfluxDbDefaultPoint<T> {

    @Column(timestamp = true)
    private final Instant time;
    @Column(tag = true)
    private final Long deviceId;
    @Column
    private final T value;

    public InfluxDbDefaultPoint(final Long deviceId, final T value) {
        this.time = Instant.now();
        this.deviceId = deviceId;
        this.value = value;
    }
}

@Measurement(name = "temperature")
public class InfluxDbTemperaturePoint extends InfluxDbDefaultPoint<Double> {

    public InfluxDbTemperaturePoint(Long deviceId, Double value) {
        super(deviceId, value);
    }
}

public static void main(String[] args) {
        final InfluxDBClient database = InfluxDBClientFactory.create("http://localhost:8200","<token>".toCharArray(),"<org>","<bucket>");
        database.getWriteApiBlocking().writeMeasurement(WritePrecision.S, new InfluxDbTemperaturePoint(0L,30.0));
    }

When I try to send such a prepared model to influxdb, I get an error: HTTP status code: 422; Message: failure writing points to database: partial write: field type conflict: input field "value" on measurement "temperature" is type string, already exists as type float dropped=1.

Previously I had an InfluxDbTemperaturePoint object without wildcard and it worked fine - it saved double

Expected behavior:
It should save the value 30.0 as float/dobule.

Actual behavior:
It tries to save the value 30.0 as a string.

Specifications:

  • Client Version: 6.9.0
  • InfluxDB Version: v2.7.1
  • JDK Version: Java(TM) SE Runtime Environment (build 19.0.2+7-44)
  • Platform: Windows

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 reproducing the issue with the @Measurement, @Column, InfluxDbDefaultPoint, and InfluxDbTemperaturePoint example through writeMeasurement. Trace how the wildcard generic field value is classified before serialization, then verify that 30.0 is written as a numeric field rather than a string without breaking the non-wildcard case.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.