Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

space in measure name makes first query after restart fail #6496

Closed
BrannonKing opened this issue Apr 28, 2016 · 0 comments
Closed

space in measure name makes first query after restart fail #6496

BrannonKing opened this issue Apr 28, 2016 · 0 comments
Assignees
@jwilder
Labels
area/tsm
Milestone
0.13.0

Comments

@BrannonKing
Copy link

Bug report

System info: Recent .13 Nightly on Windows 10

Steps to reproduce:

  1. Start a server in one console.
  2. Run the influx.exe client in another, use a database.
  3. Run this: insert a\ b value=1
  4. Run this and observe a single record: select * from "a b"
  5. Go back to the server and kill it. Restart it.
  6. Run the select again and observe no records when there should be one
  7. Run the insert and then the select again and observe the two records

Expected behavior: I should not have to insert data before I can query it.

The problem does not exist without whitespace in the measure name. This is a showstopper for me as my server is restarted daily (for other reasons) and reports are ran shortly after the server is up.
@jwilder jwilder mentioned this issue Apr 28, 2016
Merged
3 tasks
jwilder added a commit that referenced this issue Apr 29, 2016
@jwilder
Fix parsing keys when loading database index
979f234 
The code for parsing a key our of the WAL or TSM files in the engine
was naive and didn't account for measurements with escape chars. This
uses the correct parsing code to parse and load them correctly.

Fixes #6496
@jwilder jwilder added this to the 0.13.0 milestone Apr 29, 2016
@jwilder jwilder self-assigned this Apr 29, 2016
jwilder added a commit that referenced this issue Apr 30, 2016
@jwilder
Fix parsing keys when loading database index
8082fc6 
The code for parsing a key our of the WAL or TSM files in the engine
was naive and didn't account for measurements with escape chars. This
uses the correct parsing code to parse and load them correctly.

Fixes #6496
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jwilder jwilder

Labels
area/tsm
Projects
None yet
Milestone
0.13.0
Development

No branches or pull requests
2 participants
@jwilder @BrannonKing