[
https://issues.apache.org/jira/browse/MAPREDUCE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894173#action_12894173
]
Dick King commented on MAPREDUCE-323:
-------------------------------------
I need to modify {{getMatchingJob(String, String, String[])}} in my comment of
28/Jul/10 03:09 PM as follows:
{noformat}
class PathCow implements Iterator<Path> {
// Iterator<Path> methods
int numberMatches();
// returns number of matches you could get if you drive the Iterator to
// the end. Might be an approximation.
}
PathCow getMatchingJob
(String user, String jobnameSubstring, String[] dateStrings,
boolean backwards)
throws IOException
// has no remove() method
// any criterion can be null
// filtering is conjunctive
// dates are MM/DD/YYYY
// results happen approximately oldest first [or newest first,
// if backwards is true]
// a new file that gets added after the iterator is created can either be
// or not be delivered by the result
// dates are approximations of completion time
{noformat}
> Improve the way job history files are managed
> ---------------------------------------------
>
> Key: MAPREDUCE-323
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-323
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Amar Kamat
> Assignee: Dick King
> Priority: Critical
>
> Today all the jobhistory files are dumped in one _job-history_ folder. This
> can cause problems when there is a need to search the history folder
> (job-recovery etc). It would be nice if we group all the jobs under a _user_
> folder. So all the jobs for user _amar_ will go in _history-folder/amar/_.
> Jobs can be categorized using various features like _jobid, date, jobname_
> etc but using _username_ will make the search much more efficient and also
> will not result into namespace explosion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
