Java ConnectStringParser.getChrootPath方法代码示例

import org.apache.zookeeper.client.ConnectStringParser; //导入方法依赖的package包/类
private ZooMap(Builder builder) {
    this.connectionString = builder.connectionString;
    ConnectStringParser connectStringParser = new ConnectStringParser(connectionString);
    if(connectStringParser.getChrootPath() != null) {
        final String connectionStringForChrootCreation = connectStringParser.getServerAddresses().stream().map(InetSocketAddress::toString).collect(Collectors.joining(","));
        try(final CuratorFramework clientForChrootCreation = newCuratorFrameworkClient(builder, connectionStringForChrootCreation)) {
            startAndBlock(clientForChrootCreation);
            tryIt(() -> clientForChrootCreation.createContainers(connectStringParser.getChrootPath()));
        }
    }
    client = newCuratorFrameworkClient(builder, connectionString);
    this.root = builder.root;
    startAndBlock(client);
    if(!root.isEmpty()) {
        tryIt(() -> client.createContainers(root));
    }
}
 

import org.apache.zookeeper.client.ConnectStringParser; //导入方法依赖的package包/类
/**
 * if ZkConnectString contains namespace path at the end, but it does not exist we should fail
 * @param zkConnect - connect string
 * @param zkClient - zkClient object to talk to the ZK
 */
public static void validateZkNameSpace(String zkConnect, ZkClient zkClient) {
  ConnectStringParser parser = new ConnectStringParser(zkConnect);

  String path = parser.getChrootPath();
  if (Strings.isNullOrEmpty(path)) {
    return; // no namespace path
  }

  LOG.info("connectString = " + zkConnect + "; path =" + path);

  // if namespace specified (path above) but "/" does not exists, we will fail
  if (!zkClient.exists("/")) {
    throw new SamzaException("Zookeeper namespace: " + path + " does not exist for zk at " + zkConnect);
  }
}
 

import org.apache.zookeeper.client.ConnectStringParser; //导入方法依赖的package包/类
/**
 * To create a ZooKeeper client object, the application needs to pass a
 * connection string containing a comma separated list of host:port pairs,
 * each corresponding to a ZooKeeper server.
 * <p>
 * Session establishment is asynchronous. This constructor will initiate
 * connection to the server and return immediately - potentially (usually)
 * before the session is fully established. The watcher argument specifies
 * the watcher that will be notified of any changes in state. This
 * notification can come at any point before or after the constructor call
 * has returned.
 * <p>
 * The instantiated ZooKeeper client object will pick an arbitrary server
 * from the connectString and attempt to connect to it. If establishment of
 * the connection fails, another server in the connect string will be tried
 * (the order is non-deterministic, as we random shuffle the list), until a
 * connection is established. The client will continue attempts until the
 * session is explicitly closed.
 * <p>
 * Added in 3.2.0: An optional "chroot" suffix may also be appended to the
 * connection string. This will run the client commands while interpreting
 * all paths relative to this root (similar to the unix chroot command).
 *
 * @param connectString
 *            comma separated host:port pairs, each corresponding to a zk
 *            server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002" If
 *            the optional chroot suffix is used the example would look
 *            like: "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002/app/a"
 *            where the client would be rooted at "/app/a" and all paths
 *            would be relative to this root - ie getting/setting/etc...
 *            "/foo/bar" would result in operations being run on
 *            "/app/a/foo/bar" (from the server perspective).
 * @param sessionTimeout
 *            session timeout in milliseconds
 * @param watcher
 *            a watcher object which will be notified of state changes, may
 *            also be notified for node events
 * @param canBeReadOnly
 *            (added in 3.4) whether the created client is allowed to go to
 *            read-only mode in case of partitioning. Read-only mode
 *            basically means that if the client can't find any majority
 *            servers but there's partitioned server it could reach, it
 *            connects to one in read-only mode, i.e. read requests are
 *            allowed while write requests are not. It continues seeking for
 *            majority in the background.
 *
 * @throws IOException
 *             in cases of network failure
 * @throws IllegalArgumentException
 *             if an invalid chroot path is specified
 */
public ZooKeeper(String connectString, int sessionTimeout, Watcher watcher,
        boolean canBeReadOnly)
    throws IOException
{
    LOG.info("Initiating client connection, connectString=" + connectString
            + " sessionTimeout=" + sessionTimeout + " watcher=" + watcher);

    watchManager.defaultWatcher = watcher;

    ConnectStringParser connectStringParser = new ConnectStringParser(
            connectString);
    HostProvider hostProvider = new StaticHostProvider(
            connectStringParser.getServerAddresses());
    cnxn = new ClientCnxn(connectStringParser.getChrootPath(),
            hostProvider, sessionTimeout, this, watchManager,
            getClientCnxnSocket(), canBeReadOnly);
    cnxn.start();
}
 

import org.apache.zookeeper.client.ConnectStringParser; //导入方法依赖的package包/类
/**
 * To create a ZooKeeper client object, the application needs to pass a
 * connection string containing a comma separated list of host:port pairs,
 * each corresponding to a ZooKeeper server.
 * <p>
 * Session establishment is asynchronous. This constructor will initiate
 * connection to the server and return immediately - potentially (usually)
 * before the session is fully established. The watcher argument specifies
 * the watcher that will be notified of any changes in state. This
 * notification can come at any point before or after the constructor call
 * has returned.
 * <p>
 * The instantiated ZooKeeper client object will pick an arbitrary server
 * from the connectString and attempt to connect to it. If establishment of
 * the connection fails, another server in the connect string will be tried
 * (the order is non-deterministic, as we random shuffle the list), until a
 * connection is established. The client will continue attempts until the
 * session is explicitly closed.
 * <p>
 * Added in 3.2.0: An optional "chroot" suffix may also be appended to the
 * connection string. This will run the client commands while interpreting
 * all paths relative to this root (similar to the unix chroot command).
 * <p>
 * For backward compatibility, there is another version
 * {@link #ZooKeeper(String, int, Watcher, boolean)} which uses default
 * {@link StaticHostProvider}
 *
 * @param connectString
 *            comma separated host:port pairs, each corresponding to a zk
 *            server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002" If
 *            the optional chroot suffix is used the example would look
 *            like: "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002/app/a"
 *            where the client would be rooted at "/app/a" and all paths
 *            would be relative to this root - ie getting/setting/etc...
 *            "/foo/bar" would result in operations being run on
 *            "/app/a/foo/bar" (from the server perspective).
 * @param sessionTimeout
 *            session timeout in milliseconds
 * @param watcher
 *            a watcher object which will be notified of state changes, may
 *            also be notified for node events
 * @param canBeReadOnly
 *            (added in 3.4) whether the created client is allowed to go to
 *            read-only mode in case of partitioning. Read-only mode
 *            basically means that if the client can't find any majority
 *            servers but there's partitioned server it could reach, it
 *            connects to one in read-only mode, i.e. read requests are
 *            allowed while write requests are not. It continues seeking for
 *            majority in the background.
 * @param aHostProvider
 *            use this as HostProvider to enable custom behaviour.
 * @param clientConfig
 *            (added in 3.5.2) passing this conf object gives each client the flexibility of
 *            configuring properties differently compared to other instances
 * @throws IOException
 *             in cases of network failure
 * @throws IllegalArgumentException
 *             if an invalid chroot path is specified
 */
public ZooKeeper(String connectString, int sessionTimeout, Watcher watcher,
        boolean canBeReadOnly, HostProvider aHostProvider,
        ZKClientConfig clientConfig) throws IOException {
    LOG.info("Initiating client connection, connectString=" + connectString
            + " sessionTimeout=" + sessionTimeout + " watcher=" + watcher);

    if (clientConfig == null) {
        clientConfig = new ZKClientConfig();
    }
    this.clientConfig = clientConfig;
    watchManager = defaultWatchManager();
    watchManager.defaultWatcher = watcher;
    ConnectStringParser connectStringParser = new ConnectStringParser(
            connectString);
    hostProvider = aHostProvider;

    cnxn = new ClientCnxn(connectStringParser.getChrootPath(),
            hostProvider, sessionTimeout, this, watchManager,
            getClientCnxnSocket(), canBeReadOnly);
    cnxn.start();
}
 

import org.apache.zookeeper.client.ConnectStringParser; //导入方法依赖的package包/类
/**
 * To create a ZooKeeper client object, the application needs to pass a
 * connection string containing a comma separated list of host:port pairs,
 * each corresponding to a ZooKeeper server.
 * <p>
 * Session establishment is asynchronous. This constructor will initiate
 * connection to the server and return immediately - potentially (usually)
 * before the session is fully established. The watcher argument specifies
 * the watcher that will be notified of any changes in state. This
 * notification can come at any point before or after the constructor call
 * has returned.
 * <p>
 * The instantiated ZooKeeper client object will pick an arbitrary server
 * from the connectString and attempt to connect to it. If establishment of
 * the connection fails, another server in the connect string will be tried
 * (the order is non-deterministic, as we random shuffle the list), until a
 * connection is established. The client will continue attempts until the
 * session is explicitly closed.
 * <p>
 * Added in 3.2.0: An optional "chroot" suffix may also be appended to the
 * connection string. This will run the client commands while interpreting
 * all paths relative to this root (similar to the unix chroot command).
 * <p>
 * For backward compatibility, there is another version
 * {@link #ZooKeeper(String, int, Watcher, boolean)} which uses
 * default {@link StaticHostProvider}
 *
 * @param connectString
 *            comma separated host:port pairs, each corresponding to a zk
 *            server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002" If
 *            the optional chroot suffix is used the example would look
 *            like: "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002/app/a"
 *            where the client would be rooted at "/app/a" and all paths
 *            would be relative to this root - ie getting/setting/etc...
 *            "/foo/bar" would result in operations being run on
 *            "/app/a/foo/bar" (from the server perspective).
 * @param sessionTimeout
 *            session timeout in milliseconds
 * @param watcher
 *            a watcher object which will be notified of state changes, may
 *            also be notified for node events
 * @param canBeReadOnly
 *            (added in 3.4) whether the created client is allowed to go to
 *            read-only mode in case of partitioning. Read-only mode
 *            basically means that if the client can't find any majority
 *            servers but there's partitioned server it could reach, it
 *            connects to one in read-only mode, i.e. read requests are
 *            allowed while write requests are not. It continues seeking for
 *            majority in the background.
 * @param aHostProvider
 *            use this as HostProvider to enable custom behaviour.
 *
 * @throws IOException
 *             in cases of network failure
 * @throws IllegalArgumentException
 *             if an invalid chroot path is specified
 */
public ZooKeeper(String connectString, int sessionTimeout, Watcher watcher,
        boolean canBeReadOnly, HostProvider aHostProvider)
        throws IOException {
    LOG.info("Initiating client connection, connectString=" + connectString
            + " sessionTimeout=" + sessionTimeout + " watcher=" + watcher);

    watchManager = defaultWatchManager();
    watchManager.defaultWatcher = watcher;

    ConnectStringParser connectStringParser = new ConnectStringParser(
            connectString);
    hostProvider = aHostProvider;

    cnxn = new ClientCnxn(connectStringParser.getChrootPath(),
            hostProvider, sessionTimeout, this, watchManager,
            getClientCnxnSocket(), canBeReadOnly);
    cnxn.start();
}