What's different between the two environments (i.e. the working and not working ones)? Do they have the same amount of data (i.e. number of views)? Do you mean 1.3M views or 1.3M rows? Do you have any indexes on your views? If not, then dropping a view is nothing more than issuing a delete over the handful of rows in the SYSTEM.CATALOG table. Have you tried profiling it?
Some features, such as CASCADE DROP and soon having the ability to add a new column to a table that has views (PHOENIX-1504) rely on the SYSTEM.CATALOG table being a single region. Once transactions are ready, we'll likely move the DDL operations to use this mechanism instead of relying on the mutateRowsWithLocks functionality (at which point splitting would be ok). Thanks, James On Fri, Jun 5, 2015 at 3:10 PM, Arun Kumaran Sabtharishi <[email protected]> wrote: > Adding some information on this, > > The SYSTEM.CATALOG has around 1.3 million views and the region count is 1. > > Is it safe to split the SYSTEM.CATALOG table? > > Would splitting help the performance of dropping? > > Thanks, > Arun
