When the data size is huge, starting a job such as SUBMIT JOB STATS may consume quite a lot of system resources. And we don't always need to run SUBMIT JOB STATS when we need statistics.
Running SHOW STATS returns the statistics made from the latest stats job, users have two choices:
Always run SUBMIT JOB STATS before SHOW STATS to make sure they have the most recent statistics.
Run SHOW JOBS to see if the last SUBMIT JOB STATS is finished at a time that they could accept. For example, SHOW JOBS shows that the most recent SUBMIT JOB STATS job was finished this morning, and they have not imported or inserted any new data since yesterday, then they can just run SHOW STATS to get the statistics, without having to run SUBMIT JOB STATS.
OK, can we save the user some time, like, add a line in the SHOW STATS results to show when these statistics were made?
When the data size is huge, starting a job such as
SUBMIT JOB STATS
may consume quite a lot of system resources. And we don't always need to runSUBMIT JOB STATS
when we need statistics.Running
SHOW STATS
returns the statistics made from the latest stats job, users have two choices:SUBMIT JOB STATS
beforeSHOW STATS
to make sure they have the most recent statistics.SHOW JOBS
to see if the lastSUBMIT JOB STATS
is finished at a time that they could accept. For example,SHOW JOBS
shows that the most recentSUBMIT JOB STATS
job was finished this morning, and they have not imported or inserted any new data since yesterday, then they can just runSHOW STATS
to get the statistics, without having to runSUBMIT JOB STATS
.OK, can we save the user some time, like, add a line in the
SHOW STATS
results to show when these statistics were made?