Yevhen Tienkaiev

@austintlee yes we need it. To be more specific, imagine situation: You have: 1. Common filters 2. Three specific "use case" filters Now, you wanna do a multi-search query, so...

@austintlee you got it right: > In that case, the change you want should be in the client side: > > https://github.com/opensearch-project/opensearch-java/blob/main/java-client/src/main/java/org/opensearch/client/opensearch/core/SearchRequest.java > > That will match your Solr example....

@jmazzitelli thank you a lot! Frankly it's confuse a little, maybe its worth to consider removing of kiali server chart at all

@jmazzitelli makes sense, I'm just spend a lot of time debugging, yea unfortunately I didn't read that doc precisely=( Maybe add big bold red words under Kiali CR: `Be careful,...

cc @ahus1 I'm totally ok if maintainers edit this PR. Merging this PR helps a lot to others who need to work with Account API e.g. create custom Account Console

@thomasdarimont I'm ok if maintainers will do all changes that they think we need to do. I wanna make sure that this PR will be not forgotten. @stianst I wrote...

@stianst you probably really out of context and didn't read description of the PR. The way how Keycloack organize API there no possibility to make paths: ``` /accounts ``` And...

Same here, optional parameter is very useful if you want to reset optional parameter, otherwise you just can't do that. It's already supported by Spring MVC: ``` @GetMapping(path = "/test")...

I think I was missing something, it seems that contract in Spring MVC is next: Request set name `http://localhost:8132/test?name=hello` will have `hello`. Reset name request `http://localhost:8132/test?name` will have `` -...

@kdavisk6 I think `Optional` will adds nothing from what actually needed, check my previous post for suggested custom class `RequestParamEntity`(name is questionable) and suggested behaviour of it. That behaviour you...