what i want is all records where sequence_number > y
Dieterbe
but you know that sequence number is only used to differentiate amongst points with the exact same timestamp, right?
dch_ joined the channel
jerius joined the channel
fiorix
no i didnt
Guest93420 has quit
Guest93420 joined the channel
Guest93420 has quit
Guest93420 joined the channel
skinp joined the channel
Guest93420 is now known as dch
skinp has quit
dch_ has quit
dch_ joined the channel
pauldix has quit
freeformz joined the channel
toddpers_ has quit
dch_ has quit
Dieterbe
fiorix: so typically all your timestamps will have sequence number 0, unless you have multiple datapoints on the same timestamp
toddpersen joined the channel
fiorix
i didn't know that... so perhaps my sequence numbers are all zeroes because i have like 1 data point every other second
although that's not what the front-end shows.. those data points do have distinct sequence_number
toddpersen has quit
freeformz has quit
Dieterbe
how do you populate the db?
who sets the sequence numbers?
voxter joined the channel
fiorix
i don't.. but they do show up in queries
all i set in the db are the 2 columns i need.. but when i query i get 4 columns, as expected.. time, sequence_number, x, y
clarkh joined the channel
clarkh1 joined the channel
clarkh has quit
arthabaska joined the channel
blalor has quit
blalor joined the channel
clarkh1 has quit
Laverne joined the channel
pauldix joined the channel
UICTamale joined the channel
toddpersen joined the channel
toddpersen has quit
toddpersen joined the channel
timgluz joined the channel
freeformz joined the channel
freeformz has quit
buckaroo joined the channel
neurodrone_ has quit
jjmalina joined the channel
freeformz joined the channel
freeformz has quit
q_no joined the channel
spuder joined the channel
blalor is now known as blalor_afk
freeformz joined the channel
skinp joined the channel
arthabaska joined the channel
freeformz has quit
bnzmnzhnz joined the channel
freeformz joined the channel
SirDarius joined the channel
arthabaska has quit
buckaroo has quit
el-chavo joined the channel
spuder has quit
spuder joined the channel
clarkh joined the channel
arthabaska joined the channel
UICTamale has quit
SirDarius has quit
esn joined the channel
JahBurn1 has quit
clarkh has quit
wilmoore joined the channel
el-chavo has quit
tmonk42 joined the channel
clarkh joined the channel
clarkh has quit
JahBurn joined the channel
crosbymichael
what is wrong with this query? delete from engines.tyland.system where time = time1407129391352
what is wrong with this query? delete from engines.tyland.system where time = 1407129391352
the second one
clarkh joined the channel
i get this error Delete queries can't have where clause that don't reference time
Dieterbe
don't you need a s or ms or something at the end
crosbymichael
why would I need that?
pauldix
crosbymichael: you can only do < and > comparisons, not exact match
crosbymichael
pauldix: why?
i need to delete a bad data point
clarkh has quit
tmonk42
Any recommendations on protobuf_timeout and protobuf_heartbeat in EC2? Currently using default of 200ms and I'm getting heartbeat timeouts for at least one node out of three every minute or so. All three are in same Region, but split between two AZs
pauldix
crosbymichael: just what we have implemented at the moment
you could do where time > 1407129391351s and time < 1407129391353s
crosbymichael
so what do you suggest I do to delete an exact data point?
pauldix
assuming you don't have other data points in that series in the same time range