Such big dimensions better be part of the fact table (rather than on a lookup table). Simplest way is to create a hive view joining the old fact and the customer, then assign the view to be the new fact table.
On Tue, Jun 28, 2016 at 5:26 AM, Richard Calaba (Fishbowl) < [email protected]> wrote: > We have same issue though our size is just 700MB …. So interested in the > background info and workarounds other than setting higher snapshot limit … > if any ? > > > > Ric. > > > > *From:* Arun Khetarpal [mailto:[email protected]] > *Sent:* Monday, June 27, 2016 11:55 AM > *To:* [email protected] > *Subject:* Dimension table 300MB Limit > > > > Hi, > > > > We are evaluating Kylin as an Analytical Engine for OLAP. We are facing > issues with OOM when dealing with large dimensions ~ 70GB (customer data) > [set kylin.table.snapshot.max_mb to a high limit] > > > > I guess having a Dictionary this big in memory will not be a solution. Is > there any suggested workaround for the same? > > > > Is there any work done to get around this by the community? > > > > Regards, > > Arun > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2016.0.7640 / Virus Database: 4613/12504 - Release Date: 06/27/16 >
