Added a "LIMIT 1" clause to the fetch state query in BigQuery client

[xneg]

Description

Added a "LIMIT 1" clause to the fetch state query in BigQuery client since only the first record is used later in the code.

Related Issues

• Fixes Unstable behaviour while fetching the pipeline state from BigQuery #2315

[netlify]

✅ Deploy Preview for dlt-hub-docs canceled.

Name	Link
🔨 Latest commit	0bfc808
🔍 Latest deploy log	https://app.netlify.com/sites/dlt-hub-docs/deploys/67b36c063281590008195c78

[sh-rp]

I don't think this will work with all destinations, mssql has a different syntax for example.

[xneg]

@sh-rp ah, you are right, thank you! I have to think about different solution.

[xneg]

I couldn't think anything better than moving "LIMIT 1" clause to specific BigQuery client.

[sh-rp]

@xneg sorry for not responding in more detail earlier, it just occured to me that we already have a solution for this, albeit not a very elegant one. Check the _limit_clause_sql function that has a special implementation for mssql and how it is used in the datasets. You can just use that to achieve what you want with a 2 line code change. Let me know if you need help.

[sh-rp]

Additional thought: you might also want to apply this to get_stored_schema, the same problem could arise.

[xneg]

@sh-rp Thank you! It's good idea although a bit more than 2 lines of code. And thank you for hint with get_stored_schema, I applied changes there too.

[rudolfix]

@sh-rp ci from fork label does not work in this repo :/ we only have it implemented on verified sources. so to test it we would need to change our workflows...

[sh-rp]

@rudolfix I added ci from fork to our workflows a year ago or so and it is still there, but it does not work for some reason...