joao-r-reis commented on code in PR #2037:
URL: 
https://github.com/apache/cassandra-java-driver/pull/2037#discussion_r2352636601


##########
core/src/main/java/com/datastax/oss/driver/api/core/tracker/RequestIdGenerator.java:
##########
@@ -0,0 +1,74 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package com.datastax.oss.driver.api.core.tracker;
+
+import com.datastax.oss.driver.api.core.cql.Statement;
+import com.datastax.oss.driver.api.core.session.Request;
+import 
com.datastax.oss.protocol.internal.util.collection.NullAllowingImmutableMap;
+import edu.umd.cs.findbugs.annotations.NonNull;
+import java.nio.ByteBuffer;
+import java.nio.charset.StandardCharsets;
+import java.util.Map;
+
+/**
+ * Interface responsible for generating request IDs.
+ *
+ * <p>Note that all request IDs have a parent/child relationship. A "parent 
ID" can loosely be
+ * thought of as encompassing a sequence of a request + any attendant retries, 
speculative
+ * executions etc. It's scope is identical to that of a {@link
+ * com.datastax.oss.driver.internal.core.cql.CqlRequestHandler}. A "request 
ID" represents a single
+ * request within this larger scope. Note that a request corresponding to a 
request ID may be
+ * retried; in that case the retry count will be appended to the corresponding 
identifier in the
+ * logs.
+ */
+public interface RequestIdGenerator {
+  /**
+   * Generates a unique identifier for the session request. This will be the 
identifier for the
+   * entire `session.execute()` call. This identifier will be added to logs, 
and propagated to
+   * request trackers.
+   *
+   * @return a unique identifier for the session request
+   */
+  String getParentId();
+
+  /**
+   * Generates a unique identifier for the node request. This will be the 
identifier for the CQL
+   * request against a particular node. There can be one or more node requests 
for a single session
+   * request, due to retries or speculative executions. This identifier will 
be added to logs, and
+   * propagated to request trackers.
+   *
+   * @param statement the statement to be executed
+   * @param parentId the session request identifier
+   * @return a unique identifier for the node request
+   */
+  String getRequestId(@NonNull Request statement, @NonNull String parentId);

Review Comment:
   I think Session Request and Node Request are easier to explain to users in 
the context of the request tracker API but I do admit there wasn't a whole lot 
of discussion on these names when we went for these on the C# driver 
implementation. The java driver request tracker API docs refer to "node level" 
requests so making that leap to "Node Request" shouldn't be hard. I'd argue 
that "Message" is less clear since we don't have that name anywhere in the 
request tracker documentation AFAIK. SessionRequest is not an ideal name but I 
didn't want it to just be "Request" and the "node level" request be called 
"Node Request", I wanted an additional qualifier so I went with "Session" but 
it could have been something different like "Parent Request" Idk



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to