Hi, thank you for reaching out.
I can not reproduce exactly the issue you are reporting, but I confirm that I, too, can not query a mydb table in async mode right now (I'm getting a different error). We are looking to fix the issue right now.
Your query quoted above is in sync mode, but the output you quoted is the jobID that is returned when you launch an async query.
Until we fixed the querying of mydb tables in async mode, I'd like to suggest a few work-arounds:
- I f the table in your mydb was created by for instance a query to Data Lab's catalogs, and you want to download such a table, you could instead direct the output of the query to a file in your VOSpace, and then download from there. I.e. something like this:
qc.query('SELECT ... FROM ...',fmt='csv',out='vos://mytable001.csv')
- If you need to get it from your mydb, and your hsc_dr2 table can be split up, for instance in slices of RA, you could download it in pieces, for instance:
df1 = qc.query('SELECT * FROM mydb://hsc_dr2 WHERE RA>0 and RA<=90',timeout=600,fmt='pandas')
df2 = qc.query('SELECT * FROM mydb://hsc_dr2 WHERE RA>90 and RA<=180',timeout=600,fmt='pandas')
etc. Not ideal, but it could stay under 600 seconds for each RA slice.
We'll ping back here where the underlying issue has been fixed.
Thank you for reporting the problem, and for your patience.
Robert for the DL team