Modules§
- batch_
granularity_ mismatch - containerized_
extractor_ container_ failed - containerized_
extractor_ not_ found - containerized_
extractor_ timestamp_ metadata_ missing - containerized_
extractor_ unauthorized_ password_ access - containerized_
extractors_ not_ found - dataset_
file_ not_ found - dataset_
not_ found - empty_
multipart_ upload - failed_
to_ download_ file - failed_
to_ download_ file_ user_ error - frame_
count_ timestamps_ mismatch - incompatible_
connection_ type_ and_ log_ query - incompatible_
file_ for_ dataset - incompatible_
inputs - incorrect_
size_ bytes - ingest_
job_ not_ cancellable - ingest_
job_ not_ compatible_ for_ rerun - ingest_
job_ not_ found - invalid_
bucket - invalid_
container_ image - invalid_
custom_ timestamp_ format - invalid_
default_ tag - invalid_
output_ file_ format - invalid_
s3_ path - invalid_
url - missing_
metadata_ for_ reingest - null_
key - parallel_
reingest_ into_ dataset_ v1 - recursive_
reingest - reingest_
too_ many_ files - resource_
not_ found_ or_ unauthorized - run_
bounds_ inverted - s3_
path_ not_ found - sign_
download_ path_ outside_ uploads_ bucket - sign_
download_ unauthorized - streaming_
session_ not_ found - unsupported_
ingest_ source - unsupported_
request_ type_ for_ re_ ingest - workspace_
resource_ mismatch
Structs§
- Batch
Granularity Mismatch - All dataset granularities must match.
- Containerized
Extractor Container Failed - Containerized
Extractor NotFound - Containerized
Extractor Timestamp Metadata Missing - Neither the containerized extractor (or its active container image) nor the ingest request provides timestamp metadata, so the extractor output cannot be indexed. Register the image with default timestamp metadata or supply it on the request.
- Containerized
Extractor Unauthorized Password Access - The user is not authorized to access the containerized extractor password.
- Containerized
Extractors NotFound - Dataset
File NotFound - The target dataset file could not be found.
- Dataset
NotFound - The target dataset could not be found.
- Empty
Multipart Upload - Failed
ToDownload File - Failed
ToDownload File User Error - Frame
Count Timestamps Mismatch - Incompatible
Connection Type AndLog Query - Incompatible
File ForDataset - Incompatible
Inputs - The inputs provided to the ingest job are incompatible with each other
- Incorrect
Size Bytes - Ingest
JobNot Cancellable - The ingest job exists but is in a terminal state (COMPLETED, FAILED, or CANCELLED) and therefore cannot be cancelled.
- Ingest
JobNot Compatible ForRerun - The ingest job exists but is not compatible to be re-run.
- Ingest
JobNot Found - Invalid
Bucket - Invalid
Container Image - Invalid
Custom Timestamp Format - Invalid
Default Tag - Invalid
Output File Format - Invalid
S3Path - Invalid
Url - Missing
Metadata ForReingest - The timestamp metadata required to reingest the dataset is missing and must be provided in the request.
- NullKey
- Parallel
Reingest Into Dataset V1 - Cannot ingest multiple datasets in parallel into older datasets. It is recommended to reingest all source datasets and the target dataset into a new dataset destination.
- Recursive
Reingest - The target dataset is included in the source datasets.
- Reingest
TooMany Files - The number of files to reingest is too large.
- Resource
NotFound OrUnauthorized - The resource referenced by an upload’s
resourcefield was not found or the caller is not authorized to access it. Returned as NOT_FOUND (rather than PERMISSION_DENIED) to avoid leaking existence information about resources the caller cannot see. - RunBounds
Inverted - S3Path
NotFound - Sign
Download Path Outside Uploads Bucket - Sign
Download Unauthorized - Streaming
Session NotFound - The streaming session could not be found.
- Unsupported
Ingest Source - Unsupported
Request Type ForRe Ingest - Workspace
Resource Mismatch - Both
workspaceandresourcewere set on the upload request, but the workspace derived from the resource does not match the explicitly-supplied workspace. Returned as a defensive sanity check so callers don’t accidentally believe they’re uploading to one workspace while the file is actually being routed to another.