Elasticsearch Bulk Update scenarios with 'IndexNotFoundException' Despite Index Existing in Version 8.3
Quick question that's been bugging me - I'm prototyping a solution and I'm stuck on something that should probably be simple. I'm currently working with an scenario when trying to perform a bulk update operation in Elasticsearch 8.3. The bulk request is returning an behavior that states `IndexNotFoundException[no such index]`. However, I can confirm that the index exists and is correctly configured. Here's the bulk request I'm attempting to run: ```json POST _bulk { "update": { "_index": "my_index", "_id": "1" }} { "doc": { "field": "new_value" } } { "update": { "_index": "my_index", "_id": "2" }} { "doc": { "field": "another_value" } } ``` I've double-checked the index name in the request, and it matches exactly with what I see in Kibana. I also verified that I have the required permissions to access this index. Additionally, I have created the index with the following mappings: ```json PUT my_index { "mappings": { "properties": { "field": { "type": "text" } } } } ``` The scenario arises only when I execute the bulk update, while individual updates using the same index and document IDs work just fine. I've tried hitting the bulk endpoint directly as well as via the Elasticsearch Java client, but I get the same behavior in both cases. Could this be related to the way Elasticsearch handles the bulk requests or something unique to the index configuration? Any insights would be appreciated! Am I missing something obvious? The stack includes Json and several other technologies. Thanks, I really appreciate it! I'm working in a Linux environment. Any help would be greatly appreciated! Is there a simpler solution I'm overlooking?