fdb 6.2.19 → 6.2.20

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/lib/fdboptions.rb +2 -2
  3. metadata +2 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 9f7abcbc951e1ba592f062ef779c19b0b6f963d5
4
- data.tar.gz: 4fd6c488241fa22e65b8a7fca9b911e21a6392ee
3
+ metadata.gz: 67bdfe8822e9e2cd8c2f12b4cebdba4689197fbd
4
+ data.tar.gz: 3b19eee06c5e31108d4814b563e83639300a1505
5
5
  SHA512:
6
- metadata.gz: 3b98ec556293a31de2ff325f754b90af841ebb2d3f5c9f2f4e6209313f4712337db06567b4bf5bd17b0a406b4419f66515f4f87e2d9c59416ffd39c11c27cee7
7
- data.tar.gz: e8f9f8add6a5029f93736ccd6f0d0079aa1fb8c01f2a1cfed9805e094f13aebbda45e5cf60b52e2fd520ab8dc4a348c9b43255984ea3e372c1b6bfe88eb6f218
6
+ metadata.gz: 2d2b99b3caa4676ab0190fa4cff4c3cc99ee594af2b647b83c31b1c480d14679a6490919fb4b74d40490a628de4f6557e995d202c6d3e7e334b73505d3b7b2cf
7
+ data.tar.gz: b6a6c264c75c33ef4a301f3d1b4495cf935204c55daab826a7f03e81898216c3471193b85789d522bd4b22f8fdfbb7865d8a185a4792059381db477047887550
data/lib/fdboptions.rb CHANGED
@@ -71,14 +71,14 @@ module FDB
71
71
  "TRANSACTION_MAX_RETRY_DELAY" => [502, "Set the maximum amount of backoff delay incurred in the call to ``onError`` if the error is retryable. This sets the ``max_retry_delay`` option of each transaction created by this database. See the transaction option description for more information.", 0, "value in milliseconds of maximum delay"],
72
72
  "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"],
73
73
  "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],
74
- "TRANSACTION_INCLUDE_PORT_IN_ADDRESS" => [505, "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.", nil, nil],
74
+ "TRANSACTION_INCLUDE_PORT_IN_ADDRESS" => [505, "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.", nil, nil],
75
75
  }
76
76
 
77
77
  @@TransactionOption = {
78
78
  "CAUSAL_WRITE_RISKY" => [10, "The transaction, if not self-conflicting, may be committed a second time after commit succeeds, in the event of a fault", nil, nil],
79
79
  "CAUSAL_READ_RISKY" => [20, "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],
80
80
  "CAUSAL_READ_DISABLE" => [21, "", nil, nil],
81
- "INCLUDE_PORT_IN_ADDRESS" => [23, "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.", nil, nil],
81
+ "INCLUDE_PORT_IN_ADDRESS" => [23, "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.", nil, nil],
82
82
  "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],
83
83
  "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.", nil, nil],
84
84
  "READ_AHEAD_DISABLE" => [52, "Deprecated", nil, nil],
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: fdb
3
3
  version: !ruby/object:Gem::Version
4
- version: 6.2.19
4
+ version: 6.2.20
5
5
  platform: ruby
6
6
  authors:
7
7
  - FoundationDB
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2020-03-17 00:00:00.000000000 Z
11
+ date: 2020-04-23 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: ffi