The Redshift connector, on running a query that returns no rows, will return a parsons Table with no rows but with all of the columns defined. The BigQuery connector instead returns None.
I like the Redshift connector behavior better - it's more useful to still have the columns named even if there are no rows, and makes using the output from the connector the same whether or not rows are returned, making downstream use easier without conditionals.
Environment name and version (e.g. Chrome 39, node.js 5.4):
Operating System and version (desktop or mobile):
Additional Context
Add any other context about the problem here.
Priority
Please indicate whether fixing this bug is high, medium, or low priority for you. If the issue is time-sensitive for you, please let us know when you need it addressed by.
medium
The Redshift connector, on running a query that returns no rows, will return a parsons Table with no rows but with all of the columns defined. The BigQuery connector instead returns None.
I like the Redshift connector behavior better - it's more useful to still have the columns named even if there are no rows, and makes using the output from the connector the same whether or not rows are returned, making downstream use easier without conditionals.
Detailed Description
To Reproduce
Your Environment
Additional Context
Add any other context about the problem here.
Priority
Please indicate whether fixing this bug is high, medium, or low priority for you. If the issue is time-sensitive for you, please let us know when you need it addressed by. medium