Andy, Not crazy at all. Another issue with adding the hook for each foo* bucket is that you increase the size of the ring which must be gossiped between nodes. We recently added something called "bucket fixups" to 1.0 that sorta do what you want but only for buckets with custom properties. ATM, there is no way to do this for all buckets across the board.
If you're just talking about a precommit hook you could put the logic in the hook itself and match against the bucket name there. Care to elaborate more on your use case? Maybe there is another way. -Ryan On Fri, Sep 23, 2011 at 5:22 PM, Andy Skelton <[email protected]> wrote: > I would like to use bucket names to determine default bucket props > such as hooks. For example, if all buckets matching foo* should have a > certain post-commit hook, I don't want to have to set those bucket > props before I can put keys in the buckets. > > My preferred solution would be a config option that takes a mod/fun > instead of a proplist. > > In riak_core_bucket, instead of always treating > app_helper:get_env(riak_core, default_bucket_props) as a list it would > also look for a tuple {M, F} and in that case call M:F(Name) which > would return a list. > > Sound crazy? :) > > Andy Skelton > Automattic > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
