071df2f439
* Split queries into system and data queries * System queries are sequentially executed and generate separate transaction deltas * System transaction try locks for 100ms * last_commited_system_ts saved to DBMS durability * Replicating CREATE/DROP DATABASE * Sending a system snapshot if REPLICA behind * Passing a copy of the gatekeeper::access as std::any to all functions that could call an async execution * Removed delete_on_drop flag (we now always delete on drop) * Using UUID as the directory name for databases * DBMS durability update (added versioning and salient information) * Automatic migration from previous version * Interpreter can run some queries without a target database * SHOW REPLICA returns the status of the currently active DB * Returning UUID instead of db name in the RPC responses * Using UUIDs for database specification in RPC (not name) * FrequentCheck forces update on reconnect * TimestampRpc will detect if a replica is behind, and will update client's state * Safer SLK reads * Split SHOW DATABASES in two SHOW DATABASES (list of current databases) and SHOW DATABASE a single string naming the current database --------- Co-authored-by: Gareth Lloyd <gareth.lloyd@memgraph.io> |
||
---|---|---|
.. | ||
kafka | ||
pulsar | ||
transformations | ||
CMakeLists.txt | ||
common.py | ||
conftest.py | ||
kafka_streams_tests.py | ||
pulsar_streams_tests.py | ||
README.md | ||
redpanda.yml | ||
streams_owner_tests.py | ||
workloads.yaml |
There are three docker-compose files in this directory:
To run one of them, use the docker-compose -f <filename> up -V
command. Optionally you can append -d
to detach from the started containers. You can stop the detach containers by docker-compose -f <filename> down
.
If you experience strange errors, try to clean up the previously created containers by docker-compose -f <filename> rm -svf
.