This gives us back a NodesInfoResponse, which we iterate over, getting back
multiple NodeInfo objects.
Now, in Elastic Search 0.18.7, this works:
nodeInfo.getSettings()
But when we upgraded to Elastic Search 0.19.8 it gives us back null.
On debugging, we can see that actually it's not just settings that is null,
most of the fields are also null:
This is because in 0.19, you need to pass specific flags to get the relevant info you are after. NodeInfoRequest#settings(true), NodeInfoRequest#jvm(true).
This gives us back a NodesInfoResponse, which we iterate over, getting back multiple NodeInfo objects.
Now, in Elastic Search 0.18.7, this works:
nodeInfo.getSettings()
But when we upgraded to Elastic Search 0.19.8 it gives us back null.
On debugging, we can see that actually it's not just settings that is null, most of the fields are also null:
On Monday, 13 August 2012 18:15:03 UTC+1, kimchy wrote:
This is because in 0.19, you need to pass specific flags to get the
relevant info you are after. NodeInfoRequest#settings(true),
NodeInfoRequest#jvm(true).
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.