From: | Jayadevan <maymala(dot)jayadevan(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: OLAP |
Date: | 2013-08-28 03:50:24 |
Message-ID: | 1377661824903-5768782.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alban Hertroys-4 wrote
> How is Pentaho an OLAP tool? Aren't you mixing up a few things?
> We already use Pentaho for ETL, so I'm a bit familiar with it. Why do you
> consider it suitable for managing an OLAP database?
>
> How would Pentaho manage cube rollup triggers, business models, dimensions
> and stuff like that?
> We don't want to hand code those, that's far too error-prone and far too
> much work to keep track of. That stuff needs to be automated, preferably
> similar to what we're used to from Gentia (well, not me - I can't make
> heads or tails of Gentia, but the person who asked me about PG's
> suitability has been developing with it for years). That's what we're
> comparing to.
Pentaho, Jasper and Actuate are the common OLAP tools. Pentahos' ETL tool
(Kettle) is more popular than their Reporting solution. Similarly, Jasper's
reporting tool is more popular than their ETL (they integrate talend). The
OLAP functionality in both come from Mondrian, as far as I know.
The cubes, dimensions etc can be defined using a UI tool and uploaded to the
reporting "server" - either Jasper or Pentaho. These typically support MDX,
in addition to standard SQL.
http://en.wikipedia.org/wiki/MultiDimensional_eXpressions
--
View this message in context: http://postgresql.1045698.n5.nabble.com/OLAP-tp5768698p5768782.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | bricklen | 2013-08-28 03:53:06 | Re: OLAP |
Previous Message | Tom Lane | 2013-08-28 02:50:06 | Re: pg_extension_config_dump() with a sequence |