AddShards called without shards

[sergey-kovalchuk]

System returns "AddShards called without shards" on following Writing Data request (please check tcp dump):

POST /db/osgi-core/series?u=root&p=fetdiedm&time_precision=s HTTP/1.1

User-Agent: Java/1.7.0_25

Host: 192.168.1.101:8086

Accept: text/html, image/gif, image/jpeg, ; q=.2, */; q=.2

Connection: keep-alive

Content-type: application/x-www-form-urlencoded

Content-Length: 433

[{"name":"ZZZ.qqq.timer","columns":["time","count","min","max","mean","std-dev","50-percentile","75-percentile","95-percentile","99-percentile","999-percentile","one-minute","five-minute","fifteen-minute","mean-rate"],"points":[[1397727405297,1,0.500127057,0.500127057,0.500127057,0.0,0.500127057,0.500127057,0.500127057,0.500127057,0.500127057,1.4837551900328427E-8,0.007500607619655408,0.06694510278436885,0.0010060843377660727]]}]HTTP/1.1 400 Bad Request

Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept

Access-Control-Allow-Methods: GET, POST, PUT, DELETE

Access-Control-Allow-Origin: *

Access-Control-Max-Age: 2592000

Content-Type: text/plain

Date: Thu, 17 Apr 2014 10:14:28 GMT

Content-Length: 31

AddShards called without shards

---

Precondition:
system version: 0.5.7
OS: ubuntu 12

[jvshahid]

One thing i noticed is that the time precision is set to seconds in the http query parameter but the actual timestamp in the body looks like milliseconds. That said, i'm not sure if it has something to do with the error and if it does we should report a better error message.

[jjmalina]

I've seen this same error when sending millisecond timestamps but with seconds as the specified precision.

[sergey-kovalchuk]

Thanks for the fast reply.
After removing 'time precision=is'from query the error no longer appears.