You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My test code uses the "fs" snapshot repository type, and I rescue Elasticsearch::Transport::Transport::Errors::NotFound when a snapshot doesn't exist. I ran the same code with the s3 backend, and got a Elasticsearch::Transport::Transport::Errors::InternalServerError instead:
{
"error":"SnapshotException[[repository_name:index_prefix-2014.05.18] failed to get snapshots]; nested: IOException[Failed to get [snapshot-index_prefix-2014.05.18]]; nested: AmazonS3Exception[Status Code: 404, AWS Service: Amazon S3, AWS Request ID: 7B94A86E8FDBCE53, AWS Error Code: NoSuchKey, AWS Error Message: The specified key does not exist.];",
{
"error":"SnapshotException[[repository_name:index_prefix-2014.05.18] failed to get snapshots]; nested: IOException[Failed to get [snapshot-index_prefix-2014.05.18]]; nested: AmazonS3Exception[Status Code: 404, AWS Service: Amazon S3, AWS Request ID: 7B94A86E8FDBCE53, AWS Error Code: NoSuchKey, AWS Error Message: The specified key does not exist.];",
"status":500
}
"status":500
} (Elasticsearch::Transport::Transport::Errors::InternalServerError)InternalServerError
Since the code amazon is returning is 404, I'm assuming this is a bug?
The text was updated successfully, but these errors were encountered:
My test code uses the "fs" snapshot repository type, and I rescue Elasticsearch::Transport::Transport::Errors::NotFound when a snapshot doesn't exist. I ran the same code with the s3 backend, and got a Elasticsearch::Transport::Transport::Errors::InternalServerError instead:
Since the code amazon is returning is 404, I'm assuming this is a bug?
The text was updated successfully, but these errors were encountered: