tree 4947425db25d2bc761562b7b3bd79ba0f6a35b47
parent bfe9b0244eec13b5290bf47c04aea7688123f2ab
author Murtadha Hubail <mhubail@apache.org> 1536319447 +0300
committer Murtadha Hubail <mhubail@apache.org> 1536335395 -0700

[NO ISSUE][STO] Ensure Index Component Sequence Uniqueness

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

Details:
Currently, if two or more flushes are scheduled before any
of them create its files on disk, we will end up reusing
the same component sequence since the last used component
sequence is based on the files on disk. This change ensures
that the last use component sequence is only initialized
from the disk files and after that the last used component
sequence is incremented in memory.

Change-Id: I478ca3e2c9a98bab14a9145cc8b23eadbd0eab08
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2958
Sonar-Qube: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Murtadha Hubail <mhubail@apache.org>
Reviewed-by: Till Westmann <tillw@apache.org>