# Server Weighting and Field Collapsing **URL:** \ **Category:** Elasticsearch\ **Created:** [July 13, 2010, 7:14am UTC](https://discuss.elastic.co/t/server-weighting-and-field-collapsing/3093 "2010-07-13T07:14:01Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![ppearcy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppearcy/32/980_2.png) [@ppearcy](https://discuss.elastic.co/u/ppearcy)\ **Post date:** [July 13, 2010, 7:14am UTC](https://discuss.elastic.co/t/server-weighting-and-field-collapsing/3093/1 "2010-07-13T07:14:01Z")
Hello, I've been very impressed with what I've seen so far with ES and was curious if a couple of features were available or planned. 1. Ability to weight servers in the cluster to receive different loads. Our newer h/w always seems to be 2x faster than older h/w and we'd like it to receive that load when placed into the cluster. 2. Ability to collapse on a field. For example, I want the most relevant result from all different report types. Or similarly, the most recent result of each report type. So, the sort order would dictate which one from the group is returned. Similar to what is discussed here: [http://blog.jteam.nl/2009/10/20/result-grouping-field-collapsing-with-solr/](http://blog.jteam.nl/2009/10/20/result-grouping-field-collapsing-with-solr/) From my understanding, it seems that in order for field collapsing to be efficient, the result set must be relatively small. Thanks, Paul ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [July 13, 2010, 7:24am UTC](https://discuss.elastic.co/t/server-weighting-and-field-collapsing/3093/2 "2010-07-13T07:24:06Z")
Agreed on both features, both are something that I want to tackle for elasticsearch. Open issues for them? On Tue, Jul 13, 2010 at 10:14 AM, Paul [ppearcy@gmail.com](mailto:ppearcy@gmail.com) wrote: > Hello, > I've been very impressed with what I've seen so far with ES and was > curious if a couple of features were available or planned. > > 1. Ability to weight servers in the cluster to receive different > loads. Our newer h/w always seems to be 2x faster than older h/w and > we'd like it to receive that load when placed into the cluster. > > 2. Ability to collapse on a field. For example, I want the most > relevant result from all different report types. Or similarly, the > most recent result of each report type. So, the sort order would > dictate which one from the group is returned. Similar to what is > discussed here: > [http://blog.jteam.nl/2009/10/20/result-grouping-field-collapsing-with-solr/](http://blog.jteam.nl/2009/10/20/result-grouping-field-collapsing-with-solr/) > > From my understanding, it seems that in order for field collapsing to > be efficient, the result set must be relatively small. > > Thanks, > Paul ---
**Author:** ![ppearcy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppearcy/32/980_2.png) [@ppearcy](https://discuss.elastic.co/u/ppearcy)\ **Post date:** [July 13, 2010, 5:04pm UTC](https://discuss.elastic.co/t/server-weighting-and-field-collapsing/3093/3 "2010-07-13T17:04:09Z")
Great, thanks! > > > Ability to collapse on a field. For example, I want the most relevant result fro…m all different report types. Or similarly, the most recent result of each report type. Or maybe, I want to de-dup on headline. > > So, the sort order would dictate which one from the group is returned. Similar to what is discussed here: > http://blog.jteam.nl/2009/10/20/result-grouping-field-collapsing-with-solr/ > > From my understanding, it seems that in order for field collapsing to be efficient, the result set must be relatively small. > > This is also referred to as "Combine" on some other search products. > > > Ability to weight servers in the cluster to receive different loads. Our newer h…/w always seems to be 2x faster than older h/w and we'd like it to receive that load when placed into the cluster. > > So, this would allow a per server Weight field that would preferably be a float to allow for arbitrary scaling of load. > > From an implementation perspective, it seems that this can be accomplished via shard allocation. > > Thanks! I'd be happy to provide any input you'd like. On Jul 13, 1:24 am, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > Agreed on both features, both are something that I want to tackle for > elasticsearch. Open issues for them? > > On Tue, Jul 13, 2010 at 10:14 AM, Paul [ppea...@gmail.com](mailto:ppea...@gmail.com) wrote: > > > Hello, > > I've been very impressed with what I've seen so far with ES and was > > curious if a couple of features were available or planned. > > > 1. Ability to weight servers in the cluster to receive different > > loads. Our newer h/w always seems to be 2x faster than older h/w and > > we'd like it to receive that load when placed into the cluster. > > > 1. Ability to collapse on a field. For example, I want the most > > relevant result from all different report types. Or similarly, the > > most recent result of each report type. So, the sort order would > > dictate which one from the group is returned. Similar to what is > > discussed here: > > [http://blog.jteam.nl/2009/10/20/result-grouping-field-collapsing-with](http://blog.jteam.nl/2009/10/20/result-grouping-field-collapsing-with)... > > > From my understanding, it seems that in order for field collapsing to > > be efficient, the result set must be relatively small. > > > Thanks, > > Paul ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:22am UTC](https://discuss.elastic.co/t/server-weighting-and-field-collapsing/3093/4 "2017-07-06T04:22:20Z")