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.5.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.5.0
File Size Uploaded Provenance
capo_sagemaker_featurestore_runtime-0.5.0.tar.gz 72.2 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 182.9 kB

Release files / capo_sagemaker_featurestore_runtime-0.5.0.tar.gz

Download URL capo_sagemaker_featurestore_runtime-0.5.0.tar.gz
Size 72.2 kB
Tags Source
SHA-256 checksum
How to use checksums
ad4f162c9e64e2fa2fb911e71d1a08de38dc40c5d96caf8bbc5bd4552d94823c
BLAKE2b-256 checksum
How to use checksums
eb841169bdd44895616bc04e20bf21906e41d12341e8282127c3ce82dd9d1f21
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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.5.0-py3-none-any.whl

Download URL capo_sagemaker_featurestore_runtime-0.5.0-py3-none-any.whl
Size 110.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
576720a0c02199073723ef4fe7372ec351a662016cda8b0e393dedeecac94bff
BLAKE2b-256 checksum
How to use checksums
b603e74dd68d56782a9ac86536f2f429ab0a4612421b0964543d4df431302cc8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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.5.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