Uploaded image for project: 'Couchbase Go SDK'
  1. Couchbase Go SDK
  2. GOCBC-226

Expose more N1QL Query Options

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.2.5
    • Component/s: library
    • Labels:
      None

      Description

      During review of the possible n1ql query options with Marco we settled on exposing the following from the SDK directly in addition to the ones already present:

      for fine-tuning the request performance (similar to max_parallelism which we expose already)

      • scan_cap: Maximum buffered channel size between the indexer client and the query service for index scans. This parameter controls when to use scan backfill. Use 0 or a negative number to disable.
      • pipeline_batch: Controls the number of items execution operators can batch for Fetch from the KV.
      • pipeline_cap: Maximum number of items each execution operator can buffer between various operators.

      also, if the user knows the request is only ever a select, for security reasons it can make sense to tell the server this thing is readonly and it will prevent mutations from happening.

      • readonly: Controls whether a query can change a resulting recordset.
        If readonly is true, then the following statements are not allowed:

      CREATE INDEX
      DROP INDEX
      INSERT
      MERGE
      UPDATE
      UPSERT

      Note that https://developer.couchbase.com/documentation/server/5.0/settings/query-settings.html has these params documented but the docs are wrong at the time of ticket creation (it shows - and not _ when describing the on the wire representation of the param)

        Attachments

        1. text.html
          27 kB
        2. image002.png
          image002.png
          2 kB
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

          Hide
          anthony.galvez Anthony Galvez (Inactive) added a comment -

          Hope you’re well, Anthony.

           

          [1]Support-internal@couchbase.com has [2]staff_se@couchbase.com nested within it, which you are a member of.

           

          Would you like me to take you off staff_se@couchbase.com?

           

          From: "Anthony Poliseno (Marketing)" <anthony.poliseno@couchbase.com>
          Date: Wednesday, August 23, 2017 at 10:29 AM
          To: "Anthony Galvez (IT)" <Anthony.Galvez@couchbase.com>
          Subject: FW: Couchbase Issues: (JSCBC-412) Expose more N1QL Query Options

           

          Hey hey – any way I can get taken off these emails? Thanks!

           

          From: "Brett Lawson (Couchbase JIRA)" <community_admin@couchbase.com>
          Date: Wednesday, August 23, 2017 at 10:17 AM
          To: support-internal <support-internal@couchbase.com>
          Subject: Couchbase Issues: (JSCBC-412) Expose more N1QL Query Options

           

          [3]Tyler Mitchell created an issue

           

          [4]Couchbase node.js Client Library / [5][6]JSCBC-412

          [7]Expose more N1QL Query Options

          Issue Type:

          Improvement

          Assignee:

          [8]Brett Lawson

          Components:

          library

          Created:

          23/Aug/17 10:16 AM

          Fix Versions:

          2.4.0

          Priority:

          Major

          Reporter:

          [9]Tyler Mitchell

          During review of the possible n1ql query options with Marco we settled on exposing the following from the SDK directly in addition to the ones already present:

          for fine-tuning the request performance (similar to max_parallelism which we expose already)

          *scan_cap: Maximum buffered channel size between the indexer client and the query service for index scans. This parameter controls when to use scan backfill. Use 0 or a negative number to disable.
          *pipeline_batch: Controls the number of items execution operators can batch for Fetch from the KV.
          *pipeline_cap: Maximum number of items each execution operator can buffer between various operators.

          also, if the user knows the request is only ever a select, for security reasons it can make sense to tell the server this thing is readonly and it will prevent mutations from happening.

          *readonly: Controls whether a query can change a resulting recordset.
          If readonly is true, then the following statements are not allowed:

          CREATE INDEX
          DROP INDEX
          INSERT
          MERGE
          UPDATE
          UPSERT

          Note that [10]https://developer.couchbase.com/documentation/server/5.0/settings/query-settings.html has these params documented but the docs are wrong at the time of ticket creation (it shows - and not _ when describing the on the wire representation of the param)

          [11]

          [12]Add Comment

           

          This message was sent by Atlassian JIRA (v7.3.2#73013-sha1:3d53c97)

           
          ----------------------------------------------------------------------------------------
          [1] Support-internal@couchbase.com
          [2] staff_se@couchbase.com
          [3] https://issues.couchbase.com/secure/ViewProfile.jspa?name=tyler.mitchell
          [4] https://issues.couchbase.com/browse/JSCBC
          [5] https://issues.couchbase.com/browse/JSCBC-412
          [6] https://issues.couchbase.com/browse/JSCBC-412
          [7] https://issues.couchbase.com/browse/JSCBC-412
          [8] https://issues.couchbase.com/secure/ViewProfile.jspa?name=brett19
          [9] https://issues.couchbase.com/secure/ViewProfile.jspa?name=tyler.mitchell
          [10] https://developer.couchbase.com/documentation/server/5.0/settings/query-settings.html
          [11] https://issues.couchbase.com/browse/JSCBC-412#add-comment
          [12] https://issues.couchbase.com/browse/JSCBC-412#add-comment

          Show
          anthony.galvez Anthony Galvez (Inactive) added a comment - Hope you’re well, Anthony.   [1] Support-internal@couchbase.com has [2] staff_se@couchbase.com nested within it, which you are a member of.   Would you like me to take you off staff_se@couchbase.com?   From: "Anthony Poliseno (Marketing)" <anthony.poliseno@couchbase.com> Date: Wednesday, August 23, 2017 at 10:29 AM To: "Anthony Galvez (IT)" <Anthony.Galvez@couchbase.com> Subject: FW: Couchbase Issues: ( JSCBC-412 ) Expose more N1QL Query Options   Hey hey – any way I can get taken off these emails? Thanks!   From: "Brett Lawson (Couchbase JIRA)" <community_admin@couchbase.com> Date: Wednesday, August 23, 2017 at 10:17 AM To: support-internal <support-internal@couchbase.com> Subject: Couchbase Issues: ( JSCBC-412 ) Expose more N1QL Query Options   [3] Tyler Mitchell created an issue   [4] Couchbase node.js Client Library / [5] [6] JSCBC-412 [7] Expose more N1QL Query Options Issue Type: Improvement Assignee: [8] Brett Lawson Components: library Created: 23/Aug/17 10:16 AM Fix Versions: 2.4.0 Priority: Major Reporter: [9] Tyler Mitchell During review of the possible n1ql query options with Marco we settled on exposing the following from the SDK directly in addition to the ones already present: for fine-tuning the request performance (similar to max_parallelism which we expose already) *scan_cap: Maximum buffered channel size between the indexer client and the query service for index scans. This parameter controls when to use scan backfill. Use 0 or a negative number to disable. *pipeline_batch: Controls the number of items execution operators can batch for Fetch from the KV. *pipeline_cap: Maximum number of items each execution operator can buffer between various operators. also, if the user knows the request is only ever a select, for security reasons it can make sense to tell the server this thing is readonly and it will prevent mutations from happening. *readonly: Controls whether a query can change a resulting recordset. If readonly is true, then the following statements are not allowed: CREATE INDEX DROP INDEX INSERT MERGE UPDATE UPSERT Note that [10] https://developer.couchbase.com/documentation/server/5.0/settings/query-settings.html has these params documented but the docs are wrong at the time of ticket creation (it shows - and not _ when describing the on the wire representation of the param) [11] [12] Add Comment   This message was sent by Atlassian JIRA (v7.3.2#73013-sha1:3d53c97)   ---------------------------------------------------------------------------------------- [1] Support-internal@couchbase.com [2] staff_se@couchbase.com [3] https://issues.couchbase.com/secure/ViewProfile.jspa?name=tyler.mitchell [4] https://issues.couchbase.com/browse/JSCBC [5] https://issues.couchbase.com/browse/JSCBC-412 [6] https://issues.couchbase.com/browse/JSCBC-412 [7] https://issues.couchbase.com/browse/JSCBC-412 [8] https://issues.couchbase.com/secure/ViewProfile.jspa?name=brett19 [9] https://issues.couchbase.com/secure/ViewProfile.jspa?name=tyler.mitchell [10] https://developer.couchbase.com/documentation/server/5.0/settings/query-settings.html [11] https://issues.couchbase.com/browse/JSCBC-412#add-comment [12] https://issues.couchbase.com/browse/JSCBC-412#add-comment
          Hide
          build-team Couchbase Build Team added a comment -

          Build 5.1.0-1448 contains gocb commit 2f462ae8c10e15d143c0b6cfb98825264e192ef2 with commit message:
          GOCBC-226: Added additional N1QL query parameters.
          https://github.com/couchbase/gocb/commit/2f462ae8c10e15d143c0b6cfb98825264e192ef2

          Show
          build-team Couchbase Build Team added a comment - Build 5.1.0-1448 contains gocb commit 2f462ae8c10e15d143c0b6cfb98825264e192ef2 with commit message: GOCBC-226 : Added additional N1QL query parameters. https://github.com/couchbase/gocb/commit/2f462ae8c10e15d143c0b6cfb98825264e192ef2
          Hide
          build-team Couchbase Build Team added a comment -

          Build 5.0.1-4738 contains gocb commit 2f462ae8c10e15d143c0b6cfb98825264e192ef2 with commit message:
          GOCBC-226: Added additional N1QL query parameters.
          https://github.com/couchbase/gocb/commit/2f462ae8c10e15d143c0b6cfb98825264e192ef2

          Show
          build-team Couchbase Build Team added a comment - Build 5.0.1-4738 contains gocb commit 2f462ae8c10e15d143c0b6cfb98825264e192ef2 with commit message: GOCBC-226 : Added additional N1QL query parameters. https://github.com/couchbase/gocb/commit/2f462ae8c10e15d143c0b6cfb98825264e192ef2
          Hide
          build-team Couchbase Build Team added a comment -

          Build sync_gateway-2.1.0-839 contains gocb commit 2f462ae8c10e15d143c0b6cfb98825264e192ef2 with commit message:
          GOCBC-226: Added additional N1QL query parameters.
          https://github.com/couchbase/gocb/commit/2f462ae8c10e15d143c0b6cfb98825264e192ef2

          Show
          build-team Couchbase Build Team added a comment - Build sync_gateway-2.1.0-839 contains gocb commit 2f462ae8c10e15d143c0b6cfb98825264e192ef2 with commit message: GOCBC-226 : Added additional N1QL query parameters. https://github.com/couchbase/gocb/commit/2f462ae8c10e15d143c0b6cfb98825264e192ef2

            People

            • Assignee:
              brett19 Brett Lawson
              Reporter:
              tyler.mitchell Tyler Mitchell (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.