This works for the default BigDataScript install location of ~/.bds/, but will also work if the bds binary is installed somewhere else an is on PATH. It relies on the convention that bds.config will always be in the same directory as the bds binary, but I see this as a good stop-gap until this wrapper script is able to accept an explicit path to the bds.config on the commandline.
This works for the default BigDataScript install location of ~/.bds/, but will also work if the bds binary is installed somewhere else an is on PATH. It relies on the convention that bds.config will always be in the same directory as the bds binary, but I see this as a good stop-gap until this wrapper script is able to accept an explicit path to the bds.config on the commandline.