Bug 3740 - Recovery INFO lines with full EPRs instead of resource IDs
: Recovery INFO lines with full EPRs instead of resource IDs
Status: RESOLVED FIXED
: GRAM
wsrf managed execution job service
: unspecified
: PC Linux
: P3 normal
: 4.2
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-09-12 11:54 by
Modified: 2005-10-11 15:46 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-09-12 11:54:16
I'm thinking that we should just print full EPRs to jobs instead of just the
resource IDs in the INFO lines that get printed upon recovery of job resources.
 If we're not going to endorse the usage of handles, then it's stupid for us to
expect users to know how to construct an EPR from a resource ID.

There are some other places where this idea of no handles is being ignored as
well, but I'll file seperate bugs for those.
------- Comment #1 From 2005-09-12 12:54:51 -------
If you do this, please try to keep the eprs to single lines in the log. It is
important to be able to easily parse our logs, and mulit-line XML blobs can be a
problem. 
------- Comment #2 From 2005-09-12 13:00:27 -------
Yes, I was assuming I would do this since the whole point is that we don't want
to expect users to care what the actual content is.  They just need a pointer to
the resource.
------- Comment #3 From 2005-10-11 15:45:14 -------
Fix in HEAD.
------- Comment #4 From 2005-10-11 15:46:48 -------
Changing the milestone to 4.2 since I couldn't implement this in 4.0.x without
a
schema change.