[DOCS-3983] Comment on: "mongodb-ecosystem/use-cases/pre-aggregated-reports.txt" Created: 03/Sep/14  Updated: 11/Jan/17  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: ecosystem
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Minor - P4
Reporter: Edoardo Paolo Scalafiotti Assignee: Allison Reinheimer Moore
Resolution: Won't Fix Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

linux, PHP 5.5, Mongo 2.6, Yii 2.0

Location: http://docs.mongodb.org/ecosystem/use-cases/pre-aggregated-reports/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.94 Safari/537.36
Referrer: http://docs.mongodb.org/ecosystem/use-cases/hierarchical-aggregation/
Screen Resolution: 1920 x 1080
repo: docs-ecosystem
source: use-cases/pre-aggregated-reports


Issue Links:
Related
related to DOCS-4894 Pre-Aggregated Reports use case doc n... Closed
Participants:
Days since reply: 7 years, 29 weeks ago
Epic Link: docs-cleanup-ecosystem

 Description   

I'm replicating this use case in a PHP app but I'm not seeing where this script sets all values to 0 with the pre-allocation (because it only sets the metadata, not the values). Moreover, if the pre-allocation is purely random, how to be sure that when it happens, is not overwriting existing values?



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Generated at Thu Feb 08 07:46:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.