tree 457b7b7b61e1dedaa27d5f269ff0a96b404bb378
parent 6e4213bb3aac91552835927f8f171a8ef87ab614
author Dmitry Lychagin <dmitry.lychagin@couchbase.com> 1595430658 -0700
committer Dmitry Lychagin <dmitry.lychagin@couchbase.com> 1595461895 +0000

[NO ISSUE][COMP] Support dropping dataverse only if it's empty

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

Details:
- Add ifEmpty flag to DataverseDropStatement to indicate that
  the dataverse must be dropped only if it does not contain any
  objects. This flag is currently not supported in the grammar,
  but may be used by product extensions.
- Add validateDataverseStateBeforeDrop() method that is called
  before a dataverse is about to be dropped. It may be used
  by product extensions to perform additional checks before
  dropping the dataverse.
- Refactor handleCreateIndexStatement() to align with other
  handle*() methods (acquires locks, then calls doCreateIndex()).
- Ensure that all doDrop*() methods return a boolean value
  indicating whether the entity was actually dropped.

Change-Id: I86aca8ab02cf1bf0e0600237d3e2f71293166b08
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/7204
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Dmitry Lychagin <dmitry.lychagin@couchbase.com>
Reviewed-by: Ali Alsuliman <ali.al.solaiman@gmail.com>