|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
@InterfaceAudience.Public @InterfaceStability.Evolving public interface AddressTypes
Enum of address types -as integers. Why integers and not enums? Cross platform serialization as JSON
Field Summary | |
---|---|
static String |
ADDRESS_HOSTNAME_AND_PORT
hostname/FQDN and port pair: "host/port". |
static String |
ADDRESS_HOSTNAME_FIELD
|
static String |
ADDRESS_OTHER
Any other address: "". |
static String |
ADDRESS_PATH
Path /a/b/c style: "path". |
static String |
ADDRESS_PORT_FIELD
|
static String |
ADDRESS_URI
URI entries: "uri". |
static String |
ADDRESS_ZOOKEEPER
Zookeeper addresses as a triple : "zktriple". |
Field Detail |
---|
static final String ADDRESS_HOSTNAME_AND_PORT
["namenode.example.org", "50070"]
static final String ADDRESS_HOSTNAME_FIELD
static final String ADDRESS_PORT_FIELD
static final String ADDRESS_PATH
/a/b/c
style: "path".
The entire path is encoded in a single entry
["/users/example/dataset"]
static final String ADDRESS_URI
["http://example.org"]
static final String ADDRESS_ZOOKEEPER
These are provide as a 3 element tuple of: hostname, port and optionally path (depending on the application)
A single element would be
["zk1","2181","/registry"]An endpoint with multiple elements would list them as
[ ["zk1","2181","/registry"] ["zk2","1600","/registry"] ]the third element in each entry , the path, MUST be the same in each entry. A client reading the addresses of an endpoint is free to pick any of the set, so they must be the same.
static final String ADDRESS_OTHER
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |