Wait until all containers are ready. By default, docker exposes the tcp port at 9000 and http port at 8123. We can use following commands to check the readiness of byconity components:
# return 1 indicates that server is working properly
curl '127.0.0.1:8123/?query=select%20count()%20from%20system.one'
# return 1 indicates that read worker is working properly and server can connect to it
curl '127.0.0.1:8123/?query=select%20count()%20from%20cnch(`vw_default`,system,one)'
# return 1 indicates that write worker is working properly and server can connect to it
curl '127.0.0.1:8123/?query=select%20count()%20from%20cnch(`vw_write`,system,one)'
Trying some basic queries
Internally, byconity read/write to hdfs with username clickhouse (and data is stored in /user/clickhouse/), which is not created by default when starting hadoop cluster. We can use following commands to create the user clickhouse on hdfs.
This repo provides a quick way to play with ByConity with docker compose.
Noted, since FoundationDB cannot work propertly in Docker on Apple Silicon machines, this repo is not working on mac m1/m2.
The structure of this repo is shown below.
Bring the cluster up
From the current directory, run:
Wait until all containers are ready. By default, docker exposes the tcp port at 9000 and http port at 8123. We can use following commands to check the readiness of byconity components:
Trying some basic queries
Internally, byconity read/write to hdfs with username
clickhouse(and data is stored in/user/clickhouse/), which is not created by default when starting hadoop cluster. We can use following commands to create the userclickhouseon hdfs.Connect to byconity with command