Points are missing after write and extra fields with underscores are present

[carbolymer]

Bug report

System info:

[run] 2016/10/12 15:34:15 InfluxDB starting, version 1.0.1, branch master, commit 8b354f72951f50b130894dddee2e05149a1801d8
[run] 2016/10/12 15:34:15 Go version go1.6.2, GOMAXPROCS set to 8

Steps to reproduce:

1. Create new database
2. Write following points

something,name=grodno,symbol=grn close=5.75,high=5.75,low=5.75,name="grodno",open=5.75,symbol="grn",volume=22i 1476263100000000000
something,name=grodno,symbol=grn close=5.56,high=5.56,low=5.56,name="grodno",open=5.56,symbol="grn",volume=500i 1476264000000000000
something,name=grodno,symbol=grn close=5.4,high=5.4,low=5.4,name="grodno",open=5.4,symbol="grn",volume=1390i 1476265800000000000
something,name=grodno,symbol=grn close=5.4,high=5.4,low=5.4,name="grodno",open=5.4,symbol="grn",volume=852i 1476278100000000000
something,name=grodno,symbol=grn close=5.4,high=5.4,low=5.4,name="grodno",open=5.4,symbol="grn",volume=36i 1476286500000000000
something,name=grodno,symbol=grn close=5.4,high=5.4,low=5.4,name="grodno",open=5.5,symbol="grn",volume=1i 1476291000000000000

Expected behavior:
6 points inserted properly. tags and fields names without underscores

Actual behavior:
only 5 points are written, tags name and symbol are duplicated as name_1 and symbol_1

[phemmer]

Smells like #7319

[jwilder]

Looks like that last point is written into the future and the default end time for a query adds time < now() so it's not returned.

> select * from something where time <= 1476291000000000000
name: something
time            close   high    low     name    name_1  open    symbol  symbol_1        volume
----            -----   ----    ---     ----    ------  ----    ------  --------        ------
1476263100000000000     5.75    5.75    5.75    grodno  grodno  5.75    grn     grn         22
1476264000000000000     5.56    5.56    5.56    grodno  grodno  5.56    grn     grn         500
1476265800000000000     5.4     5.4     5.4     grodno  grodno  5.4     grn     grn         1390
1476278100000000000     5.4     5.4     5.4     grodno  grodno  5.4     grn     grn         852
1476286500000000000     5.4     5.4     5.4     grodno  grodno  5.4     grn     grn         36
1476291000000000000     5.4     5.4     5.4     grodno  grodno  5.5     grn     grn         1

See #4461

[jwilder]

The name and symbol columns have _1 because your points have both of these stored as a tag and a field.

[bonesyo]

@jwilder This just started happening in our production database and ended up breaking a lot of our functionality. Can you explain why this is happening all of the sudden? I feel like a warning or error from the db or query would be much better than modifying data and potentially breaking stuff.

[majidakbari]

I've just deleted the database and created new one, the issue was fixed by itself. Fortunately it did not occur in production.