Search bug / feature


#1

I am experiencing a strange behaviour in the search feature of chef
server: I have a role called zookeeper and an attribute in a cookbook
like this
default[‘app’][‘zookeeper’][‘role’] = “zookeeper”. One server is using
zookeeper role and another one is using the cookbook that contains
that attribute.

When I search the node data bag with “role:zookeeper” query the result
contains both servers. I would like to know if this is a bug or a
feature. I am using chef 11.

Thanks,
Robert


#2

On Thursday, February 28, 2013 at 9:02 AM, Robert Dolca wrote:

I am experiencing a strange behaviour in the search feature of chef
server: I have a role called zookeeper and an attribute in a cookbook
like this
default[‘app’][‘zookeeper’][‘role’] = “zookeeper”. One server is using
zookeeper role and another one is using the cookbook that contains
that attribute.

When I search the node data bag with “role:zookeeper” query the result
contains both servers. I would like to know if this is a bug or a
feature. I am using chef 11.

Thanks,
Robert

Feature. Munging the data in this way is one of chef-expander’s two tasks (the other is to provider a buffer so Solr commits don’t block API requests).

See here: http://docs.opscode.com/essentials_search_keys.html


Daniel DeLeo