The user can mount his own data directory to BigObject docker's /data with -v flag on the docker run command. The benefits of mounting user's data directory include transparency, where the user can easily find all the data he created (tables, associations, trees) in his own data directory and ease of upgrade / backup, where the user is able to keep his old data when he upgrades BigObject by remounting his data directory into new BigObject docker again.

  • volume /data

For example, if the user's data directory is /home/user/data, then he can mount that user data directory to BigObject Docker as /data with following command when he starts BigObject from docker.

docker run -t -d --name bigobject -p 9090:9090 -p 9091:9091 -p 3306:3306 -v /home/user/data:/data  bigobject/bigobject
  • volume /bofile

The data volume for input files (i.e. csv files) in BigObject docker is /bofile. The user can add a input data volume into BigObject using -v flag with the docker run command. Once the directory is mounted, the user is able to upload input data then append to the table he created with LOAD command, introduced later in this document.

For example, if the user places his csv files in the directory of /home/user/csvfiles, then he can mount that user directory to BigObject Docker as /bofile with following command when he starts BigObject from docker.

docker run -t -d --name bigobject -p 9090:9090 -p 9091:9091 -p 3306:3306 -v /home/user/data:/data -v /home/user/csvfiles:/bofile bigobject/bigobject

Once /home/user/csvfiles is mounted to /bofile in BigObject docker container, the user can apply LOAD command to import those csv files within it.