Sign inTry Free

Important

Helios features are now enabled during weekly update windows and are no longer directly tied to SingleStore engine releases. Refer to the release notes to view the latest features available in your Helios cluster.

setDefaultCollectionOptions

On this page

Sets the defaults that are used when a collection is created implicitly by a write command for the current database. All the options supported by the createCollection command can be modified using setDefaultCollectionOptions.

Syntax

db.runCommand({
  setDefaultCollectionOptions: 1
  value : <document>|<null>
})

Field

Type

Description

value

Document

Specifies the options to set. When set to null, collection options are reset to the defaults set for new databases.

Example

The following example sets default collection options for the current database:

db.runCommand({
  setDefaultCollectionOptions: 1,
  value: { rowstore: true, shardKey: { _id: 1 } },
});

To update only one option from the defaults while leaving others unchanged, you may need to run multiple commands. Here's an example:

var options = db.runCommand({ getDefaultCollectionOptions: 1 }).value;
options.shardKey = { Code: 1 };
db.runCommand({ setDefaultCollectionOptions: 1, value: options });

Last modified:

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In