Why/How did my job convert to Read-Only?

jkrfs · ‎2010-01-05

I opened one of my Jobs in a separate Project and it seems that it was converted to a Read-Only job. I never updated its version so I have no idea how this happened? The background color turns darker and I am unable to do anything to it.
I was able to duplicate the job and it opened so that I can edit it, but still, why did this happen? Is there a better solution then to duplicate the job?
thanks

Anonymous · ‎2010-02-23

Hello

Has shong posted a solution to these locked jobs yet? I'd love to learn more on a resolution to this.

Gennerally, the job is locked as you are creating several version of job. In Talend, only the latest version of job is open, and other versions are locked. When double clicking on the job name on repository, it will open the latest version of job in job editor. So, if you see the job status becomes read-only, please check if it is the latest version of job. Sometines, if you can't open the latest version of job, go to Navigator--->your project name folder-->process and remove the two files of old version job: jobName_oldVersion.item, jobName_oldVersion.properties, then return back to repository viewer and click on 'refresh' button.
Best regards
shong

Anonymous · ‎2010-02-23

I have tried removing the newly created locked version only to find that when i again try to version the original EVERY new verison is created as locked. I ended up opening the job, copying everything and pasting it into a new job so i could work with it. That seems to defeat the purpose of version control but i don't have the time to spend.

Anonymous · ‎2010-02-23

I had also tried to remove file of old versions but it didn't change anything. The only way around that locking problem (which actually happened every time I used TOS 3.2.2

) was to create a new job, copy all the components from the locked job to the new job, delete the locked job and rename the new job with the name of the previously locked job. I didn't find any other way to unlock those.
... on the other hand, no locking problems with TOS 3.2.3 ;-). (ok, but a little other problem with the job export function that doesn't export very well ...)

_AnonymousUser · ‎2010-03-03

With regards to older versions of jobs; why can't I modify them or save them under another name? If the current version of a job isn't working right do I need to remove it in order to "free up" the earlier one? How do I remove a version?
Thanks in advance...
- Russell

Anonymous · ‎2010-03-04

Hello

If the current version of a job isn't working right do I need to remove it in order to "free up" the earlier one?

Yes, go to Navigator--->your project name folder-->process and remove the two files of old version job: jobName_oldVersion.item, jobName_oldVersion.properties, then return back to repository viewer and click on 'refresh' button.
Best regards

shong

Anonymous · ‎2010-04-07

I can bring some more info to this read-only problem.
In TOS 3.2.3, I have just found out one more job that had turn to read-only. It happened that I was on the 10th version of that job and when it turned from version 3.9 to 3.10, it became read-only. It seems that 3.10 is considered as an 'older' version that 3.9.
Upgrading the job to version 4.0 made it (re)writable.
Either considering version 3.10 as being newer than v3.9 OR limiting the number of sub-version to 9 (x.0 to x.9 only) could avoid people getting very frustrated with these read-only blockage ... (just a couple of ideas)
Should I create a bug ticket?

Anonymous · ‎2010-04-12

I have the same trouble passing from 9.0 to 10.0 version of my Job with TIS 3.2.

Anonymous · ‎2010-04-12

Hello raton an jllecardinal

Should I create a bug ticket?

It shoud be a bug, please report it on our bugtracker.
Thanks for your support!!
Best regards
Shong

Anonymous · ‎2010-04-12

Thanks shong, reported in bug 0012625.

Other

Talend Data Integration