anlen321 commented on a change in pull request #14684:
URL: https://github.com/apache/flink/pull/14684#discussion_r571761491



##########
File path: 
flink-connectors/flink-connector-hbase-base/src/main/java/org/apache/flink/connector/hbase/options/HBaseOptions.java
##########
@@ -94,6 +94,33 @@
                                     + "Can be set to '0' to disable it. Note, 
both 'sink.buffer-flush.max-size' and 'sink.buffer-flush.max-rows' "
                                     + "can be set to '0' with the flush 
interval set allowing for complete async processing of buffered actions.");
 
+    public static final ConfigOption<Boolean> LOOKUP_ASYNC =
+        ConfigOptions.key("lookup.async")
+            .booleanType()
+            .defaultValue(false)
+            .withDescription("whether to set async lookup.");
+
+    public static final ConfigOption<Long> LOOKUP_CACHE_MAX_ROWS =
+        ConfigOptions.key("lookup.cache.max-rows")
+            .longType()
+            .defaultValue(-1L)
+            .withDescription(
+                "the max number of rows of lookup cache, over this value, the 
oldest rows will "
+                    + "be eliminated. \"cache.max-rows\" and \"cache.ttl\" 
options must all be specified if any of them is "
+                    + "specified. Cache is not enabled as default.");
+
+    public static final ConfigOption<Duration> LOOKUP_CACHE_TTL =
+        ConfigOptions.key("lookup.cache.ttl")
+            .durationType()
+            .defaultValue(Duration.ofSeconds(0))
+            .withDescription("the cache time to live.");
+
+    public static final ConfigOption<Integer> LOOKUP_MAX_RETRIES =
+        ConfigOptions.key("lookup.max-retries")
+            .intType()
+            .defaultValue(3)
+            .withDescription("the max retry times if lookup database failed.");

Review comment:
       Good idea, Can I support cache for HBaseRowDataLookupFunction in the 
current patch?




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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to