yes, I will asume this overhead in rowKey
2016-12-02 9:58 GMT+01:00 Billy(Yiming) Liu :
> Using Joint Dimension for your 1:1 relation is the right design.
>
> 2016-12-02 0:21 GMT+08:00 Alberto Ramón :
>
>> Nice Liu
>>
>> We have some cases like
>> DayWeekTXT , DayWeekID
>> MonthTXT, MonthID
>>
>>
jaja,
I think I loss some HBase data (hbck found some error)
The Kylin Log is OK, make a clean start-up, but after data cube isn't
accesible
I tried use metastore.sh to delete all Kylin data (Clean and reset options,
I don't know what is the difference)
OK, I redeploy new system, Isn't problem
There is no such a check tool/command today; Kylin metadata's availability
relies on HBase and HDFS's replication; If the HBase and HDFS no data loss,
then Kylin has no data loss; You can watch the kylin.log during the
startup, Kylin will report error when finding inconsistent metadata.
2016-12-0
Using Joint Dimension for your 1:1 relation is the right design.
2016-12-02 0:21 GMT+08:00 Alberto Ramón :
> Nice Liu
>
> We have some cases like
> DayWeekTXT , DayWeekID
> MonthTXT, MonthID
>
> small proposal:
> Can would be interesting create Derived with 1:1 relation, with support
> for filter
