Re:Re: Re: Re: Discussion on the support of V1 and V2 storage formats in future versions

2020-11-04 Thread 陈明雨
> Maybe we can implement a thread to convert all V1 rowset to V2 in >backgroud. >And using a counter to count how many V1 rowset in one BE. Yes, using a certain thread maybe a good way. -- 此致!Best Regards 陈明雨 Mingyu Chen Email: morning...@163.com; morningman@gmail.com 在 2020-11-02 10:2

Re: Re: Re: Discussion on the support of V1 and V2 storage formats in future versions

2020-11-01 Thread Zhao Chun
陈明雨 于2020年10月30日周五 下午9:30写道: > So how to make sure that all tablets are being compacted and converted to > V2? > Some of tablet may not be triggered to the compaction. > > > Maybe we can implement a thread to convert all V1 rowset to V2 in backgroud. And using a counter to count how many V1 rowse

Re:Re: Re: Discussion on the support of V1 and V2 storage formats in future versions

2020-10-30 Thread 陈明雨
So how to make sure that all tablets are being compacted and converted to V2? Some of tablet may not be triggered to the compaction. -- 此致!Best Regards 陈明雨 Mingyu Chen Email: chenmin...@apache.org 在 2020-10-29 14:05:31,"Zhao Chun" 写道: >陈明雨 于2020年10月29日周四 下午12:24写道: > >> > We can fiinis

Re: Re: Discussion on the support of V1 and V2 storage formats in future versions

2020-10-28 Thread Zhao Chun
陈明雨 于2020年10月29日周四 下午12:24写道: > > We can fiinish it when doing compaction, schema change. > Currenlty we do have a approach to automatically convert v1 to v2, by > setting config in be.conf. > But this approach is totally uncontrollable, that we can't even know when > it can finish. > > As fa

Re:Re: Discussion on the support of V1 and V2 storage formats in future versions

2020-10-28 Thread 陈明雨
> We can fiinish it when doing compaction, schema change.Currenlty we do have a > approach to automatically convert v1 to v2, by setting config in be.conf. But this approach is totally uncontrollable, that we can't even know when it can finish. And it is both time consuming and space consumimg.

Re: Discussion on the support of V1 and V2 storage formats in future versions

2020-10-28 Thread ling miao
I don’t think it’s a problem as long as it is divided into several parts. But now there is a problem that the v2 version of the table is actually very few, it is difficult for us to truly verify the stability of v2 in a certain version. Or are there any points that can guide users to trigger the c

Re: Discussion on the support of V1 and V2 storage formats in future versions

2020-10-28 Thread Zhao Chun
陈明雨 于2020年10月29日周四 上午9:56写道: > I agree to disable the use of V1 storage format for newly created tables > in version 0.14. > > > But "automatically convert to V2" is a dangerous and time-consuming > operation, we may need more discuss. > > We can fiinish it when doing compaction, schema change.

Re: Discussion on the support of V1 and V2 storage formats in future versions

2020-10-28 Thread Zhao Chun
+1 I think we can convert V1 to V2 in version 0.14 automatically. And leave a configure to disable this convert. However we should give user an easy way to make them know if there is V1 segment when we remove V1 code completely. Thanks, Zhao Chun apache 于2020年10月29日周四 上午9:48写道: > Hello every

Discussion on the support of V1 and V2 storage formats in future versions

2020-10-28 Thread apache
Hello everyone: At present, our V2 storage format has been developed for a long time, and V2 has many advantages that V1 does not have. The coexistence of V1 and V2 brings a lot of code and cluster maintenance costs. Therefore, I think the next version, that is, version 0.14 will disable the use