undefined response status in readMulti

[Berckyt]

Hi.

If I use readMilti method with few months data range (for example from 2013-12-22 to 2014-05-22), tempodb client returns me response with undefined status. Why?
{ [Error: Response returned non-200 code]
response:
{ headers: undefined,
status: undefined,
session:
{ key: 'some key',
secret: 'some secret',
hostname: 'api.tempo-db.com',
port: 443,
version: 'v1',
secure: true,
maxconns: 10,
path: '/v1',
headers: [Object],
connection: [Object] },
json: { data: [Object], series: [Object], rollup: null, tz: 'UTC' },
successful: 0,
error: undefined } }

But in such case response.json.data has normal data, as expected.
Can't I use big data range?

Thank you.

[CDA0]

I have this issue as well.

I can readMulti with the following options:
{ key: [ 'N0OQdkEZ9j' ],
tz: 'Europe/London',
rollup: { period: '1hour', fold: 'max' } }

adding other keys to the array returns the right data but bad status code shown:
{ key:
[ 'BfGpFbtz10',
'1zilyiix8e',
'reoutiR7nz',
'PyVu9JYzP1',
'cc8djeJYdE',
'6TnSHhzXDS',
'6pxvhIql0N',
'APODsvODhH',
'6A3uDV5yzC',
'dUcdJcmV65',
'SS1bj02Pgf' ],
tz: 'Europe/London',
rollup: { period: '1hour', fold: 'max' } }

returns:

{ [Error: Response returned non-200 code]
response:
{ headers: undefined,
status: undefined,
session:
{ key: 'some_key',
secret: 'some_secret',
hostname: 'api.tempo-db.com',
port: 443,
version: 'v1',
secure: true,
maxconns: 10,
path: '/v1',
headers: [Object],
connection: [Object] },
json:
{ data: [Object],
series: [Object],
rollup: null,
tz: 'Europe/London' },
successful: 0,
error: undefined } }

[CDA0]

Rollup cannot be an object it has to be string of 'rollup.period' and 'rollup.fold'.

If session.js sees an object it makes the query string rollup[period]=x&rollup[fold]=y which causes the error.

Not sure how the above would affect other api calls in encodeQueryData but making anobject return parent.child so easier just to use a string for now.

[mrgaaron]

CDA0 - that is true. Checking through the demo examples there are some instances (particularly in the read-multi-demo) where the example code uses out of date parameters for rollups. I will issue a PR to update any obsolete examples to avoid that confusion. I'm also curious why sending incorrectly formatted parameters like that causes the status to be undefined. What is likely happening is that TempoDB ignores invalid parameters, and we assume a default of a "raw" read (which is to say, all the raw data in the series) if we don't see a rollup.fold parameter. However, this should still be picked up by the NodeJS client as a 200. So this is a bug worth me looking into even if you have a solution.

Berckyt - I would be curious to see if CDA0's observation also addresses your problem. If not, I would like to get in touch with you over email or hangout to get more specifics on your query so that I can try to reproduce. But by itself, querying over a long range is perfectly fine and should not be the cause of this issue.