[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: [geclipse-dev] Transferring local input files duringjob submission - changes in jdl
|
Hi Mariusz,
I think you do not need to change the JDL. The directory in Sandbox just tells the system where to find the files that have to be transfered to the CE. The files will be stored on the directory (on the CE) where the executable will be run. So the executable can find the input files.
Jie
-----Ursprüngliche Nachricht-----
Von: geclipse-dev-bounces@xxxxxxxxxxx [mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im Auftrag von Mariusz Wojtysiak
Gesendet: Montag, 12. November 2007 13:25
An: Developer mailing list
Betreff: Re: [geclipse-dev] Transferring local input files duringjob submission - changes in jdl
Ariel Garcia pisze:
> can't you just submit that JDL without further steps?
I have to make changes in JDL, because original JDL refer to files on user's local machine, which is not accessible from worker node.
Submission will look like:
1. Remove from JDL (in g-Eclipse memory) all references to local files 2. Register job on WMS 3. Send local files to sandbox, into location returned during job registration 4. Start job on WMS
> i don't quite understand i think, do you want to use your JDL twice?
> You can write one JDL which then you use to submit the job and the
> input files will be transferrred at the same time.
> Or is that impossible through the API?
We cannot change JSDL->JDL transformation file (because of license), so I have to transform JSDL to JDL (in g-Elipse memory), change JDL (still in g-Eclipse memory) and submit it.
JDL will be submitted only once.
I'm not sure if after sending local files to WN sandbox, should I refer to those files in submitted JDL?
I guess not, because those files are in right place (sandbox).
--
Mariusz Wojtysiak
_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev
