[DOCS-7097] Typos in "use-cases/pre-aggregated-reports.txt" Created: 04/Feb/16 Updated: 30/Mar/16 Resolved: 10/Mar/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Jake Angerman | Assignee: | Allison Reinheimer Moore |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 48 weeks, 6 days ago |
| Epic Link: | docs-cleanup-ecosystem |
| Description |
|
1. Typos in Separate Documents by Granularity Level: "This introduce a second set of upsert operations to the data collection and aggregation portion of your application but the gains reduction in disk seeks on the queries, should be worth the costs. Consider the following example schema:" Perhaps: "This introduces a second set of upsert operations to the data collection and aggregation portion of your application, but the reduction in disk seeks on the queries should be worth the costs. Consider the following example schema:" 2. Later in the Sharding section: "This is basically unavoidable, since all updates for a single page are going to a single document." 3. Also this awkward sentence: "You may wish to include the date in addition to the site, and page fields so that MongoDB can split histories so that you can serve different historical ranges with different shards." Perhaps: "You may wish to include the date in addition to the site and page fields so that MongoDB can split histories and serve different historical ranges with different shards." |
| Comments |
| Comment by Githook User [ 10/Mar/16 ] |
|
Author: {u'username': u'schmalliso', u'name': u'Allison Moore', u'email': u'allison.moore@10gen.com'}Message: |