Hi, Each storage group has its own retention policy is fine. In our configuration, merging can be disabled or at very low frequency. Is it better to execute a global (bounded with the storage group) delete plan periodically?
Best, -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -----原始邮件----- > 发件人: "Xiangdong Huang" <[email protected]> > 发送时间: 2019-09-17 08:32:12 (星期二) > 收件人: [email protected] > 抄送: > 主题: Re: [jira] [Created] (IOTDB-205) Support retention policy > > +1 for the feature. > Cassandra names it as TTL. > > So, how about for each storage group, there is a retention policy. And, > clean the old data when merging. > > ----------------------------------- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Jialin Qiao (Jira) <[email protected]> 于2019年9月9日周一 下午5:13写道： > > > Jialin Qiao created IOTDB-205: > > --------------------------------- > > > > Summary: Support retention policy > > Key: IOTDB-205 > > URL: https://issues.apache.org/jira/browse/IOTDB-205 > > Project: Apache IoTDB > > Issue Type: New Feature > > Reporter: Jialin Qiao > > > > > > Many applications use TSDBs to just store recent data for a period of > > time. For example, 10 days, and older data will be deleted automatically. > > Influxdb also supports this function called retention policy. > > > > It would be great that we also support this. > > > > > > > > -- > > This message was sent by Atlassian Jira > > (v8.3.2#803003) > >
