alexeykudinkin commented on code in PR #7880:
URL: https://github.com/apache/hudi/pull/7880#discussion_r1099043289


##########
hudi-client/hudi-client-common/src/main/java/org/apache/hudi/config/HoodieWriteConfig.java:
##########
@@ -165,11 +165,11 @@ public class HoodieWriteConfig extends HoodieConfig {
       
.withValidValues(Arrays.stream(ExecutorType.values()).map(Enum::name).toArray(String[]::new))
       .sinceVersion("0.13.0")
       .withDocumentation("Set executor which orchestrates concurrent producers 
and consumers communicating through a message queue."
-          + "BOUNDED_IN_MEMORY(default): Use LinkedBlockingQueue as a bounded 
in-memory queue, this queue will use extra lock to balance producers and 
consumer"
+          + "BOUNDED_IN_MEMORY: Use LinkedBlockingQueue as a bounded in-memory 
queue, this queue will use extra lock to balance producers and consumer"
           + "DISRUPTOR: Use disruptor which a lock free message queue as inner 
message, this queue may gain better writing performance if lock was the 
bottleneck. "
-          + "SIMPLE: Executor with no inner message queue and no inner lock. 
Consuming and writing records from iterator directly. Compared with BIM and 
DISRUPTOR, "
+          + "SIMPLE(default): Executor with no inner message queue and no 
inner lock. Consuming and writing records from iterator directly. Compared with 
BIM and DISRUPTOR, "
           + "this queue has no need for additional memory and cpu resources 
due to lock or multithreading, but also lost some benefits such as speed limit. 
"
-          + "Although DISRUPTOR_EXECUTOR and SIMPLE are still in 
experimental.");
+          + "Although DISRUPTOR and SIMPLE are still in experimental.");

Review Comment:
   Let's remove SIMPLE from experimental



-- 
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]

Reply via email to