Package org.apache.hadoop.registry.client.types

Interface AddressTypes

@Public @Evolving public interface AddressTypes
Enum of address types -as integers. Why integers and not enums? Cross platform serialization as JSON

  • Field Details

    • ADDRESS_HOSTNAME_AND_PORT

      static final String ADDRESS_HOSTNAME_AND_PORT
      hostname/FQDN and port pair: "host/port". The host/domain name and port are set as separate strings in the address list, e.g. 
         ["namenode.example.org", "9870"]
      See Also:

    • ADDRESS_HOSTNAME_FIELD

      static final String ADDRESS_HOSTNAME_FIELD
      See Also:

    • ADDRESS_PORT_FIELD

      static final String ADDRESS_PORT_FIELD
      See Also:

    • ADDRESS_PATH

      static final String ADDRESS_PATH
      Path /a/b/c style: "path". The entire path is encoded in a single entry 
         ["/users/example/dataset"]
      See Also:

    • ADDRESS_URI

      static final String ADDRESS_URI
      URI entries: "uri". 
         ["http://example.org"]
      See Also:

    • ADDRESS_ZOOKEEPER

      static final String ADDRESS_ZOOKEEPER
      Zookeeper addresses as a triple : "zktriple".

      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.
      See Also:

    • ADDRESS_OTHER

      static final String ADDRESS_OTHER
      Any other address: "".
      See Also: