influxdata / influxdata/influxdb

A mis-spelled column name causes the select to return no rows

Open
#14,111 5 comments 0 reactions 0 assignees View on GitHub
1.x area/influxql
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

__Steps to reproduce:__
1. Do a query with a spelling error in the column names
/usr/bin/influx -precision rfc3339 -database dsp_metrics -username x -password x
-execute 'select time, dc, publisherName, bids, passes from slot_request order by
time asc limit 2'
The correct name for the columns are 'bid' and 'pass', they're singular, not plural
2. No output is produced
3. Correct the names
/usr/bin/influx -precision rfc3339 -database dsp_metrics -username x -password x
-execute 'select time, dc, publisherName, bid, pass from slot_request order by
time asc limit 2'
4. Normal output is produced
time dc publisherName bid pass
---- -- ------------- --- ----
2019-06-10T22:07:01Z ny4 DEMY_Media 1
2019-06-10T22:07:03Z ny1 Zepto_Internet_Solutions 1

__Expected behavior:__
I was expecting either an error message, or perhaps just the columns that were correct to be shown

__Actual behavior:__
I got no output, making me wonder if the where clause was wrong. Since I had no where clause, that wasn't the case (:-)) I eventually realized I'd pluralized two of the five column names, but having two make all the columns break was unexpected, and more than a little mysterious.

__Environment info:__
* System info: Linux 3.10.0-693.21.1.el7.x86_64 x86_64

* InfluxDB version: InfluxDB v1.7.3 (git: 1.7 698dbc789aff13c2678357a6b93ff73dd7136571)

__Config:__
No special configurations

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Reproduce the issue with the supplied influx select command, then determine the intended behavior for misspelled columns—an error or partial results—and verify that the completed change distinguishes this case from a valid query.

Written by the indexing model from the issue text.

Assessment

Domain
database
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.