Takafumi Hirata

Hi there I am not familiar with pyspark or spark-bigquery-connector, but I understand that the bigquery-emulator does not request permissions or provide authentication features. Therefore, it seems unlikely that this...

Thank you for the detailed report. I have confirmed that there are indeed differences in output compared to BigQuery, and also outputs vary between values within a structure and those...

@ohaibbq Thank you for your response. As I haven’t started working on it yet, I would be grateful if you could address this issue.

@kurrenda Passing Float64 to UNNEST seems odd, is this intended? The error is not due to Float64, but because you are passing parameters to UNNEST in FROM clause. Currently, you...

I Understood. Indeed, that aspect is not compatible with BigQuery. In the case of the emulator, not limited to float but also int, passing them as query parameters in their...

I see, you were using the Python SDK. Understood, thank you very much for clarifying. I also understood the point you made about how, even if numerical values are written...

The information provided is insufficient to reproduce the issue. Please include a code snippet or any relevant details that can actually reproduce the issue you are experiencing. This will help...

Thank you for your report. To better understand and address the issue, could you please provide detailed steps to reproduce it, or executable code if possible?

Thank you. I have confirmed that this has been fixed since version 0.6.0, so I will close this issue.

This issue appears difficult to fix given the current design, so it might be better to temporarily use an alternative method or a workaround. As a workaround, you can use...