ctubbsii commented on issue #296: URL: https://github.com/apache/fluo-uno/issues/296#issuecomment-1748025851
My workaround for special cases, when I want to diverge from Uno's default behavior, is to create a new branch in my fork that diverges from the main branch just slightly and makes the changes I want. I have found that to be more useful than adding a ton of options to Uno's config files and modifying its scripts to support those options. In the case you're describing, I would probably just comment out the line in `bin/impl/install/accumulo.sh` that does `accumulo-cluster create-config` and place my own preferred `cluster.yaml` in `conf/accumulo/common/`. If one were to patch Uno to support this natively, rather than add more Uno config for the number of scan servers or external compactor services, I'd just make it do `[[ -f conf/cluster.yaml ]] || accumulo-cluster create-config`. That way, it doesn't try to generate a new config if you already have one copied in from `conf/accumulo/common/`, and then you just supply your own there. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
