Greg, Yes, use the new property going forward. The old property will still work but at some point will be phased out. When that happens it will be documented in the release notes.
You currently can't remove a bucket property. In the case where rs_extractfun is still set in a future version it shouldn't matter because it will just be ignored by the code. However, I could maybe see this being an issue if you wanted to change a property to no longer have any effect (e.g. unset a custom extractor). Currently, as it stands, you could do this by setting the property to `undefined` but that can only be achieved via the Erlang client. We should probably have a way to set a sentinel value via HTTP as well. -Ryan On Fri, Sep 30, 2011 at 7:51 PM, Greg Pascale <[email protected]> wrote: > Hi, > > Somewhere along the line, it looks like the mechanism for setting a custom > extractor changed slightly. The documentation now says to set a property > called search_extractor with the fields mod, fun and arg. > > It used to be a property called rs_extractfun with the fields language, > function and module. > > The old rs_extractfun syntax still seems to work with 1.0, but I'm > wondering if I should switch over the new style to stay compatible with > future releases. This also brings up an interesting question - how do I > unset a bucket property? > > -- > Greg > Clipboard > > > _______________________________________________ > 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
