[Mondrian] timezones in timedimension

Oren Mazor oren.mazor at shopify.com
Mon Mar 25 23:30:13 EDT 2013

That's what we do (utc) but what about aggregates? Those I can't really cast to a timezone on output. Ill probably have to double store a time ID per sale with my ETL. 

On 2013-03-24, at 8:58 AM, Robert Lemmen <robertle at semistable.com> wrote:

> On Sat, Mar 23, 2013 at 07:19:49PM -0400, Oren Mazor wrote:
>> The reason I ask is that I have a multi-tenant data cube, and different tenants would like to see things in their native timezone. 
> isn't the general rule (for all software?) to store and process time 
> in a timezone-neutral format (UTC string, epoch seconds etc), and only
> do the timezoning on input and output? wouldn't that solve your problem
> as well?
> regards  robert
> -- 
> Robert Lemmen                               http://www.semistable.com 
> _______________________________________________
> Mondrian mailing list
> Mondrian at pentaho.org
> http://lists.pentaho.org/mailman/listinfo/mondrian

More information about the Mondrian mailing list