Schema viewer should not automatically show versioned tables

[fbertsch]

In Presto, we have both $TABLENAME, and $TABLENAME_$VERSION, where we have many historical versions of a table. Most of the time, people just need $TABLENAME. Not only does having all the versions clutter the menu, it also slows it down drastically and makes it difficult to use.

I would propose some way to optionally view all versioned datasets for a $TABLENAME.

Note that this is specifically a mozilla thing, and has to do with how we process ETL jobs in our pipeline. Parquet2hive guarantees this $TABLENAME_$VERSION and $TABLENAME convention.

[arikfr]

In the no so distant future I want to improve the schema browser & add a dedicated screen for it. As part of this I'm thinking of letting the user decide which tables he wants to show in the schema browser. So you will be able to hide all the $TABLENAME_$VERSION.

Re slow down: that shouldn't happen any more. How many tables/columns do you have?

[fbertsch]

I just verified again that the slow down occurs. It is very difficult to scroll through the list of tables.

We have 195 tables, of which 164 are versioned tables.

[arikfr]

Just noticed that the version you're deploying doesn't have the performance fix I made to the schema browser. So hopefully once you deploy master it will resolve the slow down.

[fbertsch]

Makes sense, that was going to be my guess as well. Would still like to see the other improvements to the schema browser!

[arikfr]

Me too ;-)

[washort]

We'll ignore table names on Presto of the form 'foo_vN' in the schema listing.
bf10361

[fbertsch]

I don't know if that's a good solution. The versioned tables have different schemas, they should still be available, but only when needed.

[washort]

The schema listing loads everything at once, so we'd have to invent some means for discerning when that should include versioned tables or not.