Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
MIME-Version: 1.0
Date: Thu, 11 Jun 2015 13:47:31 -0500
Message-ID: 
 <CAFk21wdiQJwqzwACwdcAmomWBZeSnkAAbfBXeLuT9f4y1=PLfg@mail.gmail.com>
Subject: Table Delete in Apache Hbase
From: Arun Kumaran Sabtharishi <arun1087@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=047d7b1636e18a7f180518426cfb

--047d7b1636e18a7f180518426cfb
Content-Type: text/plain; charset=UTF-8

Hello Hbase users and developers,

I have a few questions regarding how table table delete works in hbase.

*What I know:*
If a hbase table is deleted(after disabling), the SYSTEM.CATALOG entries
related to that table will be deleted.

If a view is created using phoenix (assuming there are other views which
are not related to each other) and the view that has been created is
deleted, the SYSTEM.CATALOG entries related to the view will be deleted.
Okay. Sounds good!

*What I want to know:*
Does the 'delete view' checks whether the other views(which were already
existing) are going to be affected(doing a scan)?

If table T1 and views V1, V2 and V3 already exists.

Create a view Vx which is not dependent/related to any of V1, V2 and V3.

Delete Vx.

Does the delete Vx checks SYSTEM.CATALOG for V1, V2 and V3? In other words,
does it do a scan to check whether the V1, V2 and V3 are dependent/related
to Vx?

Thanks,
Arun

--047d7b1636e18a7f180518426cfb--