Select to scan conversion

It looks like select has been deprecated since 0.17, but the documentation didn’t go detail on how to actual convert the query, is it simply replace the keyword from select to scan. My query times out with “network error” after that.

{
    "dataSource": "*******-eed1-49e5-9129-***********",
    "descending": false,
    "dimensions": [],
    "granularity": "month",
    "intervals": [
        "-146136543-09-08T08:23:32.096Z/146140482-04-24T15:36:27.903Z"
    ],
    "metrics": [],
    "pagingSpec": {
        "pagingIdentifiers": {},
        "threshold": 0
    },
    "queryType": "scan"
}

I am able to create a scan query to get the results (the list of columns) back.

What are you trying to achieve with this query? Is it a full extract of the contents?

I don’t know that this is your issue, but the json structure for scan is a bit different:

{
    "dataSource": "*******-eed1-49e5-9129-***********",
    "order": "ascending",
    "columns":[],
    "intervals": [
        "-146136543-09-08T08:23:32.096Z/146140482-04-24T15:36:27.903Z"
    ],
    "queryType": "scan"
}

I removed all the properties that are not part of the scan query properties and replaced them with what seem to be the new alternative for them.

I did not find anything for "granularity": "month",. I’ve never used the older select query type, so I’m not sure what that is meant to do, but there doesn’t seem to be an equivalent in the scan query.

I didn’t find a replacement for the pagingSpec either although offset should provide similar behavior, I think.

Let us know how it goes.

Thanks, this helped!