Job order in HistoryServer is not always correct

Now in JobHistoryServer, jobs are ordered by JobID in a datatable. JobID here is interpreted as a string rather than parsing the id number from the JobID. As a result, jobID job_1516090502319_9999 is alway in front of  job_1516090502319_10123 while the latter is the newer job.