Skip to main content

Getting Started

Installation

pip install capo-sagemaker-featurestore-runtime

Usage

from capo_sagemaker_featurestore_runtime import AsyncSageMakerFeatureStoreRuntimeClient


async def main():
    async with AsyncSageMakerFeatureStoreRuntimeClient() as sage_maker_feature_store_runtime:
        # Example: call the batch_get_record operation
        response = await sage_maker_feature_store_runtime.batch_get_record()
        print(response["records"])

Pagination

Some operations in this SDK support pagination. If the operation supports pagination it will have an iter_ prefixed method that returns an async iterator.

from capo_sagemaker_featurestore_runtime import AsyncSageMakerFeatureStoreRuntimeClient


async def main():
    async with AsyncSageMakerFeatureStoreRuntimeClient() as sage_maker_feature_store_runtime:
        # Example: paginate over list_records
        async for item in sage_maker_feature_store_runtime.iter_list_records():
            print(item)

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_sagemaker_featurestore_runtime import AsyncSageMakerFeatureStoreRuntimeClient
from capo_sagemaker_featurestore_runtime.error import AccessForbidden


async def main():
    async with AsyncSageMakerFeatureStoreRuntimeClient() as sage_maker_feature_store_runtime:
        try:
            await sage_maker_feature_store_runtime.batch_get_record()
        except AccessForbidden as e:
            print(f"Error: {e}")
            print(e.data)  # additional error data

Retrying

The SDK retries failed operations automatically. Retry behaviour follows the Smithy specification: errors are retried based on their is_retryable and is_throttling_error attributes. Throttling errors use a longer base delay. Network-level failures (connection errors and timeouts) are also retried. Non-retryable errors, such as client errors without the @retryable trait, are raised immediately without further attempts.

The number of attempts defaults to 3 and can be changed at the client level via retry_max_attempts, or per call via config_overrides.

from capo_sagemaker_featurestore_runtime import AsyncSageMakerFeatureStoreRuntimeClient


async def main():
    async with AsyncSageMakerFeatureStoreRuntimeClient() as sage_maker_feature_store_runtime:
        # Default: 3 attempts for every operation
        response = await sage_maker_feature_store_runtime.batch_get_record()

        # Override per operation
        response = await sage_maker_feature_store_runtime.batch_get_record(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await sage_maker_feature_store_runtime.batch_get_record(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-sagemaker-featurestore-runtime 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for capo-sagemaker-featurestore-runtime 0.3.0
File Size Uploaded Provenance
capo_sagemaker_featurestore_runtime-0.3.0.tar.gz 72.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-sagemaker-featurestore-runtime 0.3.0
File Interpreter ABI Platform
capo_sagemaker_featurestore_runtime-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 182.5 kB

Release files / capo_sagemaker_featurestore_runtime-0.3.0.tar.gz

Download URL capo_sagemaker_featurestore_runtime-0.3.0.tar.gz
Size 72.1 kB
Tags Source
SHA-256 checksum
How to use checksums
6c0ff20f9b2f83fa8f719c47927f9adf2abc0c81e5e9179755e0f5c4ee22db58
BLAKE2b-256 checksum
How to use checksums
d1908e2e7395ca4586263622a3bee5ed6a09de475ae385c2eab1f5fe03307f2a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / capo_sagemaker_featurestore_runtime-0.3.0-py3-none-any.whl

Download URL capo_sagemaker_featurestore_runtime-0.3.0-py3-none-any.whl
Size 110.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
593e8907f8ab4bbc6e656343a37c2bf8275b1411132cbfb0f801fa6d57dd2aa9
BLAKE2b-256 checksum
How to use checksums
34fa849e9944951611ff8f5045557506607ce5758d9f5f64a52dd507f4887c30
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for capo-sagemaker-featurestore-runtime 0.3.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page