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
..
main	Support Client and RoleMapping in custom Realms (#50950)	2020-01-14 15:26:41 +11:00
test/java/org/elasticsearch/example	NodeInfo response should use a collection rather than fields (#54460) (#55132)	2020-04-13 17:18:39 -04:00