You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Denis Magda <dm...@apache.org> on 2017/10/16 22:40:28 UTC
Clarification on DROP TABLE command needed
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
Re: Clarification on DROP TABLE command needed
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Vladimir,
Is the cache purged synchronously or in the background?
D.
On Tue, Oct 17, 2017 at 12:10 AM, Vladimir Ozerov <vo...@gridgain.com>
wrote:
> 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
> afterwards.
>
> On Tue, Oct 17, 2017 at 1:40 AM, Denis Magda <dm...@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
>
Re: Clarification on DROP TABLE command needed
Posted by Vladimir Ozerov <vo...@gridgain.com>.
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
afterwards.
On Tue, Oct 17, 2017 at 1:40 AM, Denis Magda <dm...@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