* adding wait parameter to blobbify api
* formatting
* fixing comment style
* fixing bug and adding debugging
* adding blob ranges unit test
* testing both blobbify cases in cancel
* formatting
* switch to explicit blocking api instead of boolean flag
* remove comments
* format
* Enable secure allocation mode in Arena
This mode allows zeroing out blocks holding sensitive data after use
* Introduce WipedString to all token-holding memory
Also introduce a option flag "sensitive"
* Make pointer equivalency a hard requirement for non-ASAN builds
So that we can detect when Arena/malloc/memory-wipe behavior changes
* client_config_tester: use a generic mechanism to set specific network options
* trace_initialize_on_setup option to initialize client traces on network setup without local IP address
* trace_initialize_on_setup: Addressing review comments
* Restore correct formatting
* trace_initialize_on_setup: Update go bindings
* Include PID for identification into trace file names by default
* Use the same naming pattern for trace files in all configurations
* Empty commit
Adds a prototype of new APIs to access the Blob Granule data:
fdb_future_readbg_get_descriptions
fdb_readbg_parse_snapshot_file
fdb_readbg_parse_delta_file
fdb_result_get_bg_mutations_array
The client first calls fdb_future_readbg_get_descriptions to get a high level description of granules, reads the files and then calls fdb_readbg_parse_snapshot_file and fdb_readbg_parse_delta_file to parse the snapshot and delta files, respectively. This allows the client to get a raw access to the blob granule data, and allows the client to process them in a way they wouldn't be efficiently able to when using previous blob granule read APIs.
We expect these APIs to evolve before a release.
---------
Co-authored-by: Josh Slocum <josh.slocum@snowflake.com>
* MVC: Keep track of database initialization state; some refactoring of database update for better readability
* Do not create unused temp directory in old binaries downloader
* MVC: Fail transactions with an error code on database initialization errors
* Exit client config tester immediately on errors
* Fail database operations for incompatible clients and database initialization errors
* Some tests for database initialization errors
* local_cluster: reopen fdbmonitor.log in append mode, close it before reopening
* Introduce an option ignore_incompatible_client restoring the behavior of indefinite wait when there is no client matching a cluster version
* Multi-Version API: remove atomics from initializationError
* Update GO bindings: adding option ignore_incompatible_client
* MVC to fail on incompatible clients: addressing review comments
* MVC: An option to fail in case of an incompatible client
* fdb_c_client_config_tester: update help text
Rahul Kodali