venkatamandavilli-code commented on issue #40131: URL: https://github.com/apache/superset/issues/40131#issuecomment-4471296669
Thanks for reporting this issue. The problem description makes sense, especially for cross-project BigQuery environments where fully qualified dataset references are required. It looks like the current implementation may assume a two-part table reference (`dataset.table`) instead of handling the full three-part structure (`project.dataset.table`). In multi-project deployments, that can easily lead to lookup failures or 404 responses when metadata APIs attempt to resolve partition information. It may help to validate: * how table identifiers are parsed before calling `get_time_partition_column` * whether the connector consistently preserves project-level context during metadata resolution * whether quoted identifiers or custom schemas behave differently across environments A regression test covering cross-project dataset references would probably help prevent similar issues in future BigQuery connector updates. Thanks again for documenting the issue clearly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
