Supported MongoDB Commands¶
The following MongoDB query operations are supported by Data Lake.
Some commands have special behavior in Data Lake that differs from standard MongoDB functionality.
To run a command against your Data Lake, use db.runCommand():
db.runCommand( { <command> } )
Aggregation Commands¶
Command | Description |
---|---|
The following limitation applies: Atlas Data Lake supports the For the Atlas Data Lake supports Tip | |
The following limitations apply:
|
Diagnostic Commands¶
Command | Description | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The response returns the following fields:
Example
| ||||||||||||||||||
The following fields are omitted from the response:
The following fields are added to the response. You can use these fields to verify what partitions are being used to populate a collection.
Example
| ||||||||||||||||||
Returns information about the current connection, specifically the state of authenticated users and their available roles. Note Only one user can authenticate on a connection to a Data Lake at any
given time. If a user authenticates and then runs the The connectionStatus
command shows only the newly authenticated user in the
| ||||||||||||||||||
The following fields are omitted from the response:
| ||||||||||||||||||
The data returned by The following commands are explainable in Data Lake:
The following
The Example The following example shows how to use the
| ||||||||||||||||||
The response returns successfully, but includes no log data. | ||||||||||||||||||
The MaxTimeMS option is not supported. | ||||||||||||||||||
The reponse returns the following subset of fields from the standard MongoDB response:
| ||||||||||||||||||
Tests whether a server is responding to commands. | ||||||||||||||||||
Returns the client IP address. |
Query and Write Operation Commands¶
Command | Description |
---|---|
The following options are supported:
|
Authentication Commands¶
Command | Description |
---|---|
Data Lake uses SCRAM-SHA authentication. |
Replication Commands¶
Command | Description |
---|---|
The response always returns a document in which
The optional Note About the hello Command Atlas Data Lake also supports the |
Administration Commands¶
Command | Description |
---|---|
Kills the specified cursor or cursors for a collection. | |
Retrieves information about the collections in a database, such as collection names and options. The response contains information that can be used to create a cursor to the collection information. The following options are supported:
| |
Provides a list of all existing databases. You must use the
The following options are supported:
|
Role Management Commands¶
Command | Description |
---|---|
Returns inheritance and privilege information for specified
roles. |
User Management Commands¶
Command | Description |
---|---|
Returns information about one or more users. The |
Data Lake Commands¶
Command | Description | |
---|---|---|
storageGetConfig | Returns the current Data Lake configuration. For complete documentation on the configuration document format, see Configuration Document Format.
To learn more about this command, see Retrieve Data Lake Configuration. | |
storageSetConfig | Replaces the current Data Lake configuration with a JSON document. For complete documentation on the configuration document format, see Configuration Document Format.
To learn more about this command, see Set or Update Data Lake Configuration. | |
storageGenerateConfig | Generates a configuration for your Data Lake in JSON format. For complete documentation on the configuration document format, see Configuration Document Format.
To learn more about this command, see Generate Data Lake Configuration. | |
storageValidateConfig | Validates the given Data Lake configuration. For complete documentation on the configuration document format, see Configuration Document Format.
To learn more about this command, see Validate Data Lake Configuration. |