Update fdb 620 includes to 6.2.20

Author: Speedy37

foundationdb-gen/include/620/fdb.options

@@ -158,7 +158,7 @@ description is not currently required but encouraged.
             defaultFor="500"/>
     <Option name="transaction_retry_limit" code="501"
             paramType="Int" paramDescription="number of times to retry"
-            description="Set a timeout in milliseconds which, when elapsed, will cause a transaction automatically to be cancelled. This sets the ``retry_limit`` option of each transaction created by this database. See the transaction option description for more information." 
+            description="Set a maximum number of retries after which additional calls to ``onError`` will throw the most recently seen error code. This sets the ``retry_limit`` option of each transaction created by this database. See the transaction option description for more information." 
             defaultFor="501"/>
     <Option name="transaction_max_retry_delay" code="502"
             paramType="Int" paramDescription="value in milliseconds of maximum delay"
@@ -172,7 +172,7 @@ description is not currently required but encouraged.
             description="The read version will be committed, and usually will be the latest committed, but might not be the latest committed in the event of a simultaneous fault and misbehaving clock."
             defaultFor="20"/>
     <Option name="transaction_include_port_in_address" code="505"
-            description="Addresses returned by get_addresses_for_key include the port when enabled. This will be enabled by default in api version 700, and this option will be deprecated."
+            description="Addresses returned by get_addresses_for_key include the port when enabled. This will be enabled by default in api version 630, and this option will be deprecated."
             defaultFor="23"/>
   </Scope>
 
@@ -183,7 +183,7 @@ description is not currently required but encouraged.
             description="The read version will be committed, and usually will be the latest committed, but might not be the latest committed in the event of a simultaneous fault and misbehaving clock."/>
     <Option name="causal_read_disable" code="21" />
     <Option name="include_port_in_address" code="23"
-            description="Addresses returned by get_addresses_for_key include the port when enabled. This will be enabled by default in api version 700, and this option will be deprecated." />
+            description="Addresses returned by get_addresses_for_key include the port when enabled. This will be enabled by default in api version 630, and this option will be deprecated." />
     <Option name="next_write_no_write_conflict_range" code="30"
             description="The next write performed on this transaction will not generate a write conflict range. As a result, other transactions which read the key(s) being modified by the next write will not conflict with this transaction. Care needs to be taken when using this option on a transaction that is shared between multiple threads. When setting this option, write conflict ranges will be disabled on the next write operation, regardless of what thread it is on." />
     <Option name="commit_on_first_proxy" code="40"
@@ -217,7 +217,7 @@ description is not currently required but encouraged.
     <Option name="debug_transaction_identifier" code="403" paramType="String" paramDescription="String identifier to be used when tracing or profiling this transaction. The identifier must not exceed 100 characters."
             description="Sets a client provided identifier for the transaction that will be used in scenarios like tracing or profiling. Client trace logging or transaction profiling must be separately enabled." />
     <Option name="log_transaction" code="404"
-            description="Enables tracing for this transaction and logs results to the client trace logs. The DEBUG_TRANSACTION_IDENTIFIER option must be set before using this option, and client trace logging must be enabled and to get log output." />
+            description="Enables tracing for this transaction and logs results to the client trace logs. The DEBUG_TRANSACTION_IDENTIFIER option must be set before using this option, and client trace logging must be enabled to get log output." />
     <Option name="transaction_logging_max_field_length" code="405" paramType="Int" paramDescription="Maximum length of escaped key and value fields."
             description="Sets the maximum escaped length of key and value fields to be logged to the trace file via the LOG_TRANSACTION option, after which the field will be truncated. A negative value disables truncation." />
     <Option name="timeout" code="500"
@@ -240,7 +240,7 @@ description is not currently required but encouraged.
     <Option name="snapshot_ryw_disable" code="601"
             description="Snapshot read operations will not see the results of writes done in the same transaction. This was the default behavior prior to API version 300." />
     <Option name="lock_aware" code="700"
-            description="The transaction can read and write to locked databases, and is resposible for checking that it took the lock."/>
+            description="The transaction can read and write to locked databases, and is responsible for checking that it took the lock."/>
     <Option name="used_during_commit_protection_disable" code="701"
             description="By default, operations that are performed on a transaction while it is being committed will not only fail themselves, but they will attempt to fail other in-flight operations (such as the commit) as well. This behavior is intended to help developers discover situations where operations could be unintentionally executed after the transaction has been reset. Setting this option removes that protection, causing only the offending operation to fail."/>
     <Option name="read_lock_aware" code="702"
@@ -258,7 +258,7 @@ description is not currently required but encouraged.
     <Option name="want_all" code="-2"
             description="Client intends to consume the entire range and would like it all transferred as early as possible." />
     <Option name="iterator" code="-1"
-            description="The default. The client doesn't know how much of the range it is likely to used and wants different performance concerns to be balanced. Only a small portion of data is transferred to the client initially (in order to minimize costs if the client doesn't read the entire range), and as the caller iterates over more items in the range larger batches will be transferred in order to minimize latency." />
+            description="The default. The client doesn't know how much of the range it is likely to used and wants different performance concerns to be balanced. Only a small portion of data is transferred to the client initially (in order to minimize costs if the client doesn't read the entire range), and as the caller iterates over more items in the range larger batches will be transferred in order to minimize latency. After enough iterations, the iterator mode will eventually reach the same byte limit as ``WANT_ALL``" />
     <Option name="exact" code="0"
             description="Infrequently used. The client has passed a specific row limit and wants that many rows delivered in a single batch. Because of iterator operation in client drivers make request batches transparent to the user, consider ``WANT_ALL`` StreamingMode instead. A row limit must be specified if this mode is used." />
     <Option name="small" code="1"

foundationdb-gen/include/620/version.txt

@@ -1 +1 @@
-6.2.10
+6.2.20

foundationdb-sys/include/620/fdb_c_options.g.h

@@ -186,7 +186,7 @@ typedef enum {
     // Parameter: (Int) value in milliseconds of timeout
     FDB_DB_OPTION_TRANSACTION_TIMEOUT=500,
 
-    // Set a timeout in milliseconds which, when elapsed, will cause a transaction automatically to be cancelled. This sets the ``retry_limit`` option of each transaction created by this database. See the transaction option description for more information.
+    // Set a maximum number of retries after which additional calls to ``onError`` will throw the most recently seen error code. This sets the ``retry_limit`` option of each transaction created by this database. See the transaction option description for more information.
     // Parameter: (Int) number of times to retry
     FDB_DB_OPTION_TRANSACTION_RETRY_LIMIT=501,
 
@@ -202,7 +202,7 @@ typedef enum {
     // Parameter: Option takes no parameter
     FDB_DB_OPTION_TRANSACTION_CAUSAL_READ_RISKY=504,
 
-    // Addresses returned by get_addresses_for_key include the port when enabled. This will be enabled by default in api version 700, and this option will be deprecated.
+    // Addresses returned by get_addresses_for_key include the port when enabled. This will be enabled by default in api version 630, and this option will be deprecated.
     // Parameter: Option takes no parameter
     FDB_DB_OPTION_TRANSACTION_INCLUDE_PORT_IN_ADDRESS=505
 } FDBDatabaseOption;
@@ -220,7 +220,7 @@ typedef enum {
     // Parameter: Option takes no parameter
     FDB_TR_OPTION_CAUSAL_READ_DISABLE=21,
 
-    // Addresses returned by get_addresses_for_key include the port when enabled. This will be enabled by default in api version 700, and this option will be deprecated.
+    // Addresses returned by get_addresses_for_key include the port when enabled. This will be enabled by default in api version 630, and this option will be deprecated.
     // Parameter: Option takes no parameter
     FDB_TR_OPTION_INCLUDE_PORT_IN_ADDRESS=23,
 
@@ -280,7 +280,7 @@ typedef enum {
     // Parameter: (String) String identifier to be used when tracing or profiling this transaction. The identifier must not exceed 100 characters.
     FDB_TR_OPTION_DEBUG_TRANSACTION_IDENTIFIER=403,
 
-    // Enables tracing for this transaction and logs results to the client trace logs. The DEBUG_TRANSACTION_IDENTIFIER option must be set before using this option, and client trace logging must be enabled and to get log output.
+    // Enables tracing for this transaction and logs results to the client trace logs. The DEBUG_TRANSACTION_IDENTIFIER option must be set before using this option, and client trace logging must be enabled to get log output.
     // Parameter: Option takes no parameter
     FDB_TR_OPTION_LOG_TRANSACTION=404,
 
@@ -312,7 +312,7 @@ typedef enum {
     // Parameter: Option takes no parameter
     FDB_TR_OPTION_SNAPSHOT_RYW_DISABLE=601,
 
-    // The transaction can read and write to locked databases, and is resposible for checking that it took the lock.
+    // The transaction can read and write to locked databases, and is responsible for checking that it took the lock.
     // Parameter: Option takes no parameter
     FDB_TR_OPTION_LOCK_AWARE=700,
 
@@ -333,7 +333,7 @@ typedef enum {
     // Client intends to consume the entire range and would like it all transferred as early as possible.
     FDB_STREAMING_MODE_WANT_ALL=-2,
 
-    // The default. The client doesn't know how much of the range it is likely to used and wants different performance concerns to be balanced. Only a small portion of data is transferred to the client initially (in order to minimize costs if the client doesn't read the entire range), and as the caller iterates over more items in the range larger batches will be transferred in order to minimize latency.
+    // The default. The client doesn't know how much of the range it is likely to used and wants different performance concerns to be balanced. Only a small portion of data is transferred to the client initially (in order to minimize costs if the client doesn't read the entire range), and as the caller iterates over more items in the range larger batches will be transferred in order to minimize latency. After enough iterations, the iterator mode will eventually reach the same byte limit as ``WANT_ALL``
     FDB_STREAMING_MODE_ITERATOR=-1,
 
     // Infrequently used. The client has passed a specific row limit and wants that many rows delivered in a single batch. Because of iterator operation in client drivers make request batches transparent to the user, consider ``WANT_ALL`` StreamingMode instead. A row limit must be specified if this mode is used.

foundationdb-sys/include/620/version.txt

@@ -1 +1 @@
-6.2.10
+6.2.20