ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Ozerov <voze...@gridgain.com>
Subject Re: Clarification on DROP TABLE command needed
Date Tue, 17 Oct 2017 07:10:02 GMT
Hi Denis,

1) Yes, cache is destroyed and data is purged.
2) We acquire table lock, so that DML and SELECT statements will be blocked
until operation is finished. Exception about missing table will be thrown

On Tue, Oct 17, 2017 at 1:40 AM, Denis Magda <dmagda@apache.org> wrote:

> Alex P., Vladimir,
> I’m finalizing DROP TABLE command documentation and unsure what happens
> with the following once the command is issued:
> 1. Do we destroy the underlying cache and purge all its content?
> 2. What happens to DML operations targeting a table that is somewhere in
> the middle of the drop process? Do we block such DML commands waiting while
> the DROP TABLE is over or kick them off right away with some special
> exception?
> —
> Denis

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message