davidradl commented on code in PR #27130:
URL: https://github.com/apache/flink/pull/27130#discussion_r2444223438


##########
docs/layouts/shortcodes/generated/execution_config_configuration.html:
##########
@@ -117,6 +117,33 @@
             <td>Duration</td>
             <td>The async timeout for the asynchronous operation to complete, 
including any retries which may occur.</td>
         </tr>
+        <tr>
+            <td><h5>table.exec.async-vector-search.async</h5><br> <span 
class="label label-primary">Batch</span> <span class="label 
label-primary">Streaming</span></td>
+            <td style="word-wrap: break-word;">false</td>
+            <td>Boolean</td>
+            <td>Whether to run an async search function or not. Default to 
false.</td>
+        </tr>
+        <tr>
+            
<td><h5>table.exec.async-vector-search.max-concurrent-operations</h5><br> <span 
class="label label-primary">Batch</span> <span class="label 
label-primary">Streaming</span></td>
+            <td style="word-wrap: break-word;">10</td>
+            <td>Integer</td>
+            <td>The max number of async i/o operation that the async vector 
search can trigger.</td>
+        </tr>
+        <tr>
+            <td><h5>table.exec.async-vector-search.output-mode</h5><br> <span 
class="label label-primary">Batch</span> <span class="label 
label-primary">Streaming</span></td>
+            <td style="word-wrap: break-word;">ORDERED</td>
+            <td><p>Enum</p></td>
+            <td>Output mode for async vector search, which describes whether 
or not the output should attempt to be ordered or not.
+The supported options are:
+ALLOW_UNORDERED means the operator emits the result when execution finishes. 
The planner will attempt to use ALLOW_UNORDERED when it doesn't affect the 
correctness of the results.

Review Comment:
   nit: affect -> effect



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