fdb 7.2.7 → 7.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b73e0d516cf6b3c6b3878b03bc338c27a2373dfca685cea516c9764461fd3c8d
-  data.tar.gz: 6e6e8bc8155c6036c767b850b8e4dcb4d02fbd07b28f8e62e1af4122ead6046c
+  metadata.gz: f49696ed3283b9e76f9caa6b7d064baa7db55edc4353a8c766a31da6a2429a9d
+  data.tar.gz: 0b27383d0b6f20cc586d239ea2306507ff79fd938ac7bafec53aceb0b0c289ce
 SHA512:
-  metadata.gz: c3f8e3b761907374d19c748adf939943614229778d26e58b772a69115ef82d487a947f149f2f3a0791ab5318f332844e057a014b2d550dc1bada2308cd91f912
-  data.tar.gz: a3bd8d0a09025f5f59a452c7dc72e1975708bf10b852e9acd32dcfe4fcca8af6b06e1b51fe3cb3bb09c417b72f4ab28cec6971e3d90128629dc75f89fd4fda25
+  metadata.gz: fc2bd90b4531d65264172ee44fbcab0c0667c1830ce49e0b236cbf1450124eb0490b2cb2b89b7822f7cb5481562a33323090d446d8aae78482f7869bafdaded2
+  data.tar.gz: a894f8701fda023d7ba39a7e48ec6ce0f8eb760735412cc0c532cd4354d0c2395a893dc50e12f7e871078999f44492420632a6fab9c652051ea1f64519e1248c

data/lib/fdb.rb

@@ -36,7 +36,7 @@ module FDB
     end
   end
   def self.api_version(version)
-    header_version = 720
+    header_version = 730
     if self.is_api_version_selected?()
       if @@chosen_version != version
         raise "FDB API already loaded at version #{@@chosen_version}."

data/lib/fdboptions.rb

@@ -34,6 +34,7 @@ module FDB
     "TRACE_CLOCK_SOURCE" => [35, "Select clock source for trace files. now (the default) or realtime are supported.", '', "Trace clock source"],
     "TRACE_FILE_IDENTIFIER" => [36, "Once provided, this string will be used to replace the port/PID in the log file names.", '', "The identifier that will be part of all trace file names"],
     "TRACE_SHARE_AMONG_CLIENT_THREADS" => [37, "Use the same base trace file name for all client threads as it did before version 7.2. The current default behavior is to use distinct trace file names for client threads by including their version and thread index.", nil, nil],
+    "TRACE_INITIALIZE_ON_SETUP" => [38, "Initialize trace files on network setup, determine the local IP later. Otherwise tracing is initialized when opening the first database.", nil, nil],
     "TRACE_PARTIAL_FILE_SUFFIX" => [39, "Set file suffix for partially written log files.", '', "Append this suffix to partially written log files. When a log file is complete, it is renamed to remove the suffix. No separator is added between the file and the suffix. If you want to add a file extension, you should include the separator - e.g. '.tmp' instead of 'tmp' to add the 'tmp' extension."],
     "KNOB" => [40, "Set internal tuning or debugging knobs", '', "knob_name=knob_value"],
     "TLS_PLUGIN" => [41, "Deprecated", '', "file path or linker-resolved name"],
@@ -56,6 +57,9 @@ module FDB
     "DISABLE_LOCAL_CLIENT" => [64, "Prevents connections through the local client, allowing only connections through externally loaded client libraries.", nil, nil],
     "CLIENT_THREADS_PER_VERSION" => [65, "Spawns multiple worker threads for each version of the client that is loaded.  Setting this to a number greater than one implies disable_local_client.", 0, "Number of client threads to be spawned.  Each cluster will be serviced by a single client thread."],
     "FUTURE_VERSION_CLIENT_LIBRARY" => [66, "Adds an external client library to be used with a future version protocol. This option can be used testing purposes only!", '', "path to client library"],
+    "RETAIN_CLIENT_LIBRARY_COPIES" => [67, "Retain temporary external client library copies that are created for enabling multi-threading.", nil, nil],
+    "IGNORE_EXTERNAL_CLIENT_FAILURES" => [68, "Ignore the failure to initialize some of the external clients", nil, nil],
+    "FAIL_INCOMPATIBLE_CLIENT" => [69, "Fail with an error if there is no client matching the server version the client is connecting to", nil, nil],
     "DISABLE_CLIENT_STATISTICS_LOGGING" => [70, "Disables logging of client statistics, such as sampled transaction activity.", nil, nil],
     "ENABLE_SLOW_TASK_PROFILING" => [71, "Deprecated", nil, nil],
     "ENABLE_RUN_LOOP_PROFILING" => [71, "Enables debugging feature to perform run loop profiling. Requires trace logging to be enabled. WARNING: this feature is not recommended for use in production.", nil, nil],
@@ -82,9 +86,12 @@ module FDB
     "TRANSACTION_SIZE_LIMIT" => [503, "Set the maximum transaction size in bytes. This sets the ``size_limit`` option on each transaction created by this database. See the transaction option description for more information.", 0, "value in bytes"],
     "TRANSACTION_CAUSAL_READ_RISKY" => [504, "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.", nil, nil],
     "TRANSACTION_INCLUDE_PORT_IN_ADDRESS" => [505, "Deprecated. Addresses returned by get_addresses_for_key include the port when enabled. As of api version 630, this option is enabled by default and setting this has no effect.", nil, nil],
+    "TRANSACTION_AUTOMATIC_IDEMPOTENCY" => [506, "Set a random idempotency id for all transactions. See the transaction option description for more information. This feature is in development and not ready for general use.", nil, nil],
     "TRANSACTION_BYPASS_UNREADABLE" => [700, "Allows ``get`` operations to read from sections of keyspace that have become unreadable because of versionstamp operations. This sets the ``bypass_unreadable`` option of each transaction created by this database. See the transaction option description for more information.", nil, nil],
+    "TRANSACTION_USED_DURING_COMMIT_PROTECTION_DISABLE" => [701, "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.", nil, nil],
+    "TRANSACTION_REPORT_CONFLICTING_KEYS" => [702, "Enables conflicting key reporting on all transactions, allowing them to retrieve the keys that are conflicting with other transactions.", nil, nil],
     "USE_CONFIG_DATABASE" => [800, "Use configuration database.", nil, nil],
-    "TEST_CAUSAL_READ_RISKY" => [900, "An integer between 0 and 100 (default is 0) expressing the probability that a client will verify it can't read stale data whenever it detects a recovery.", nil, nil],
+    "TEST_CAUSAL_READ_RISKY" => [900, "Enables verification of causal read risky by checking whether clients are able to read stale data when they detect a recovery, and logging an error if so.", 0, "integer between 0 and 100 expressing the probability a client will verify it can't read stale data"],
   }
 
   @@TransactionOption = {
@@ -95,6 +102,11 @@ module FDB
     "NEXT_WRITE_NO_WRITE_CONFLICT_RANGE" => [30, "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.", nil, nil],
     "READ_YOUR_WRITES_DISABLE" => [51, "Reads performed by a transaction will not see any prior mutations that occured in that transaction, instead seeing the value which was in the database at the transaction's read version. This option may provide a small performance benefit for the client, but also disables a number of client-side optimizations which are beneficial for transactions which tend to read and write the same keys within a single transaction. It is an error to set this option after performing any reads or writes on the transaction.", nil, nil],
     "READ_AHEAD_DISABLE" => [52, "Deprecated", nil, nil],
+    "READ_SERVER_SIDE_CACHE_ENABLE" => [507, "Storage server should cache disk blocks needed for subsequent read requests in this transaction.  This is the default behavior.", nil, nil],
+    "READ_SERVER_SIDE_CACHE_DISABLE" => [508, "Storage server should not cache disk blocks needed for subsequent read requests in this transaction.  This can be used to avoid cache pollution for reads not expected to be repeated.", nil, nil],
+    "READ_PRIORITY_NORMAL" => [509, "Use normal read priority for subsequent read requests in this transaction.  This is the default read priority.", nil, nil],
+    "READ_PRIORITY_LOW" => [510, "Use low read priority for subsequent read requests in this transaction.", nil, nil],
+    "READ_PRIORITY_HIGH" => [511, "Use high read priority for subsequent read requests in this transaction.", nil, nil],
     "DURABILITY_DATACENTER" => [110, "", nil, nil],
     "DURABILITY_RISKY" => [120, "", nil, nil],
     "DURABILITY_DEV_NULL_IS_WEB_SCALE" => [130, "Deprecated", nil, nil],
@@ -104,6 +116,7 @@ module FDB
     "ACCESS_SYSTEM_KEYS" => [301, "Allows this transaction to read and modify system keys (those that start with the byte 0xFF). Implies raw_access.", nil, nil],
     "READ_SYSTEM_KEYS" => [302, "Allows this transaction to read system keys (those that start with the byte 0xFF). Implies raw_access.", nil, nil],
     "RAW_ACCESS" => [303, "Allows this transaction to access the raw key-space when tenant mode is on.", nil, nil],
+    "BYPASS_STORAGE_QUOTA" => [304, "Allows this transaction to bypass storage quota enforcement. Should only be used for transactions that directly or indirectly decrease the size of the tenant group's data.", nil, nil],
     "DEBUG_RETRY_LOGGING" => [401, "", '', "Optional transaction name"],
     "TRANSACTION_LOGGING_ENABLE" => [402, "Deprecated", '', "String identifier to be used in the logs when tracing this transaction. The identifier must not exceed 100 characters."],
     "DEBUG_TRANSACTION_IDENTIFIER" => [403, "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.", '', "String identifier to be used when tracing or profiling this transaction. The identifier must not exceed 100 characters."],
@@ -114,6 +127,7 @@ module FDB
     "RETRY_LIMIT" => [501, "Set a maximum number of retries after which additional calls to ``onError`` will throw the most recently seen error code. Valid parameter values are ``[-1, INT_MAX]``. If set to -1, will disable the retry limit. Prior to API version 610, like all other transaction options, the retry limit must be reset after a call to ``onError``. If the API version is 610 or greater, the retry limit is not reset after an ``onError`` call. Note that at all API versions, it is safe and legal to set the retry limit each time the transaction begins, so most code written assuming the older behavior can be upgraded to the newer behavior without requiring any modification, and the caller is not required to implement special logic in retry loops to only conditionally set this option.", 0, "number of times to retry"],
     "MAX_RETRY_DELAY" => [502, "Set the maximum amount of backoff delay incurred in the call to ``onError`` if the error is retryable. Defaults to 1000 ms. Valid parameter values are ``[0, INT_MAX]``. If the maximum retry delay is less than the current retry delay of the transaction, then the current retry delay will be clamped to the maximum retry delay. Prior to API version 610, like all other transaction options, the maximum retry delay must be reset after a call to ``onError``. If the API version is 610 or greater, the retry limit is not reset after an ``onError`` call. Note that at all API versions, it is safe and legal to set the maximum retry delay each time the transaction begins, so most code written assuming the older behavior can be upgraded to the newer behavior without requiring any modification, and the caller is not required to implement special logic in retry loops to only conditionally set this option.", 0, "value in milliseconds of maximum delay"],
     "SIZE_LIMIT" => [503, "Set the transaction size limit in bytes. The size is calculated by combining the sizes of all keys and values written or mutated, all key ranges cleared, and all read and write conflict ranges. (In other words, it includes the total size of all data included in the request to the cluster to commit the transaction.) Large transactions can cause performance problems on FoundationDB clusters, so setting this limit to a smaller value than the default can help prevent the client from accidentally degrading the cluster's performance. This value must be at least 32 and cannot be set to higher than 10,000,000, the default transaction size limit.", 0, "value in bytes"],
+    "AUTOMATIC_IDEMPOTENCY" => [505, "Automatically assign a random 16 byte idempotency id for this transaction. Prevents commits from failing with ``commit_unknown_result``. WARNING: If you are also using the multiversion client or transaction timeouts, if either cluster_version_changed or transaction_timed_out was thrown during a commit, then that commit may have already succeeded or may succeed in the future. This feature is in development and not ready for general use.", nil, nil],
     "SNAPSHOT_RYW_ENABLE" => [600, "Snapshot read operations will see the results of writes done in the same transaction. This is the default behavior.", nil, nil],
     "SNAPSHOT_RYW_DISABLE" => [601, "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.", nil, nil],
     "LOCK_AWARE" => [700, "The transaction can read and write to locked databases, and is responsible for checking that it took the lock.", nil, nil],

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: fdb
 version: !ruby/object:Gem::Version
-  version: 7.2.7
+  version: 7.3.0
 platform: ruby
 authors:
 - FoundationDB
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-05-05 00:00:00.000000000 Z
+date: 2023-05-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ffi