Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I had a disk issue earlier and when I closed Talend it said there was a problem saving the state of the workbench.
Opening Talend again, the job I was working on is not listed. I had 4 job designs but only 3 are present. I definitely saved the file (successfully!) before the disk error arose, so I can't see why there would be an issue.
Similarly, when I go into
C:\MyProject\MYPROJECT\process
there are 12 files visible each of the 4 job designs has 3 files with extensions
.item
.properties
.screenshot
So they should be there, right? But they're not.
Can anyone suggest what might be going wrong?
Thanks
OK, we're back in business. For the benefit of anyone else who has the same issue, I'll list the steps taken.
NB in my case, both jobs were version 0_1, so all the instructions reference 0_1 in the file name. I guess if yours was a higher version your best bet would be to save the "expendable" job (in step 1) with the same version number and then follow the rest of the steps but adjusting so that 0_1 becomes 0_3 or whatever
Hi,
If you have not saved your job before the disk crash happened, that job will not be available when you open the job next time.
So my advise would be to save the jobs at regular intervals and if you have GIT, copy the source code to GIT also at regular intervals.
Warm Regards,
Nikhil Thampi
@nthampi wrote:
Hi,
If you have not saved your job before the disk crash happened, that job will not be available when you open the job next time.
So my advise would be to save the jobs at regular intervals and if you have GIT, copy the source code to GIT also at regular intervals.
Warm Regards,
Nikhil Thampi
Thanks for the reply. They definitely were saved. In fact, they were created almost a week ago, so they were saved before I turned my computer on. Even if none of my changes for that day had been saved, the job design should still be visible. I'll attach a screenshot of the files sitting in the folder.
Hm, now that I look at it, it's interesting that although the .item and .screenshot files are bigger than any of the equivalent files for the other job designs, the .properties file says 0kb (all the others are 2kb) so I'm now thinking maybe the file got corrupted during the attempted save and that's why it's broken. Possible clue there...
OK, we're back in business. For the benefit of anyone else who has the same issue, I'll list the steps taken.
NB in my case, both jobs were version 0_1, so all the instructions reference 0_1 in the file name. I guess if yours was a higher version your best bet would be to save the "expendable" job (in step 1) with the same version number and then follow the rest of the steps but adjusting so that 0_1 becomes 0_3 or whatever