You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/03/09 21:24:00 UTC

[jira] [Commented] (ASTERIXDB-1952) Filters are not properly reconstructed during recovery

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

ASF subversion and git services commented on ASTERIXDB-1952:
------------------------------------------------------------

Commit 693844cc5cccaf78db6b1260f1656292558c8a70 in asterixdb's branch refs/heads/master from [~imaxon]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=693844c ]

[ASTERIXDB-1952][TX][IDX] Filter logs pt.2

- user model changes: no
- storage format changes: yes
- interface changes: yes

Details:
- Add a log type specifically for filters
- Only log change when filter actually widens
- Stop logging of index + filter tuple during modification
- Redo index and filter tuples separately via their logs

Change-Id: Ie9e7795d9c8c212e8610dcb9bb5d26ec9fbbee8a
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1857
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <je...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Ian Maxon <im...@apache.org>


> Filters are not properly reconstructed during recovery
> ------------------------------------------------------
>
>                 Key: ASTERIXDB-1952
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1952
>             Project: Apache AsterixDB
>          Issue Type: Bug
>            Reporter: Ian Maxon
>            Assignee: Ian Maxon
>            Priority: Major
>
> The redo process does not reconstruct the state of the in-memory component's filter right now. Basically it lacks the knowledge of either the metadata to extract this info, or the extra explicitly logged information. This causes the disk components created during recovery to have essentially bogus data for the filter values. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)