Why using ThreadLocal<GraphService.Client> in GraphClientImpl? about nebula-java

[Nicole00]

Thanks for your attention to nebula java client.

1. We used ThreadLocal to achieve thread safe, in case the executions are disorderly. If we share a client in different threads, the "use space" execution will cause that all operations in other threads are executed on this space.
2. Your code lost the connect() operation, and your first executeQuery operation will throw ConnectionException("thrift rpc call failed")
   The GraphClient's usage is:

GraphClient graphClient = new GraphClientImpl(addresses);
graphClient.connect();
graphClient.executeQuery(gql);

new Thread(() -> {
        graphClient.connect();
        graphClient.executeQuery(gql);
    }).start();

[RaulGuo]

@Nicole00 Thank you for your reply. So, for question one, if I can guarante in my application that differenct thread using the same thriftClient will execute with no switch space operation, I can use thriftClient across multi thread, right?

[Nicole00]

use thriftClient across multi thread, right

Yeah，and please guarantee that your client is connected before any execution.