Can you please send the instance that had this failing import to cloud-sql@google.com? I'd like to investigate why the failed import didn't return an error to you. (usually, this error shows up as the result of the operation and you can see it on the Cloud Console, gcloud, or through the API.)
On Monday, April 3, 2017 at 12:54:01 PM UTC-7, Brian Kessler wrote:
-- On Monday, April 3, 2017 at 12:54:01 PM UTC-7, Brian Kessler wrote:
Hi,I was trying to import data into CloudSQL and was facing a confusing situation of barely any rows of my data being imported into the destination table even though the import was recorded as successful. Eventually, I realized that the issue was an improper key setup on my table so that most of the entries were being discarded for duplicate primary key. However, I could not figure out how to access any logs that would report that this was in fact what was happening. The operation log in the cloud console just reported that the load operation was successful, not that most of the rows had been discarded. In general, I've stumbled across these issues with the CSV import in CloudSQL that it is very permissive on loading and doesn't report errors or fail the import if there are issues with rows. Is this behavior configurable anywhere?Thanks,Brian
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/d3f97113-4989-4e8c-b755-de8960dd5419%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment