Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[HTCondor-users] Idiom for job transforms with late-materialization factories
- Date: Tue, 4 Feb 2025 08:37:23 +0100
- From: Jeff Templon <templon@xxxxxxxxx>
- Subject: [HTCondor-users] Idiom for job transforms with late-materialization factories
Hi,
If the user uses a late-materialization factory, then job transforms are applied twice - once when making the factory Ad, and then again for each instantiation of a job.
Is there some mechanism or idiom in the job transform language to help deal with this? I have a case where a user might have specified a value for a ClassAd at job submission, and the transform is putting information into the same (multi valued) classAd, either creating it if it did not exist (the user specified nothing) or appending if the user did. Since I donât know how to detect âfirst passâ or âsecond passâ, I get stuff like
Ad = user_value, system_value, system_value
The system value is repeated since the transform is repeated. One solution is to forbid users to give their own values, Iâd like to avoid that though, there are good reasons why a user might do that.
JT