tree 1343b5d8d843ca44060d309d5df9be9055ab42ba
parent 5a34ce7c78e873ed759536b96a9842435032c6dd
author Abdullah Alamoudi <bamousaa@gmail.com> 1527749218 +0300
committer abdullah alamoudi <bamousaa@gmail.com> 1527819144 -0700

[NO ISSUE][STO] Skip deleting unallocated memory component

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

Details:
- This change fixes the component delete logic
- It first ensures that memory is allocated for the index
- Then it checks whether the memory component is to be deleted
- This is important since there might be cases where primary
  index has the memory allocated but not the secondary and
  without allocating secondary and deleting it, we could end
  up with memory components with different ids.

Change-Id: I0c6c7968830f3c9241bd036c0a330be1400349b4
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2668
Sonar-Qube: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: abdullah alamoudi <bamousaa@gmail.com>
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Michael Blow <mblow@apache.org>
Reviewed-by: Murtadha Hubail <mhubail@apache.org>