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.

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

Support datetime strings #88

Closed
hvt opened this issue Dec 3, 2013 · 1 comment
Closed

Support datetime strings #88

hvt opened this issue Dec 3, 2013 · 1 comment

Comments

@hvt
Copy link

hvt commented Dec 3, 2013

Using the following (simple) query:

select * from test where time > '2013-01-01' limit 10

I get back an empty array while the log says:

********************************BUG********************************
Database: mydb
Query: [select * from test where time > '2013-01-01' limit 10]
Error: runtime error: invalid memory address or nil pointer dereference. Stacktrace: goroutine 30 [running]:
engine.func·004()
    /home/vagrant/influxdb/src/engine/engine.go:28 +0x116
datastore.(*LevelDbDatastore).sendBatch(0xc2000e8f90, 0xc2000e7d80, 0xc2001b68c0, 0xc2001b9760, 0x6c7800, ...)
    /home/vagrant/influxdb/src/datastore/leveldb_datastore.go:498 +0x136
datastore.(*LevelDbDatastore).executeQueryForSeries(0xc2000e8f90, 0xc2001bb776, 0x5, 0xc20015d1a0, 0x9, ...)
    /home/vagrant/influxdb/src/datastore/leveldb_datastore.go:462 +0x1200
datastore.(*LevelDbDatastore).ExecuteQuery(0xc2000e8f90, 0xc2000f55a0, 0xc200157ee0, 0xc2001bb776, 0x5, ...)
    /home/vagrant/influxdb/src/datastore/leveldb_datastore.go:216 +0x3bd
coordinator.(*CoordinatorImpl).DistributeQuery(0xc2000f77c0, 0xc2000f55a0, 0xc200157ee0, 0xc2001bb776, 0x5, ...)
    /home/vagrant/influxdb/src/coordinator/coordinator.go:29 +0x72
engine.(*QueryEngine).distributeQuery(0xc2000d0a90, 0xc2000f55a0, 0xc200157ee0, 0xc2001bb776, 0x5, ...)
    /home/vagrant/influxdb/src/engine/engine.go:61 +0x145
engine.(*QueryEngine).RunQuery(0xc2000d0a90, 0xc20

Note this fails without the 'limit'-clause too.

@jvshahid
Copy link
Contributor

jvshahid commented Dec 3, 2013

Thanks @hvt for reporting this issue. This feature isn't implemented yet. I'll try to get to it sometime today. Stay tuned.

jvshahid pushed a commit that referenced this issue Aug 12, 2014
encode entry should reuse memory rather than alloc each time
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants