clarify scan_consistency values and diff between statement/request in N1QL

Summary: Currently, in N1QL, a request can have single statement. And hence, scan_consistency value of request_plus and statement_plus are equivalent.
Also, define 'request', and 'statement'.

thanks,
-Prasad

From: Gerald Sangudi <Gerald@couchbase.com>
Date: Tuesday, September 27, 2016 at 5:43 PM
To: Prasad Varakur <prasad.varakur@couchbase.com>, query-dev <query-dev@couchbase.com>
Subject: Re: diff between request_plus and statement_plus

Hi Prasad,

The intent is to support multiple statements per request, e.g. anonymous blocks with multiple statements.

When that happens, request_plus will be different from statement_plus…

Gerald

From: Prasad Varakur <prasad.varakur@couchbase.com>
Date: Tuesday, September 27, 2016 at 5:41 PM
To: query-dev <query-dev@couchbase.com>
Subject: diff between request_plus and statement_plus

Hi team,

What is the diff between request & statement (in the context of N1QL)? Following documentation for scan-consistency seems to imply that a request can have multiple statements..
http://developer.couchbase.com/documentation/server/4.5/n1ql/n1ql-rest-api/index.html

request_plus This implements strong consistency per request. Before processing the request, a current vector is obtained. The vector is used as a lower bound for the statements in the request.
Can you pls clarify/explain.. For example putting two statements in a single REST request throws error:

varakurprasad$ curl -v http://localhost:8093/query/service -d "statement=SELECT type, name from \`travel-sample\` limit 2; select 1 from default;”
…
"errors": [

{ "code": 1065, "msg": "Unrecognized parameter in request: select 1 from default" }

Thanks,
-Prasad