| Name | Type | Description |
|---|---|---|
token | str | TokenProvider | None | Default: NoneAPI token for Astra DB usage, either in the form of a string
or a subclass of |
ext_callers | list[tuple[str | None, str | None] | str | None] | None | Default: None |
component_name | str | None | Default: None |
collection_embedding_api_key | str | EmbeddingHeadersProvider | None | Default: None |
collection_reranking_api_key | str | RerankingHeadersProvider | None | Default: None |
Create a copy, possibly with changed attributes.
This method creates a shallow copy of this environment. If a parameter is passed and differs from None, it will replace the corresponding value in the copy.
The method allows changing only the parameters that ensure the copy is
functional and does not trigger side-effects:
for example, one cannot create a copy acting on a new collection.
In those cases, one should create a new instance of AstraDBVectorStore
from scratch.
additional custom (caller_name, caller_version) pairs to attach to the User-Agent header when issuing Data API requests.
a value for the LangChain component name to use when identifying the originator of the Data API requests.
the API Key to supply in each Data API
request if necessary. This is necessary if using the Vectorize
feature and no secret is stored with the database.
In order to suppress the API Key in the copy, explicitly pass
astrapy.authentication.EmbeddingAPIKeyHeaderProvider(None).
for usage of server-side reranking services
within Astra DB. With this parameter one can supply an API Key
that will be passed to Astra DB with each data request.
This parameter can be either a string or a subclass of
astrapy.authentication.RerankingHeadersProvider.
This is useful when the service is configured for the collection,
but no corresponding secret is stored within
Astra's key management system.
