Affects Version/s: None
Fix Version/s: None
There is a problem with table statistics:
If 2 partitions of a table are being created/updated concurrently,
table level stats may not be correct.
For eg. if a table T has 2 partitions P1 and P2 with number of rows 10 and 20
respectively, and both the partitions are being updated concurrently (via
insert overwrite ...), the table object is obtained in StatsTask and updated.
Even with concurrency turned on, the table is not locked, and the two table
statistics updates may lead to one to them being lost.