[DOCS-9088] Add a note about types to $bucket's documentation Created: 05/Oct/16 Updated: 21/Nov/16 Resolved: 21/Nov/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Jonathan DeStefano |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 12 weeks, 2 days ago | ||||||||
| Epic Link: | Facets | ||||||||
| Story Points: | 0.25 | ||||||||
| Description |
|
The release notes for the $bucket stage specifies that the 'boundaries' argument should contain values which are all the same type. This is slightly inaccurate, since you are allowed to mix numeric types as described in this note about bson types and sort orders. For example, [1, NumberLong(2), NumberInt(3)] is a valid specification for 'boundaries'. It's also probably worth mentioning that 'default' can be of a different type than the entries in 'boundaries'. |
| Comments |
| Comment by Jonathan DeStefano [ 21/Nov/16 ] |
|
These points were added to $bucket's documentation. Tracking remaining effort under |