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
bc5c65e5ab
Merge pull request #1756 from jzhou77/db-option
...
Add transaction getApproximateSize() API
2019-07-19 08:33:24 -07:00
a26980682d
Merge pull request #1835 from TWarszawski/master
...
Add more information to the java binding jar's MANIFEST.
2019-07-18 14:01:46 -07:00
93be69b6a3
Increase the API version to 620.
2019-07-18 10:56:05 -07:00
24c7960c12
Removing uneccessary attributes from MANIFEST
2019-07-16 12:46:40 -07:00
b0a6e2d2c4
Update bindings/java/CMakeLists.txt
...
Fix Specification-Title
Co-Authored-By: Alec Grieser <alloc@apple.com>
2019-07-16 11:22:10 -07:00
7390df35a1
updated binding testers to set causalReadRisky
2019-07-15 11:39:03 -07:00
af35061200
Addressing reviewer comments.
2019-07-15 08:51:22 -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
2dcc3cfd0a
Deprecate fdb_future_get_version for version 620
...
Use fdb_future_get_int64 in all bindings.
2019-07-11 21:17:31 -07:00
b2a89c8b77
Address review comments for PR #1756
...
Use fdb_future_get_int64 for language bindings and get rid of using Version
with getApproximateSize API.
2019-07-11 16:41:29 -07:00
ada31e7dcc
Add more information to MANIFEST in jar.
2019-07-11 13:20:15 -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
4a15be3643
Code format for fdbJNI.cpp
2019-07-10 14:51:52 -07:00
c50a675bf0
Add transaction getApproximateSize() API
...
The size is the summation of expected size of mutations, read conflict ranges,
and write conflict ranges.
2019-07-10 14:51:52 -07:00
7bfda1faaa
Fixed three more Windows issues
...
This is now compiling on my Windows machine
2019-06-27 11:39:36 -07:00
ab7562160c
Made JavaWorkload an external workload
2019-06-19 13:03:41 -07:00
296adada93
Use c++11 thread_local instead of redefining it to platform specific variants.
2019-05-23 18:35:45 -07:00
3acaa7343e
Enabled C++17 for all Windows projects
...
Set Visual Studio version to 2017 (first version to support C++17)
2019-05-16 17:44:13 -07:00
94aed513c7
Switched Windows tools within projects to 2017
2019-05-16 15:05:11 -07:00
648fc8ec7c
Merge pull request #1472 from mpilman/fixes/no-libfdbc-in-jar
...
Remove fdb_c from fat-jar
2019-05-01 14:23:56 -07:00
9fea60675f
Fix comments to use transaction_too_old instead of past_version
2019-04-24 18:50:57 -07:00
abb68cba92
Remove fdb_c from fat-jar
...
Fixes #1460
2019-04-18 13:26:27 -07:00
160949d071
Remove unnecessary function
2019-04-02 16:28:34 -07:00
d38efac7f8
minor code cleanup
2019-04-02 16:23:36 -07:00
371a41dbba
Allow classPath to be modified at runtime
2019-04-02 11:56:40 -07:00
6facfa931b
fixed weird encoding issue
2019-04-02 10:32:09 -07:00
e23e63c6ac
Implemented JavaWorkload
...
This change allows a user to write a workload in Java.
The way this is implemented is by creating a JVM within the
simulator and calling the corresponding workload class. A
workload can then run in the simulator or on a testing cluster.
If the workload is executed within the simulator, the resulting
test will not be deterministic anymore as it will execute in a
different thread (and even without that it is not clear, whether
we could get determinism as the JVM does a lot of stuff that are
not deterministic).
This is intendet to get better testing of the Java client and
layer authors can use the simulator to test their layers on a single
machine but they can still simulate failing machines etc.
2019-03-31 17:57:43 -07:00
e6e2ea2af6
Merge remote-tracking branch 'upstream/master' into 00775-database-level-tr-options
2019-03-22 14:41:27 -04:00
4fff1f6756
add database options to bindingtester stack tester
2019-03-20 11:13:38 -06:00
253597466c
revert temporary testing changes
2019-03-18 13:00:59 -07:00
ff4386f4e4
TuplePerformanceTester no longer generates malformed UTF-16
2019-03-18 09:43:31 -07:00
715c2c980d
Fixes #1186 : Tuples: Malformed UTF-16 treated differently in Java and Python
...
Technically, they are still treated differently in Java and Python, but now, Java throws an exception if it encounters malformed UTF-16 to avoid serializing things in ways that it cannot deserialize. It also now throws an error when reading malformed UTF-8, which I think is safer as it stops it from accidentally doing something like reading bytes and then writing it back but accidentally writing to the wrong spot, but that might be a mistake.
2019-03-18 09:19:54 -07:00
636d2ca631
Merge pull request #1207 from alecgrieser/tuple-performance-cache-packed
...
Java: Tuple serialization/deserialization uses fewer allocations
2019-03-13 15:53:52 -07:00
d9e9e0c521
use bitwise or instead of addition when reconsituting long
2019-03-11 18:26:08 -07:00
36c12cd749
Add missing definitions.
2019-03-11 17:49:03 -07:00
7340298202
remove debugging printing that was accidentally added
2019-03-11 16:57:36 -07:00
f66ddb13c2
rewrite replace without a buffer to use replace with a buffer to first get length
2019-03-11 16:57:36 -07:00
75e475563a
clarify comments and be more strict about using UUID_BYTES constant
2019-03-11 16:57:36 -07:00
40aa2ba6f0
CMakeLists alphabetization and Javadoc improvements
2019-03-11 16:57:36 -07:00
39fd30330f
memoize incomplete versionstamp information in Tuples ; add more tests
2019-03-11 16:55:01 -07:00
663d750e1d
pack Tuples with a single byte array allocation of the right size
2019-03-11 16:55:01 -07:00
a74dfa5487
compare strings by unicode codepoint without copying
2019-03-11 16:55:01 -07:00
e9771364d7
various Java tuple performance tweaks
...
These include:
* Memoizing packed representations within Tuples
* Using longs instead of BigIntegers if possible
* As much as possible sticking to manipulating primitive types when using floats/doubles
2019-03-11 16:55:00 -07:00
e6ce0ebd27
improve tuple performance tester for more types and add serialization check in TupleTest
2019-03-11 16:55:00 -07:00
78ff3d92c1
memoize the packed Tuple representation
2019-03-11 16:55:00 -07:00
Evan Tschannen