Details
-
Bug
-
Resolution: Fixed
-
None
-
None
-
*Location*: http://developer.couchbase.com/documentation/server/4.5/architecture/global-secondary-indexes.html
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
*Referrer*: http://developer.couchbase.com/documentation/server/4.5/architecture/incremental-map-reduce-views.html
*Screen Resolution*: 1536 x 864
*Location*: http://developer.couchbase.com/documentation/server/4.5/architecture/global-secondary-indexes.html *User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 *Referrer*: http://developer.couchbase.com/documentation/server/4.5/architecture/incremental-map-reduce-views.html *Screen Resolution*: 1536 x 864
Description
Isn't a 'BETWEEN' operator inclusive of the ends? The example on this page about partitioning the beer index sets name values for the 2 partitions to 'between "A" and "C"' and 'between "C" and "F"', which would be redundant on C if your 'between' operator acts like most betweens which are defined as inclusive of the ends, as in >= "A" and <= "C".
The only logical conclusion if you're attempting to do this without redundancy would mean that your 'between' instead does this: >= "A" and < "C".
Am I explaining myself clearly?
Reporter: Tim Dillon
E-mail: tim.dillon@arris.com