This used to happen before we added a workaround in {{ElasticsearchRequest.Builder#multiValuedParam}} disabled some tests :
{noformat}
HSEARCH400007: Elasticsearch request failed: HSEARCH400090: Elasticsearch response indicates a failure.
Request: POST /indexname/_search with parameters {size=10000, routing=someText_8,someText_9,someText_6,someText_7,someText_4,someText_5,someText_2,someText_3,someText_0,someText_1}
Response: 403 'Forbidden' with body
{
"message": "The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details."
}
{noformat}
It I wasn ' s probably because t able to pinpoint the aws-v4-signer library does not sort multi-valued parameters actual problem . We should fix the library Everything is fine as long as we use only one routing key , ask for a release and upgrade to a newer version but as soon as we used multiple keys, all hell breaks loose . .. |
|
