List of filters for query results. See API documentation for "Query Methods" for more guidance.
No Additional Items[
[
"name",
"=",
"bob"
]
]
[
[
"OR",
[
[
[
"name",
"=",
"bob"
]
],
[
[
"name",
"=",
"larry"
]
]
]
]
]
Query options customize the results returned by a query method. More complete documentation with examples
are covered in the "Query methods" section of the TrueNAS API documentation.
Extra options are defined on a per-endpoint basis and are described in the documentation for the associated
query method.
An array of field names describing the manner in which query results should be ordered. The field names may
also have one of more of the following special prefixes: - (reverse sort direction), nulls_first: (place
any null values at the head of the results list), nulls_last: (place any null values at the tail of the
results list).
[
"size",
"-devname",
"nulls_first:-expiretime"
]
An array of field names specifying the exact fields to include in the query return. The dot character .
may be used to explicitly select only subkeys of the query result.
[
"username",
"Authentication.status"
]
Return a numeric value representing the number of items that match the specified query-filters.
Return the JSON object of the first result matching the specified query-filters. The query fails
if there specified query-filters return no results.
This specifies the beginning offset of the results array. When combined with the limit query-option
it may be used to implement pagination of large results arrays. WARNING: some query methods provide
volatile results and the onus is on the developer to understand whether pagination is appropriate
for a particular query API method.
This specifies the maximum number of results matching the specified query-filters to return. When
combined wtih the offset query-option it may be used to implement pagination of large results arrays.
WARNING: some query methods provide volatile results and the onus is on the developer to understand whether
pagination is appropriate for a particular query API method.
Namespace ID (NSID)
Each namespace within a subsystem has an associated NSID, unique within that subsystem.
If not supplied during namespace creation then the next available NSID will be used.
Value must be greater or equal to 1 and strictly lesser than 4294967295
Human readable name for the subsystem.
If subnqn is not provided on creation, then this name will be appended to the basenqn from nvmet.global.config to generate a subnqn.
Must be at least 1 characters long
Must be at least 1 characters long
Must be at most 223 characters long
If True then any host can access the storage associated with this subsystem (i.e. no access control).
If set to either True or False then override the global ana setting from nvmet.global.config for this subsystem only.
If null then the global ana setting will take effect.
List of host ids which have access to this subsystem.
Only populated on query if extra.options.verbose is set.
List of namespaces ids in this subsystem.
Only populated on query if extra.options.verbose is set.
List of ports ids on which this subsystem is available.
Only populated on query if extra.options.verbose is set.
Type of device (or file) used to implement the namespace.
Path to the device or file being used to implement the namespace.
When device_type is "ZVOL" then this path is e.g. "zvol/poolname/zvolname"
When device_type is "FILE" then this path is e.g. "/mnt/poolmnt/path/to/file". The file will be created if necessary.
When device_type is "FILE" then this will be the size of the file in bytes.
Must be at least 1 characters long
Must be at least 1 characters long
If enabled is False then the namespace will not be accessible.
Some namespace configuration changes are blocked when that namespace is enabled.
Reflect the locked state of the namespace.
The underlying device_path could be an encrypted ZVOL, or a file on an encrypted dataset. In either case locked will be True if the underlying entity is locked.
Namespace ID (NSID)
Each namespace within a subsystem has an associated NSID, unique within that subsystem.
If not supplied during namespace creation then the next available NSID will be used.
Value must be greater or equal to 1 and strictly lesser than 4294967295
Type of device (or file) used to implement the namespace.
Path to the device or file being used to implement the namespace.
When device_type is "ZVOL" then this path is e.g. "zvol/poolname/zvolname"
When device_type is "FILE" then this path is e.g. "/mnt/poolmnt/path/to/file". The file will be created if necessary.
When device_type is "FILE" then this will be the size of the file in bytes.
Must be at least 1 characters long
Must be at least 1 characters long
If enabled is False then the namespace will not be accessible.
Some namespace configuration changes are blocked when that namespace is enabled.
Reflect the locked state of the namespace.
The underlying device_path could be an encrypted ZVOL, or a file on an encrypted dataset. In either case locked will be True if the underlying entity is locked.