- Newest
- Most votes
- Most comments
Amazon OpenSearch Serverless supports ingestion with "id" if collection type is search, document ingestion with id is not supported for time-series collection.
Can you confirm, what kind of collection you are creating? Also, it has been documented in the AWS docs under aoss:WriteDocument here: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless-genref.html#serverless-operations PUT <index>/_create/<id> (for search collection types only)
Let me know if this helps.
I believe you are correct - I was using a time-series collection. I didn't see that comment in the documentation, nor did I see the note in the collection differences here: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless-overview.html#serverless-usecase. Thank you.
What would be the recommend practice to ensure idempotency of records being batched into an index?
I am new to AOSS. I have a serverless vector opensearch collection. I am trying to use langchain to add embeddings to the db
My code -
def opensearchvector(docs, embedding_function, opensearch_url, awsauth, index_name): return OpenSearchVectorSearch.from_documents( docs, embedding_function, opensearch_url=opensearch_url, http_auth=awsauth, use_ssl=True, verify_certs=True, http_compress = True, connection_class=RequestsHttpConnection, index_name = index_name, engine="faiss" )
This worked for me a few days ago, but recently it has started giving me the illegal_document_exception - ('1 document(s) failed to index.', [{'index': {'_index': 'json-test-index', '_id': 'cec36b7c-7140-45cb-aaa0-ddede89ed5af', 'status': 400, 'error': {'type': 'illegal_argument_exception', 'reason': 'Document ID is not supported in create/index operation request'}. I am not adding any indexes to my documents but still i get this error
Hi, any updates on this? I am running the exact same issue as @Ayush Bhura
Relevant content
- Accepted Answerasked 5 months ago
- asked 6 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
I have switched to using Domain-based OpenSearch and this problem goes away. It's something to do with Serverless service not adhering to the OpenSearch bulk API