-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: ecosystem
-
Labels:
-
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
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
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?
- related to
-
-
- Closed
-