Content search
Searches file content with a regular expression, accelerated by the namespace’s grep index. Matches are verified against the real pattern and returned in ascending (inode_id, byte_offset) order; revisions committed after the index watermark are scanned exhaustively unless allow_stale skips them. Requires this deployment to serve grep and the namespace to carry a materialized active grep index.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Namespace id
Query Parameters
Section titled “Query Parameters ”Pattern in the Rust regex crate’s dialect. Its UTF-8 encoding must be at most 1024 bytes.
Match case-insensitively (true or false). Defaults to false.
Complete absolute path used to restrict matches.
Permit a capped exhaustive scan when the pattern has no required grams (true or false). Defaults to false.
Return indexed-only results when the unindexed tail exceeds the scan budget (true or false). Defaults to false.
Maximum matches per page
Opaque grep page cursor
Responses
Section titled “ Responses ”One page of matches
One content-search page.
object
Commits at or below this sequence were answered from the index.
The namespace head sequence used to evaluate this page.
The matches in ascending (inode_id, byte_offset) order.
One line-oriented match.
object
Byte offset of the match within the file.
Durable identity of the matched file.
Example
ino_123The matching line, truncated to the server’s line cap.
One-based line number of the match.
True when line was truncated.
The file’s absolute path, derived at the snapshot.
Example
/docs/report.txtThe matched revision (the newest visible one at the snapshot).
Namespace searched.
Example
demoPresent when another page follows.
Whether revisions after built_through_seq were scanned exhaustively.
Invalid pattern, cursor, or an unindexable pattern without allow_scan
HTTP error body used by LoonFS APIs.
object
The stable machine-readable error code as a string.
The optional machine-readable context for the error code.
object
The Unix-millisecond time when the current writer acquired its epoch, when available.
Epoch that currently owns the namespace.
The writer ID recorded for the current epoch, when available.
Access revision that is actually current for the inode.
Attribute revision that is actually current for the inode.
Current binding token; absent for the root, which has no binding.
Deletion sequence actually active for the inode.
The actual namespace head sequence.
The path actually contained this inode.
Example
ino_123Revision that is actually current; absent when the inode has none.
Change-feed cursor the request asked to resume after.
Idempotency key of the commit the error concerns.
Example
c_f3a9c2d4b6e8417a90c5d2f8e1b7a6c0The fingerprint of the mutation that landed under commit_id, present with committed_seq.
The sequence where this commit ID already landed, when recorded by a durable receipt.
Access revision the request expected to be current.
Attribute revision the request expected to be current.
Opaque binding token supplied by the request.
Deletion sequence the undelete expected to be active.
The head sequence required by the request.
The request expected the path to contain this inode.
Example
ino_123Revision the request expected to be current.
Epoch the failing writer session held when it was displaced.
Inode the failed precondition or operation targeted.
Example
ino_123Maximum writer sessions admitted by the node.
The deleted namespace that caused the operation to fail.
Example
demoThe index of the failed operation in the request.
Zero-based position of the failed request precondition.
Oldest sequence still promised for incremental replay.
The capability feature key for a not_supported error.
Human-readable error message.
The invalid JSON Pointer, parameter name, CLI flag, or CLI argument.
The request correlation ID also sent in the x-request-id response header.
Unauthorized
HTTP error body used by LoonFS APIs.
object
The stable machine-readable error code as a string.
The optional machine-readable context for the error code.
object
The Unix-millisecond time when the current writer acquired its epoch, when available.
Epoch that currently owns the namespace.
The writer ID recorded for the current epoch, when available.
Access revision that is actually current for the inode.
Attribute revision that is actually current for the inode.
Current binding token; absent for the root, which has no binding.
Deletion sequence actually active for the inode.
The actual namespace head sequence.
The path actually contained this inode.
Example
ino_123Revision that is actually current; absent when the inode has none.
Change-feed cursor the request asked to resume after.
Idempotency key of the commit the error concerns.
Example
c_f3a9c2d4b6e8417a90c5d2f8e1b7a6c0The fingerprint of the mutation that landed under commit_id, present with committed_seq.
The sequence where this commit ID already landed, when recorded by a durable receipt.
Access revision the request expected to be current.
Attribute revision the request expected to be current.
Opaque binding token supplied by the request.
Deletion sequence the undelete expected to be active.
The head sequence required by the request.
The request expected the path to contain this inode.
Example
ino_123Revision the request expected to be current.
Epoch the failing writer session held when it was displaced.
Inode the failed precondition or operation targeted.
Example
ino_123Maximum writer sessions admitted by the node.
The deleted namespace that caused the operation to fail.
Example
demoThe index of the failed operation in the request.
Zero-based position of the failed request precondition.
Oldest sequence still promised for incremental replay.
The capability feature key for a not_supported error.
Human-readable error message.
The invalid JSON Pointer, parameter name, CLI flag, or CLI argument.
The request correlation ID also sent in the x-request-id response header.
Namespace not found
HTTP error body used by LoonFS APIs.
object
The stable machine-readable error code as a string.
The optional machine-readable context for the error code.
object
The Unix-millisecond time when the current writer acquired its epoch, when available.
Epoch that currently owns the namespace.
The writer ID recorded for the current epoch, when available.
Access revision that is actually current for the inode.
Attribute revision that is actually current for the inode.
Current binding token; absent for the root, which has no binding.
Deletion sequence actually active for the inode.
The actual namespace head sequence.
The path actually contained this inode.
Example
ino_123Revision that is actually current; absent when the inode has none.
Change-feed cursor the request asked to resume after.
Idempotency key of the commit the error concerns.
Example
c_f3a9c2d4b6e8417a90c5d2f8e1b7a6c0The fingerprint of the mutation that landed under commit_id, present with committed_seq.
The sequence where this commit ID already landed, when recorded by a durable receipt.
Access revision the request expected to be current.
Attribute revision the request expected to be current.
Opaque binding token supplied by the request.
Deletion sequence the undelete expected to be active.
The head sequence required by the request.
The request expected the path to contain this inode.
Example
ino_123Revision the request expected to be current.
Epoch the failing writer session held when it was displaced.
Inode the failed precondition or operation targeted.
Example
ino_123Maximum writer sessions admitted by the node.
The deleted namespace that caused the operation to fail.
Example
demoThe index of the failed operation in the request.
Zero-based position of the failed request precondition.
Oldest sequence still promised for incremental replay.
The capability feature key for a not_supported error.
Human-readable error message.
The invalid JSON Pointer, parameter name, CLI flag, or CLI argument.
The request correlation ID also sent in the x-request-id response header.
Namespace deleted
HTTP error body used by LoonFS APIs.
object
The stable machine-readable error code as a string.
The optional machine-readable context for the error code.
object
The Unix-millisecond time when the current writer acquired its epoch, when available.
Epoch that currently owns the namespace.
The writer ID recorded for the current epoch, when available.
Access revision that is actually current for the inode.
Attribute revision that is actually current for the inode.
Current binding token; absent for the root, which has no binding.
Deletion sequence actually active for the inode.
The actual namespace head sequence.
The path actually contained this inode.
Example
ino_123Revision that is actually current; absent when the inode has none.
Change-feed cursor the request asked to resume after.
Idempotency key of the commit the error concerns.
Example
c_f3a9c2d4b6e8417a90c5d2f8e1b7a6c0The fingerprint of the mutation that landed under commit_id, present with committed_seq.
The sequence where this commit ID already landed, when recorded by a durable receipt.
Access revision the request expected to be current.
Attribute revision the request expected to be current.
Opaque binding token supplied by the request.
Deletion sequence the undelete expected to be active.
The head sequence required by the request.
The request expected the path to contain this inode.
Example
ino_123Revision the request expected to be current.
Epoch the failing writer session held when it was displaced.
Inode the failed precondition or operation targeted.
Example
ino_123Maximum writer sessions admitted by the node.
The deleted namespace that caused the operation to fail.
Example
demoThe index of the failed operation in the request.
Zero-based position of the failed request precondition.
Oldest sequence still promised for incremental replay.
The capability feature key for a not_supported error.
Human-readable error message.
The invalid JSON Pointer, parameter name, CLI flag, or CLI argument.
The request correlation ID also sent in the x-request-id response header.
The grep index is corrupt or its backing store is unavailable
HTTP error body used by LoonFS APIs.
object
The stable machine-readable error code as a string.
The optional machine-readable context for the error code.
object
The Unix-millisecond time when the current writer acquired its epoch, when available.
Epoch that currently owns the namespace.
The writer ID recorded for the current epoch, when available.
Access revision that is actually current for the inode.
Attribute revision that is actually current for the inode.
Current binding token; absent for the root, which has no binding.
Deletion sequence actually active for the inode.
The actual namespace head sequence.
The path actually contained this inode.
Example
ino_123Revision that is actually current; absent when the inode has none.
Change-feed cursor the request asked to resume after.
Idempotency key of the commit the error concerns.
Example
c_f3a9c2d4b6e8417a90c5d2f8e1b7a6c0The fingerprint of the mutation that landed under commit_id, present with committed_seq.
The sequence where this commit ID already landed, when recorded by a durable receipt.
Access revision the request expected to be current.
Attribute revision the request expected to be current.
Opaque binding token supplied by the request.
Deletion sequence the undelete expected to be active.
The head sequence required by the request.
The request expected the path to contain this inode.
Example
ino_123Revision the request expected to be current.
Epoch the failing writer session held when it was displaced.
Inode the failed precondition or operation targeted.
Example
ino_123Maximum writer sessions admitted by the node.
The deleted namespace that caused the operation to fail.
Example
demoThe index of the failed operation in the request.
Zero-based position of the failed request precondition.
Oldest sequence still promised for incremental replay.
The capability feature key for a not_supported error.
Human-readable error message.
The invalid JSON Pointer, parameter name, CLI flag, or CLI argument.
The request correlation ID also sent in the x-request-id response header.
This deployment does not serve grep queries, the grep index is not enabled, or its backfill has not completed on this namespace
HTTP error body used by LoonFS APIs.
object
The stable machine-readable error code as a string.
The optional machine-readable context for the error code.
object
The Unix-millisecond time when the current writer acquired its epoch, when available.
Epoch that currently owns the namespace.
The writer ID recorded for the current epoch, when available.
Access revision that is actually current for the inode.
Attribute revision that is actually current for the inode.
Current binding token; absent for the root, which has no binding.
Deletion sequence actually active for the inode.
The actual namespace head sequence.
The path actually contained this inode.
Example
ino_123Revision that is actually current; absent when the inode has none.
Change-feed cursor the request asked to resume after.
Idempotency key of the commit the error concerns.
Example
c_f3a9c2d4b6e8417a90c5d2f8e1b7a6c0The fingerprint of the mutation that landed under commit_id, present with committed_seq.
The sequence where this commit ID already landed, when recorded by a durable receipt.
Access revision the request expected to be current.
Attribute revision the request expected to be current.
Opaque binding token supplied by the request.
Deletion sequence the undelete expected to be active.
The head sequence required by the request.
The request expected the path to contain this inode.
Example
ino_123Revision the request expected to be current.
Epoch the failing writer session held when it was displaced.
Inode the failed precondition or operation targeted.
Example
ino_123Maximum writer sessions admitted by the node.
The deleted namespace that caused the operation to fail.
Example
demoThe index of the failed operation in the request.
Zero-based position of the failed request precondition.
Oldest sequence still promised for incremental replay.
The capability feature key for a not_supported error.
Human-readable error message.
The invalid JSON Pointer, parameter name, CLI flag, or CLI argument.
The request correlation ID also sent in the x-request-id response header.
The server cannot complete the request now. Inspect code to determine whether the cause is a deadline, shutdown, load, writer-session admission, required maintenance, or invalid storage credentials. A mutation may still complete after a deadline or lost acknowledgment, so determine its outcome before retrying.
HTTP error body used by LoonFS APIs.
object
The stable machine-readable error code as a string.
The optional machine-readable context for the error code.
object
The Unix-millisecond time when the current writer acquired its epoch, when available.
Epoch that currently owns the namespace.
The writer ID recorded for the current epoch, when available.
Access revision that is actually current for the inode.
Attribute revision that is actually current for the inode.
Current binding token; absent for the root, which has no binding.
Deletion sequence actually active for the inode.
The actual namespace head sequence.
The path actually contained this inode.
Example
ino_123Revision that is actually current; absent when the inode has none.
Change-feed cursor the request asked to resume after.
Idempotency key of the commit the error concerns.
Example
c_f3a9c2d4b6e8417a90c5d2f8e1b7a6c0The fingerprint of the mutation that landed under commit_id, present with committed_seq.
The sequence where this commit ID already landed, when recorded by a durable receipt.
Access revision the request expected to be current.
Attribute revision the request expected to be current.
Opaque binding token supplied by the request.
Deletion sequence the undelete expected to be active.
The head sequence required by the request.
The request expected the path to contain this inode.
Example
ino_123Revision the request expected to be current.
Epoch the failing writer session held when it was displaced.
Inode the failed precondition or operation targeted.
Example
ino_123Maximum writer sessions admitted by the node.
The deleted namespace that caused the operation to fail.
Example
demoThe index of the failed operation in the request.
Zero-based position of the failed request precondition.
Oldest sequence still promised for incremental replay.
The capability feature key for a not_supported error.
Human-readable error message.
The invalid JSON Pointer, parameter name, CLI flag, or CLI argument.
The request correlation ID also sent in the x-request-id response header.