We should add the capability to only archive events that match metadata/dimension queries. Add these two as parameters, and pass them through to the call to get events to archive.
Currently we can contact s3 by prefixing s3- to the front of any namespace. Ideally we would have something a little more obvious like s3://, but our servlet was inhibiting that ability. Since S3 datacenter specific we don't actually need to support the servlet, so axing prod support could be a simple approach
The unit tests for Cantor implementation on top of MySQL requires an instance of MySQL to run. Change the bang.sh script to start/stop one in a docker container.
Since we can't control the type of load balancer and client-side load balancing is a much larger task that wouldn't even apply to most current use-cases of the Cantor gRPC client this issue aims to add logic to the client that periodically refreshes the gRPC channel to ensure actual load balancing.
Nodes start as a stand alone JVM, connect to the master and report the namespaces they support. Requests to the master are routed to nodes based on the namespace lookup table maintained in the master.
Write wrappers similar to the loggable wrappers, that record metrics for each method in cantor. Should record metrics such as frequency, duration, and potentially some characteristics of the response.