Andriy Redko

Thanks a lot @finnegancarroll , it looks like we are at crossroads now: should we move forward with protobuf (since the latency wins are moderate) or (may be) move forward...

> Additional benchmarks comparing protobuf to native protocol with the same inflated DocumentFields size as used [here](https://github.com/opensearch-project/OpenSearch/issues/15308#issuecomment-2418350882). Thanks @finnegancarroll , `writeToNativeBench` & `writeToProtoBench` are really close, I think XContent ones...

> @reta What do you think of this PR now? Instead of creating a new extension point in the IdentityPlugin, I changed this PR to remove the code from the...

@cwperks I think it looks pretty good, a few minor comments but LGTM otherwise, thanks!

@amberzsy @dblock I have two questions please: 1. `3.x` comes with HTTP/2 support (clients + server) out of the box, what are the tangible benefits of using gRPC here? 2....

> I don't know if gRPC would show better performance when compared to any other HTTP/2-based solution that sent protobuf blobs but I think it is worth experimenting with some...

@cwperks none of the OpenSearch plugins have access to the file system outside `OPENSEARCH_PATH_CONFIG` (and although technically possible, it is not recommended). @c3-davidtran this is clearly an issue that was...

> @reta Can you expand upon your thoughts on solving it through a setting? Absolutely, thanks @cthtrifork . The idea is to introduce the setting like this: ``` /** The...

> What are people thoughts? @chengwushi-netapp @reta\n@peternied any opinions on approaches? Thanks @cthtrifork , patching the security policy is not recommended (it opens up yet another can of worms), soft...

> Hello @cwperks @peternied @reta > It's been quite some time since we last discussed this issue. We are still encountering this issue in version 2.18 so would you >...