stats table timestamp incorrectly used as table timestamp

I think there is a problem introduced by PHOENIX-1390 related to table timestamps.

We run into a situation where we are unable to drop a table due to a NewerTableAlreadyExistsException. This table was created at a certain timestamp in the past (say 2 years ago) and we try to drop it at a more recent timestamp in the past (say 1 year ago).

During the drop, the client timestamp (1 year ago) is compared with the table timestamp. The table timestamp should be 2 years ago, but due to this statement on line 856 in MetaDataEndpointImpl:

timeStamp = Math.max(timeStamp, stats.getTimestamp())

the timestamp of the table is set to the timestamp of the stats table, which happens to be something much more recent.

I think this is wrong?