You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "刘珍 (Jira)" <ji...@apache.org> on 2022/01/17 10:40:00 UTC

[jira] [Commented] (IOTDB-2282) Tag recover bug after tag upsert

    [ https://issues.apache.org/jira/browse/IOTDB-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477112#comment-17477112 ] 

刘珍 commented on IOTDB-2282:
---------------------------

CREATE TIMESERIES root.sg.dev.s_1 WITH DATATYPE=INT32, ENCODING=PLAIN,compression=SNAPPY tags(salary=low,happy=false)attributes(color=red,eat=icecream);
show timeseries root.**  where salary=low
ALTER timeseries root.sg.dev.s_1 set  salary=high;
show timeseries root.**  where salary=low  //无结果
show timeseries root.**  where salary=high  //有结果

> Tag recover bug after tag upsert
> --------------------------------
>
>                 Key: IOTDB-2282
>                 URL: https://issues.apache.org/jira/browse/IOTDB-2282
>             Project: Apache IoTDB
>          Issue Type: Bug
>          Components: Core/Schema Manager
>            Reporter: Yukun Zhou
>            Assignee: Yukun Zhou
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: master branch, 0.12.5
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> Currently, the tagIndex in metadata module uses mlog to recover.
> However, if user alters one timeseries' tag, the tag will only be updated to the tagLogFile rather than mlog.
> Thus, after tag update operation, the recover won't use the up-to-date tag information in tagLogFile but use the outdated tag information in mlog.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)