asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ASTERIXDB-1109) Index entries are not deleted on an open-type secondary index
Date Tue, 24 Nov 2015 22:22:11 GMT


ASF subversion and git services commented on ASTERIXDB-1109:

Commit a05f71826a4ab2c0e7148009e0b7e269b15e0a2f in incubator-asterixdb's branch refs/heads/release-0.8.8
from [~iabsalyamov]
[;h=a05f718 ]

ASTERIXDB-1109: Fixed deletion of records from open secondary index
 - Avoided creating calling record constructor in delete pipeline
 - Fixed the case when multiple open indexes enforce the type of the
  same field & covered it with tests

Change-Id: I41bde91401f67918365de7df19dd2f0de20c73d2
Tested-by: Jenkins <>
Reviewed-by: Yingyi Bu <>

> Index entries are not deleted on an open-type secondary index
> -------------------------------------------------------------
>                 Key: ASTERIXDB-1109
>                 URL:
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: AsterixDB, Operators
>            Reporter: Taewoo Kim
>            Assignee: Ildar Absalyamov
>            Priority: Critical
> Currently, index entries (SK, PK) are not deleted on an open-type secondary index. This
issue was not surfaced due to the fact that every search after a secondary index search needs
to go through the primary index lookup. Therefore, un-deleted entries were removed during
this Pidx lookup.
> Now, we have an index-only plan that can skip the Pidx lookup after a Sidx search. Therefore,
the query result is not correct anymore.

This message was sent by Atlassian JIRA

View raw message