OpenSearch/modules/transport-netty4
William Brafford 52bebec51f
NodeInfo response should use a collection rather than fields (#54460) (#55132)
This is a first cut at giving NodeInfo the ability to carry a flexible
list of heterogeneous info responses. The trick is to be able to
serialize and deserialize an arbitrary list of blocks of information. It
is convenient to be able to deserialize into usable Java objects so that
we can aggregate nodes stats for the cluster stats endpoint.

In order to provide a little bit of clarity about which objects can and
can't be used as info blocks, I've introduced a new interface called
"ReportingService."

I have removed the hard-coded getters (e.g., getOs()) in favor of a
flexible method that can return heterogeneous kinds of info blocks
(e.g., getInfo(OsInfo.class)). Taking a class as an argument removes the
need to cast in the client code.
2020-04-13 17:18:39 -04:00
..
licenses Upgrade netty to 4.1.45.Final (#51689) 2020-02-18 09:11:29 -07:00
src NodeInfo response should use a collection rather than fields (#54460) (#55132) 2020-04-13 17:18:39 -04:00
build.gradle [7.x] Optimize which Rest resources are used by the Rest tests… (#53766) 2020-03-19 12:28:59 -05:00