influxdata / influxdata/influxdb-java

Fields sometimes null after retrieving QueryResult from InfluxDB

Open
#733 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
1.2k
Forks
469
PR merge metrics
No merged PRs in 30d

Description

Most of the time I'm able to successfully query my InfluxDB and convert the result to POJO without any issue. However, sometimes after getting the QueryResult , some of the property fields, for my object, in the QueryResult are null even though none of the fields are null/empty for that record in my InfluxDB measurement. This only happens to a few of the property fields too, not all of them. Why does this happen?

My Spring Boot application also receives many concurrent requests at any given moment, which makes me think this may be a multi-threading issue. Also my class has a `@Data` Lombok annotation if that is relevant during the POJO conversion. So far, a temporary solution is refetching the QueryResults a second time. During this second time, the fields are no longer null. I included an example below for my Transaction measurement and class/POJO

**Transaction measurement (in InfluxDB)**
Time: 1612283422708733547
Amount: 18.20
Status: Success

**POJO (in Spring Boot application after resultMapper.toPOJO)**
Time: 1612283422708733547
Amount: null
Status: null

Current logic in application

```
Query query = new Query(String.format(queryString, lastTimestamp), "transaction");
QueryResult queryResult = influxDB.query(query);
return resultMapper.toPOJO(queryResult, Transaction.class, TimeUnit.NANOSECONDS);
```

InfluxDB version: 1.8.3

Could this be related to #676 or #693 or #683 ?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the Query, QueryResult, and resultMapper.toPOJO path described in the issue, then inspect how concurrent requests are handled. Reproduce the intermittent null-field conversion with the Transaction example and InfluxDB 1.8.3; done means the cause is identified and populated fields are preserved during concurrent requests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot
Domain
backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.