You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kylin.apache.org by Alberto Ramón <a....@gmail.com> on 2017/09/30 08:05:23 UTC
Re: kylin encode
As resume:
yyyy-MM-dd / *yyyyMMdd* / yyyy-MM-dd HH:mm:ss
Check this JIRAS:
https://issues.apache.org/jira/browse/KYLIN-1101
https://issues.apache.org/jira/browse/KYLIN-1441
https://issues.apache.org/jira/browse/KYLIN-1427
On 30 September 2017 at 04:45, 崔苗 <cu...@danale.com> wrote:
> we have a timestamp column used as the partition column,what should be
> used to encoed the column,date or time? what's the difference between the
> two code? BTW, can kylin recognize all the level of timestamp ,no matter
> it's s or ms timestamp?
>
>
> thanks in advanced for your reply.
>
>
>
>
>
>
Re:Re: Re: kylin encode
Posted by 崔苗 <cu...@danale.com>.
the timestamp in kafka table can be recognized and automatically be changed into date format,but the timestamp in hive can't be used?
在 2017-09-30 16:24:43，"Alberto Ramón" <a....@gmail.com> 写道：
>I think yes. You have 3 format to choose o column sompose
>
>On 30 September 2017 at 09:21, 崔苗 <cu...@danale.com> wrote:
>
>> the time column in our table is timestamp such as 1501210920742,saved as
>> bigint in hive,not the date format as yyyy-MM-dd HH:mm:ss,so we must change
>> the timestamp to date format?
>> 在 2017-09-30 16:05:23，"Alberto Ramón" <a....@gmail.com> 写道：
>> >As resume:
>> >
>> >yyyy-MM-dd / *yyyyMMdd* / yyyy-MM-dd HH:mm:ss
>> >
>> >Check this JIRAS:
>> >https://issues.apache.org/jira/browse/KYLIN-1101
>> >https://issues.apache.org/jira/browse/KYLIN-1441
>> >https://issues.apache.org/jira/browse/KYLIN-1427
>> >
>> >On 30 September 2017 at 04:45, 崔苗 <cu...@danale.com> wrote:
>> >
>> >> we have a timestamp column used as the partition column,what should be
>> >> used to encoed the column,date or time? what's the difference between
>> the
>> >> two code? BTW, can kylin recognize all the level of timestamp ,no matter
>> >> it's s or ms timestamp?
>> >>
>> >>
>> >> thanks in advanced for your reply.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>>
>>
>>
Re: Re: kylin encode
Posted by Alberto Ramón <a....@gmail.com>.
I think yes. You have 3 format to choose o column sompose
On 30 September 2017 at 09:21, 崔苗 <cu...@danale.com> wrote:
> the time column in our table is timestamp such as 1501210920742,saved as
> bigint in hive,not the date format as yyyy-MM-dd HH:mm:ss,so we must change
> the timestamp to date format?
> 在 2017-09-30 16:05:23，"Alberto Ramón" <a....@gmail.com> 写道：
> >As resume:
> >
> >yyyy-MM-dd / *yyyyMMdd* / yyyy-MM-dd HH:mm:ss
> >
> >Check this JIRAS:
> >https://issues.apache.org/jira/browse/KYLIN-1101
> >https://issues.apache.org/jira/browse/KYLIN-1441
> >https://issues.apache.org/jira/browse/KYLIN-1427
> >
> >On 30 September 2017 at 04:45, 崔苗 <cu...@danale.com> wrote:
> >
> >> we have a timestamp column used as the partition column,what should be
> >> used to encoed the column,date or time? what's the difference between
> the
> >> two code? BTW, can kylin recognize all the level of timestamp ,no matter
> >> it's s or ms timestamp?
> >>
> >>
> >> thanks in advanced for your reply.
> >>
> >>
> >>
> >>
> >>
> >>
>
>
>
Re:Re: kylin encode
Posted by 崔苗 <cu...@danale.com>.
the time column in our table is timestamp such as 1501210920742,saved as bigint in hive,not the date format as yyyy-MM-dd HH:mm:ss,so we must change the timestamp to date format?
在 2017-09-30 16:05:23，"Alberto Ramón" <a....@gmail.com> 写道：
>As resume:
>
>yyyy-MM-dd / *yyyyMMdd* / yyyy-MM-dd HH:mm:ss
>
>Check this JIRAS:
>https://issues.apache.org/jira/browse/KYLIN-1101
>https://issues.apache.org/jira/browse/KYLIN-1441
>https://issues.apache.org/jira/browse/KYLIN-1427
>
>On 30 September 2017 at 04:45, 崔苗 <cu...@danale.com> wrote:
>
>> we have a timestamp column used as the partition column,what should be
>> used to encoed the column,date or time? what's the difference between the
>> two code? BTW, can kylin recognize all the level of timestamp ,no matter
>> it's s or ms timestamp?
>>
>>
>> thanks in advanced for your reply.
>>
>>
>>
>>
>>
>>