> 1. We have around 35 dimensions and 1 measure where most of dimensions are transactional and we want all those in a single cube.
There is no simple answer. If you could share the data model, we may help. > 2. Moreover we have update scenarios that we need to update on the cube incrementally everyday where updates can happen on any record present already in the previous days cube data. You can refresh a segment to update it. > 3. How distinct count on any of the dimension column present in different segment calculated? Count distinct on dimension is calculated at runtime using sets. On Tue, Jun 7, 2016 at 7:08 PM, Sudeep Dey <[email protected]> wrote: > Hi, > > We have the following use case and we need a solution on how to handle the > same in Kylin :- > > 1. We have around 35 dimensions and 1 measure where most of dimensions are > transactional and we want all those in a single cube. > 2. Moreover we have update scenarios that we need to update on the cube > incrementally everyday where updates can happen on any record present > already in the previous days cube data. > 3. How distinct count on any of the dimension column present in different > segment calculated? > > -- > Thanks and Regards > > Sudeep Dey > Zaloni Technology > IDC,Nexia Park > Christian Basti > Pin-781005 > > > "This e-mail, including attachments, may include confidential and/or > proprietary information, and may be used only by the person or entity > to which it is addressed. If the reader of this e-mail is not the intended > recipient or his or her authorized agent, the reader is hereby notified > that any dissemination, distribution or copying of this e-mail is > prohibited. If you have received this e-mail in error, please notify the > sender by replying to this message and delete this e-mail immediately." > > > > > > > >
