elasticsearch-net-aws icon indicating copy to clipboard operation
elasticsearch-net-aws copied to clipboard

Add-on to Elasticsearch.Net & NEST for using AWS's elasticsearch service.

Results 4 elasticsearch-net-aws issues
Sort by recently updated
recently updated
newest added

I'm trying to use v7.1.0 with Elasticsearch.net v7.7 and Nest v7.14.1. After upgrading from v6.0, I am now getting 403 response from my AWS Elasticsearch endpoint. I found out that...

Just updating from Elasticsearch.Net.Aws 7.2.1 to 7.2.2, causes 403 from AWS OpenSearch cluster

[{"_id":"66bdfed38d15a6f26f0b0184","body":"That's odd. Nothing changed related to signing. Here's the diff for 7.2.1 -> 7.2.2\r\n\r\nhttps:\/\/github.com\/bcuff\/elasticsearch-net-aws\/commit\/1c71ad16e7aacddb43903cfae87197d45c624473","issue_id":1707477241993,"origin_id":1478626730,"user_origin_id":504266,"create_time":1679435107,"update_time":1679435107,"id":1723727571760,"updated_at":"2024-08-15T13:12:51.759000Z","created_at":"2024-08-15T13:12:51.759000Z"},{"_id":"66bdfed38d15a6f26f0b0185","body":"That is strange. This happens to be running under an older WebAPI REST service with TargetFrameworkVersion=v4.7.2, I wonder if the framework target changes altered something? That and Newtonsoft is about it... really weird.","issue_id":1707477241993,"origin_id":1479926869,"user_origin_id":11542134,"create_time":1679503966,"update_time":1679503966,"id":1723727571766,"updated_at":"2024-08-15T13:12:51.765000Z","created_at":"2024-08-15T13:12:51.765000Z"},{"_id":"66bdfed38d15a6f26f0b0186","body":"Did the endpoint change? There's another [reported issue](https:\/\/github.com\/bcuff\/elasticsearch-net-aws\/issues\/72) related to the URL changing due to the open search service domain changing.\r\n\r\nIf it's not that, it could be .NET Framework. There are a few weird things the Uri class does to change certain characters. I've run into that in the past. My memory is fuzzy on exactly what the issue was around that though.","issue_id":1707477241993,"origin_id":1479992809,"user_origin_id":504266,"create_time":1679506570,"update_time":1679506570,"id":1723727571770,"updated_at":"2024-08-15T13:12:51.769000Z","created_at":"2024-08-15T13:12:51.769000Z"},{"_id":"66bdfed38d15a6f26f0b0187","body":"To isolate the problem, the only thing I did was update this one single NuGet package 7.2.1 -> 7.2.2 and it broke, then rolled back to 7.2.1 and it started working (no changes to our AWS-side at all). I went back and forth a few times to make sure I was seeing it right. As a workaround for now we'll have to stick with Elasticsearch.Net.Aws 7.2.1 and just remember we can't update it, but I thought I'd ask to see what could be going on. Very strange indeed.","issue_id":1707477241993,"origin_id":1481334208,"user_origin_id":11542134,"create_time":1679583007,"update_time":1679583007,"id":1723727571773,"updated_at":"2024-08-15T13:12:51.773000Z","created_at":"2024-08-15T13:12:51.773000Z"},{"_id":"66bdfed38d15a6f26f0b0188","body":"Definitely strange. Maybe it was the target framework change from 461 to 481?\r\n\r\nhttps:\/\/github.com\/bcuff\/elasticsearch-net-aws\/commit\/1c71ad16e7aacddb43903cfae87197d45c624473#diff-3625fd895652561b68373f0741d92727c2e6b1cc8302e8e4cda724e71e7d2536L4\r\n\r\nThat line is the only thing that changed in the released package. The rest of the changes were to tests.","issue_id":1707477241993,"origin_id":1481366632,"user_origin_id":504266,"create_time":1679584086,"update_time":1679584086,"id":1723727571776,"updated_at":"2024-08-15T13:12:51.776000Z","created_at":"2024-08-15T13:12:51.776000Z"},{"_id":"66bdfed38d15a6f26f0b0189","body":"We are experiencing this issue as well. Downgrading to 7.2.1 worked.","issue_id":1707477241993,"origin_id":1581225336,"user_origin_id":5931533,"create_time":1686158099,"update_time":1686158099,"id":1723727571780,"updated_at":"2024-08-15T13:12:51.780000Z","created_at":"2024-08-15T13:12:51.780000Z"}] comment

Just updating from Elasticsearch.Net.Aws 7.2.1 to 7.2.2 and we start receiving a 403 from our AWS OpenSearch cluster (running in elastisearch compatibility mode) Elasticsearch.Net.ElasticsearchClientException: The remote server returned an error:...

Highlight error with only 2 characters

[{"_id":"66bdfeda8d15a6f26f0b018c","body":"It sounds like you're raising an issue with search functionality. This library is only an add-on to Elasticsearch.Net that enables one to sign requests for AWS Elasticsearch service. Perhaps you should report your issue [here](https:\/\/github.com\/elastic\/elasticsearch-net).","issue_id":1707477242039,"origin_id":1485272324,"user_origin_id":504266,"create_time":1679929111,"update_time":1679929144,"id":1723727578621,"updated_at":"2024-08-15T13:12:58.620000Z","created_at":"2024-08-15T13:12:58.620000Z"}] comment

I search text "abe" and the result is correct for highlight value "<Abe>rGain" but if I used just 2 characters "ab" the highlight result is incorrect because highlight whole word...

OpenSearch Serverless

[{"_id":"66bdfedebdced2948705d84f","body":"Hey Kelly thanks for raising the issue. Any chance you can share your fork? No big deal if not. I have enough to go on but I might not get around to it for a little while.\r\n\r\nAlso - I'll look into that reflection bit. That always annoyed me and I never figured out a way around using reflection. Might not have been possible in the 4.8.1 version but I think we can deprecate support for .NET Framework at this point.","issue_id":1707477242124,"origin_id":1446729468,"user_origin_id":504266,"create_time":1677518321,"update_time":1677518321,"id":1723727582258,"updated_at":"2024-08-15T13:13:02.257000Z","created_at":"2024-08-15T13:13:02.257000Z"},{"_id":"66bdfedebdced2948705d850","body":"Hi Brandon,\r\n\r\nIt turns out I didn't end up doing the changes in the fork after all, as I was able to replace the whole library with a small class as above. That said, I've put the same code into the library and I think it will work as-is. I've pushed it as a wip commit on my fork so you can see the new code. Sorry for not cleaning up, I just have way too many things going on to give it the attention it deserves, so I figured I'd just share what I could with the time I have.\r\n\r\nWith the changes I made, you don't need the reflection or the other class (http handler) at all. Though just for your information, the fix to the http message handler to remove the reflection is there anyway (DelgatingHandler is the way to do that). That said, you don't need it anymore if you do everything in the connection object.\r\n\r\nKelly","issue_id":1707477242124,"origin_id":1446884220,"user_origin_id":53208,"create_time":1677524252,"update_time":1677524252,"id":1723727582269,"updated_at":"2024-08-15T13:13:02.269000Z","created_at":"2024-08-15T13:13:02.269000Z"}] comment

Amazon has recently introduced a new serverless option for opensearch. In their infinite wisdom, they decided to change the service name for the purposes of signing HTTP requests from 'es'...