You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kylin.apache.org by hongbin ma <ma...@apache.org> on 2016/09/03 08:13:42 UTC
Re: Do not order columns for Auto Generate Dimensions in Cube Design
+1
alphabetical order obviously makes no sense. can we sort them by
cardinality?
--
Regards,
*Bin Mahone | 马洪宾*
Re: Do not order columns for Auto Generate Dimensions in Cube Design
Posted by Luke Han <lu...@gmail.com>.
+1 should keep orginal order
Best Regards!
---------------------
Luke Han
On Sat, Sep 3, 2016 at 6:01 PM, Yiming Liu <li...@gmail.com> wrote:
> I would like suggest keeping original order still. Just like we execute
> "desc table", no reorder happens, and the original order normal has some
> kinds of relationship.
>
> 2016-09-03 16:13 GMT+08:00 hongbin ma <ma...@apache.org>:
>
> > +1
> >
> > alphabetical order obviously makes no sense. can we sort them by
> > cardinality?
> >
> >
> >
> > --
> > Regards,
> >
> > *Bin Mahone | 马洪宾*
> >
>
>
>
> --
> With Warm regards
>
> Yiming Liu (刘一鸣)
>
Re: Do not order columns for Auto Generate Dimensions in Cube Design
Posted by Yiming Liu <li...@gmail.com>.
Agree with Luke. Should I create a JIRA for this feature?
2016-09-04 15:40 GMT+08:00 Luke Han <lu...@gmail.com>:
> I think the designer should keep original order when create "data model"
> And allow user to re-order in a data model.
>
> When create a cube, it should also keep the same order from data model.
>
> User could adjust the order after created dimensions and metrics later
>
> How about this?
>
> Thanks.
>
>
> Best Regards!
> ---------------------
>
> Luke Han
>
> On Sat, Sep 3, 2016 at 11:00 PM, hongbin ma <ma...@apache.org> wrote:
>
> > The order by original table is already lost when we define dimensions in
> > model. So the problem becomes how to order the dimension when creating
> > model?
> >
> > To illustrate the problem let's assume we have fact table and a lookup
> > table. Assume the columns on fact is "dim1, FK, dim2, metrics1,
> metrics2",
> > and the lookup table looks like "PK, dim3, dim4", what kind of ordering
> is
> > reasonable? 1234 ro 1342?
> >
> > On Sat, Sep 3, 2016 at 6:01 PM, Yiming Liu <li...@gmail.com>
> > wrote:
> >
> > > I would like suggest keeping original order still. Just like we execute
> > > "desc table", no reorder happens, and the original order normal has
> some
> > > kinds of relationship.
> > >
> > > 2016-09-03 16:13 GMT+08:00 hongbin ma <ma...@apache.org>:
> > >
> > > > +1
> > > >
> > > > alphabetical order obviously makes no sense. can we sort them by
> > > > cardinality?
> > > >
> > > >
> > > >
> > > > --
> > > > Regards,
> > > >
> > > > *Bin Mahone | 马洪宾*
> > > >
> > >
> > >
> > >
> > > --
> > > With Warm regards
> > >
> > > Yiming Liu (刘一鸣)
> > >
> >
> >
> >
> > --
> > Regards,
> >
> > *Bin Mahone | 马洪宾*
> >
>
--
With Warm regards
Yiming Liu (刘一鸣)
Re: Do not order columns for Auto Generate Dimensions in Cube Design
Posted by Luke Han <lu...@gmail.com>.
I think the designer should keep original order when create "data model"
And allow user to re-order in a data model.
When create a cube, it should also keep the same order from data model.
User could adjust the order after created dimensions and metrics later
How about this?
Thanks.
Best Regards!
---------------------
Luke Han
On Sat, Sep 3, 2016 at 11:00 PM, hongbin ma <ma...@apache.org> wrote:
> The order by original table is already lost when we define dimensions in
> model. So the problem becomes how to order the dimension when creating
> model?
>
> To illustrate the problem let's assume we have fact table and a lookup
> table. Assume the columns on fact is "dim1, FK, dim2, metrics1, metrics2",
> and the lookup table looks like "PK, dim3, dim4", what kind of ordering is
> reasonable? 1234 ro 1342?
>
> On Sat, Sep 3, 2016 at 6:01 PM, Yiming Liu <li...@gmail.com>
> wrote:
>
> > I would like suggest keeping original order still. Just like we execute
> > "desc table", no reorder happens, and the original order normal has some
> > kinds of relationship.
> >
> > 2016-09-03 16:13 GMT+08:00 hongbin ma <ma...@apache.org>:
> >
> > > +1
> > >
> > > alphabetical order obviously makes no sense. can we sort them by
> > > cardinality?
> > >
> > >
> > >
> > > --
> > > Regards,
> > >
> > > *Bin Mahone | 马洪宾*
> > >
> >
> >
> >
> > --
> > With Warm regards
> >
> > Yiming Liu (刘一鸣)
> >
>
>
>
> --
> Regards,
>
> *Bin Mahone | 马洪宾*
>
Re: Do not order columns for Auto Generate Dimensions in Cube Design
Posted by hongbin ma <ma...@apache.org>.
The order by original table is already lost when we define dimensions in
model. So the problem becomes how to order the dimension when creating
model?
To illustrate the problem let's assume we have fact table and a lookup
table. Assume the columns on fact is "dim1, FK, dim2, metrics1, metrics2",
and the lookup table looks like "PK, dim3, dim4", what kind of ordering is
reasonable? 1234 ro 1342?
On Sat, Sep 3, 2016 at 6:01 PM, Yiming Liu <li...@gmail.com> wrote:
> I would like suggest keeping original order still. Just like we execute
> "desc table", no reorder happens, and the original order normal has some
> kinds of relationship.
>
> 2016-09-03 16:13 GMT+08:00 hongbin ma <ma...@apache.org>:
>
> > +1
> >
> > alphabetical order obviously makes no sense. can we sort them by
> > cardinality?
> >
> >
> >
> > --
> > Regards,
> >
> > *Bin Mahone | 马洪宾*
> >
>
>
>
> --
> With Warm regards
>
> Yiming Liu (刘一鸣)
>
--
Regards,
*Bin Mahone | 马洪宾*
Re: Do not order columns for Auto Generate Dimensions in Cube Design
Posted by Yiming Liu <li...@gmail.com>.
I would like suggest keeping original order still. Just like we execute
"desc table", no reorder happens, and the original order normal has some
kinds of relationship.
2016-09-03 16:13 GMT+08:00 hongbin ma <ma...@apache.org>:
> +1
>
> alphabetical order obviously makes no sense. can we sort them by
> cardinality?
>
>
>
> --
> Regards,
>
> *Bin Mahone | 马洪宾*
>
--
With Warm regards
Yiming Liu (刘一鸣)