What would you recommend instead, I had thought about block join perhaps I'm open to suggestions tbough
On Wednesday, March 21, 2012, Martijn v Groningen < martijn.v.gronin...@gmail.com> wrote: > I'm not sure if grouping is the right feature to use for your > requirements... Grouping does have an impact on performance which you need > to take into account. > Depending on what grouping features you're going to use (grouped facets, > ngroups), grouping performs well on large indices if you use filters > queries well. > (E.g. 100M travel offers, but during searching only interrested in in > travel offers to specific destinations or in a specific period of time). > Best way to find this out, is to just try it out. > > On 21 March 2012 22:34, Jamie Johnson <jej2...@gmail.com> wrote: > >> I was wondering how much more intensive grouping queries are in >> general. I am considering using grouping queries as my primary query >> because I have the need to store a document as pieces with varying >> access controls, for instance a portion of a document a user can see >> but an admin can see the entire thing (I'm greatly simplifying this). >> My thought was to do a grouping request and group on a field which >> contained a key which the documents all shared, but I am worried about >> how well this will perform at scale. Any thoughts/suggestions on this >> would be appreciated. >> > > > > -- > Met vriendelijke groet, > > Martijn van Groningen >
