public class EsClusterInfoSelector
extends Object
Storm bolts and spouts don't actually ever run anything on the driver side of a topology submission.
There's a chance for them to do so, but it would require all configurations to be passed into the
object when it is constructed, which means that the code misses out on defaults, cluster level, and
topology level settings.
Since nothing runs in the client, if using Kerberos + Tokens the integration cannot get the cluster
name via Kerberos in order to look up a token by that cluster name later once the Kerberos session
has ended.
Thus, this is a sort of hack that picks a cluster name from the list of tokens on a user in order
to find that token by name later.