Re: join column derived vs normal
Hi Sachin Aggarwal When a lookup table is stored as snapshot, all columns in that table will be taken as derived dimension by default during cube design. Compare to normal dimension, derived dimension does not participate in cube calculation directly. Instead, it is represented by its FK (Foreign Key) in cube. That is why using derived dimensions can greatly reduce cube complexity. During query, derived dimensions have to be converted to their FKs first, causing a small panalty to performance. --- Regards! Aron Tao On [DATE], "[NAME]" <[ADDRESS]> wrote: Hi Team, while creating cube what are recommendations across join column between fact and dimension. should we mark it as derived or normal while selecting it from dimension column. what factors play a role in making this decision. -- Thanks & Regards Sachin Aggarwal
??????join column derived vs normal
I hope this may help you. http://kylin.apache.org/docs/howto/howto_optimize_cubes.html -- -- ??: "Sachin Aggarwal"; : 2018??10??23??(??) 7:25 ??: "user";"dev"; : join column derived vs normal Hi Team, while creating cube what are recommendations across join column between fact and dimension. should we mark it as derived or normal while selecting it from dimension column. what factors play a role in making this decision. -- Thanks & Regards Sachin Aggarwal
join column derived vs normal
Hi Team, while creating cube what are recommendations across join column between fact and dimension. should we mark it as derived or normal while selecting it from dimension column. what factors play a role in making this decision. -- Thanks & Regards Sachin Aggarwal