[ https://issues.apache.org/jira/browse/ASTERIXDB-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124729#comment-16124729 ]
ASF subversion and git services commented on ASTERIXDB-2025: ------------------------------------------------------------ Commit 476f14c38bc551602cee97d26bc55fd4546927d6 in asterixdb's branch refs/heads/master from [~alamoudi] [ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=476f14c ] [ASTERIXDB-2025][STO] Fix Merge Lifecycle - user model changes: no - storage format changes: no - interface changes: no Details: - Complete merge operation after deletion of old components files. Change-Id: I843de8b26c181205e43f4eabe22a7c43f3ebfcbc Reviewed-on: https://asterix-gerrit.ics.uci.edu/1930 Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Contrib: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Reviewed-by: Murtadha Hubail <mhub...@apache.org> > MergeOperation completes before deleting old components from disk > ----------------------------------------------------------------- > > Key: ASTERIXDB-2025 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-2025 > Project: Apache AsterixDB > Issue Type: Bug > Components: STO - Storage > Reporter: Abdullah Alamoudi > Assignee: Abdullah Alamoudi > > This could lead to conflict between delete index and deleting old components > which would make one of them to try and delete non-existing files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)