BigQuery Profiler Fails on Nested Columns with Case-Sensitive Names (Uppercases)

[aimendenche-nw]

Affected module BigQuery Profiler

Describe the bug When profiling a BigQuery table that contains a column named insertTime, the profiler completes with a success status, but no statistics are displayed in the OpenMetadata UI.

In the logs, we observe the following exception: metadata.ingestion.ometa.client.APIError: Invalid column name kafka_data.inserttime

To Reproduce

Use or create a BigQuery table that contains a column named insertTime (or any camelCase / mixed-case name).

Run the OpenMetadata profiler ingestion.

Check the UI: no profiling stats will appear.

Check logs for an error similar to: `metadata.ingestion.ometa.client.APIError: Invalid column name kafka_data.inserttime

Expected behavior Profiler should correctly handle and preserve case-sensitive column names (e.g., insertTime) and return profiling stats as expected in the UI.

Version:

• OS: [e.g. iOS]
• Python version:
• OpenMetadata version: 1.7.1
• OpenMetadata Ingestion package version: [e.g

Warehouse_profiler_r80UoWt6-profiler (2)(1).log

. openmetadata-ingestion[docker]==XYZ]

Additional context OpenMetadata support confirmed this is likely a case-sensitivity issue with nested columns and suggested opening a GitHub issue to track it