influxdata / influxdata/influxdb
how line protocol support inserting empty tag value?
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Proposal:__
I want to migrate data to influxdb from other tsdb. Now I has some data with empty tag value, when wirte it to influxdb and query it, find that channel_name tag value is null. beflow is my test data:
```
{
"measurement": "mysql_slave_status_seconds_behind_master",
"fields": {
"value": 1
},
"tags": {
"channel_name": "",
"key": "1234",
}
}
```
__Current behavior:__
"" tag value inserted to influxdb, value is null
__Desired behavior:__
I desired aflter "" tag value inserted to influxdb, it's value is ""
__Use case:__
test data:
```
{
"measurement": "mysql_slave_status_seconds_behind_master",
"fields": {
"value": 1
},
"tags": {
"channel_name": "",
"key": "1234",
}
}
```
got line ptotocol: mysql_slave_status_seconds_behind_master,key=1234 value=1i
Contributor guide
Research direction
No implementation file or test is identified. Reproduce the supplied empty-tag example using InfluxDB's line protocol, then trace how the empty tag is represented during writing and querying. Done means agreeing on and verifying whether an empty tag value is preserved as "" rather than returned as null.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100