a167bf344e
Update api version to 700
2020-05-28 12:16:03 -07:00
4b65da6db7
Merge remote-tracking branch 'origin/pyfdbgenerators' into pyfdbgenerators
2020-05-11 13:20:27 -07:00
ffc36dcf45
7.0 became 6.3, so change API versions accordingly
2020-05-11 11:53:34 -07:00
7b87cc3f88
Merge remote-tracking branch 'upstream/release-6.3' into pyfdbgenerators
2020-05-11 11:11:10 -07:00
6d570cd865
Change version from 7.0 to 6.3
2020-04-03 21:38:58 -07:00
338c62b176
Moved up the new test cases to comply the convention there.
2020-03-24 09:53:52 -07:00
527686ffe0
Added a test in API tests for the new API(getEstimagedRangeSize).
2020-03-24 09:26:56 -07:00
986905f3dd
Update bindings/python/tests/tester.py
...
Co-Authored-By: A.J. Beamon <ajbeamon@users.noreply.github.com>
2020-02-06 16:57:14 -08:00
72f92626e4
Update API version to 700
2020-01-30 09:26:27 -08:00
4ceae8c83a
Ban generators in 7.0.0
2020-01-23 16:40:14 -08:00
62baf6d121
Merge remote-tracking branch 'upstream/master' into pyfdbgenerators
2020-01-22 18:05:05 -08:00
95c6c9618e
Update documentation and testers for new options
2019-09-05 16:40:12 -07:00
b509a441e7
Merge branch 'master' into feature-skip-confirm
...
# Conflicts:
# bindings/flow/tester/Tester.actor.cpp
# bindings/go/src/_stacktester/stacktester.go
# bindings/java/src/test/com/apple/foundationdb/test/AsyncStackTester.java
# bindings/java/src/test/com/apple/foundationdb/test/StackTester.java
# bindings/python/tests/tester.py
# bindings/ruby/tests/tester.rb
# documentation/sphinx/source/api-c.rst
# documentation/sphinx/source/api-python.rst
# documentation/sphinx/source/api-ruby.rst
# documentation/sphinx/source/data-modeling.rst
# documentation/sphinx/source/developer-guide.rst
# fdbclient/vexillographer/fdb.options
# fdbserver/MasterProxyServer.actor.cpp
2019-07-27 15:08:13 -07:00
cbc913f902
When run through external means (such as the binding tester), the size limits tests should not change db level defaults.
2019-07-19 09:03:11 -07:00
bc5c65e5ab
Merge pull request #1756 from jzhou77/db-option
...
Add transaction getApproximateSize() API
2019-07-19 08:33:24 -07:00
93be69b6a3
Increase the API version to 620.
2019-07-18 10:56:05 -07:00
c4c9e6cee7
fixed compiler errors
2019-07-12 18:28:41 -07:00
02de53160d
only skip confirm epoch live if CAUSAL_READ_RISKY is enabled
...
time checked on the proxy should be less than the time waited by the master to account for clock speed differences
setting REQUIRED_MIN_RECOVERY_DURATION and ENFORCED_MIN_RECOVERY_DURATION to 0 will go back to the old behavior
2019-07-12 17:58:16 -07:00
562bf6511a
Fix approximate size calculation
2019-07-12 16:53:37 -07:00
d5051b08dd
Make trace event field lengths (and total event sizes) default knobified and configurable. Add a transaction option to control the field length of transaction debug logging. Make the program start command line field less likely to be truncated.
2019-07-12 16:12:35 -07:00
990c205f70
Push a string to stack for getApproximateSize in binding testers
...
Because different bindings may issue different limit for get_range calls, it is
impossible to return the same size value for getApproximateSize API. So we just
push a string to make sure binding test results are the same. Use another unit
test to make sure the sizes got back are monotonically increasing.
2019-07-12 14:15:20 -07:00
9c3591ff43
Fix python3 test failure
...
Both key and value has to be of type bytes.
2019-07-12 10:15:40 -07:00
a8cd25bc46
Fix python3 test failure
...
Both key and value has to be of type bytes.
2019-07-10 21:55:24 -07:00
55d1d62ee3
Fix python tests and use 620 version for C test
2019-07-10 15:19:49 -07:00
20ed0bf802
Add get_approximate_size python unit test
2019-07-10 15:03:24 -07:00
5d1437c8e0
Push int directly to stack for getApproximateSize
2019-07-10 15:00:50 -07:00
0802df2c8f
Convert size from int to string before pushing onto stack
...
Using int is troublesome because the size of int can be different from the
desired 64 bits. So, using a string representation seems to be more consistent.
2019-07-10 14:58:35 -07:00
9d12843a26
Push size as tuple to stack
2019-07-10 14:58:35 -07:00
0ad2d2d16e
Add binding test for getApproximateSize API
2019-07-10 14:58:07 -07:00
c91e712576
Add Python txn get_approximate_size API and test
2019-07-10 14:57:39 -07:00
c6df30deb3
Move size_limit.py to size_limit_tests.py
2019-06-28 13:24:56 -07:00
2035b36257
Make default and persistent options specifyable via annotations to fdb.options. Fix some issues with persisting these options in the multi-version client. Make size limit option not persistent.
2019-06-28 13:24:32 -07:00
16765c6b67
Fix a comment
2019-06-20 20:52:29 -07:00
77d5932465
Add a transaction size limit test
2019-06-20 14:14:09 -07:00
9c2257a0e5
Add transaction size option
2019-06-19 07:45:23 -07:00
4098eb721e
Upon reflection, I think this test was doing nothing.
2019-06-19 02:35:07 -07:00
e8f994965d
python: Post-API Version 620, @fdb.transactional on a generator will throw.
...
Previously, writing code like
@fdb.transactional
def foo(tr):
yield tr.get('a')
yield tr.get('b')
print(foo(db))
was accepted by the python bindings, but had surprising semantics. The
function returned by @fdb.transactional opens a transaction, runs foo(),
commits the transaction, and then returns the generator returned by foo().
This generator then uses the committed transaction. This worked before API
version 410 (FDB 4.1), and hasn't worked since. This will also be a problem if
a closure is returned from foo() that contains `tr`, but it's much harder to
check that in Python.
Rather than allow users to hit an unexpected and mysterious "Operation issued
while a commit was outstanding" exception, it's nicer to explicitly highlight
this problem as soon as we can. Unfortunately, we have no way to know that a
function will return a generator until we call it, so that's the soonest we can
give a more informative error.
2019-06-19 01:38:35 -07:00
63f23c0818
add tests for new database behavior to python scripted tests
...
This also fixes the behavior for the tests of the options which are no longer reset when on_error is called.
2019-03-22 15:10:08 -04:00
e6e2ea2af6
Merge remote-tracking branch 'upstream/master' into 00775-database-level-tr-options
2019-03-22 14:41:27 -04:00
5e8e2ef2a6
rename the function where it is defined as well as where it is called
2019-03-22 13:26:41 -04:00
9e15872418
remove test that is now extraneous
2019-03-22 13:20:00 -04:00
001fde718c
fix comments to mark things that throw as throwing rather than not throwing
...
Co-Authored-By: alecgrieser <alloc@apple.com>
2019-03-22 13:04:11 -04:00
4ac3e790ad
modify the reset and timeout option unit tests to handle new on_error cancellation behavior
2019-03-22 12:45:59 -04:00
4fff1f6756
add database options to bindingtester stack tester
2019-03-20 11:13:38 -06:00
083a73b0d2
In our binding testers, stop using the TRANSACTION_LOGGING_ENABLE option and switch to the DEBUG_TRANSACTION_IDENTIFIER and LOG_TRANSACTION options
2019-03-11 13:35:43 -07:00
8669aea22b
Python: creating a SingleFloat with an integer didn't work. Updated the tester to exercise this path.
2019-03-01 09:25:53 -08:00
5db549c203
Changes to print output
2018-05-18 16:24:03 -07:00
47c9e4f923
update bindings and bindingtester that uses versionstamps to use new protocol
...
issue #148
2018-05-08 08:57:09 -07:00
6ee14bbb93
expose second versionstamp value type through vexillographer and add support in bindings and bindingtester
2018-05-08 08:57:09 -07:00
a1faaafca3
Merge remote-tracking branch 'upstream/release-5.1' into merge-release-5.1
2018-04-27 16:38:18 -07:00
Balachandar Namasivayam