Skip to main content
Announcements
A fresh, new look for the Data Integration & Quality forums and navigation! Read more about what's changed.
cancel
Showing results for 
Search instead for 
Did you mean: 
EV89
Contributor III

Drop table if exists and create doesn't works - table already exists error

Hello,

 

i set up a job to import a csv file in mysql table. I choose the Drop table if exists and create option in mysql output component.

 

The job works the first time when it's create the table, but the second time the job give error "table already exists" instead to drop the table and recreate it.

 

I attach you the screenshot and the error message, any idea?

 

thanks 

Labels (3)
1 Solution

Accepted Solutions
EV89
Contributor III
Author

We have discard the Talend project and recreate it. Now the job works without problems. I dont'know  if i inadvertently change something or if the project was corrupt in somehow.

 

 

View solution in original post

4 Replies
Anonymous
Not applicable

This is interesting. I have just tried this in 7.2.1. It works for me. Can you tell me what version you are trying this with? You *may* have found a bug. Just to make sure, can you check that you have the privileges to drop the table? I see you are using root, but if you could double check that you don't have some non default settings that might prevent this, that would be useful.

EV89
Contributor III
Author

I think privilege to drop is ok, i can manual drop the table with heidi sql and if i change action and select remove table and create table it works (see screenshoot). It' s strange also that if i try to retrieve table schema from database Talend return me no result.

 

I don' t know if this is a bug because i don't work with the latest version. I attach screenshoot with other information.


version_talend.png
schema.png
rimuove se esiste.png
EV89
Contributor III
Author

We have discard the Talend project and recreate it. Now the job works without problems. I dont'know  if i inadvertently change something or if the project was corrupt in somehow.

 

 

Anonymous
Not applicable

This is unusual, but sometimes a job can get corrupted if the Studio has been left open for a long time (several days) and memory issues occur. It is good practice to make sure the Studio is shutdown on a daily basis at least. Although, I do not always live by that rule 🙂