[
https://issues.apache.org/jira/browse/HADOOP-4670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678502#action_12678502
]
dhruba borthakur commented on HADOOP-4670:
------------------------------------------
The most common case is when a user is looking for the logs of a job that he
had submitted earlier. So, your proposal looks good to me. +1
On a general note, it appears that what we are trying to do is to index the
metadata of completed jobs for efficient retrieval. Is there any way that
Apache Derby http://db.apache.org/derby/ might help in this regard?
> Improve the way job history files are managed
> ---------------------------------------------
>
> Key: HADOOP-4670
> URL: https://issues.apache.org/jira/browse/HADOOP-4670
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Amar Kamat
> Assignee: Amar Kamat
>
> 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.
