Question 1

Does TextQL handle BigQuery's nested and repeated fields?

Accepted Answer

Yes. TextQL fully supports BigQuery's STRUCT and ARRAY column types. When you ask a question involving nested data, Ana automatically generates the correct UNNEST operations and field path references. You don't need to know the schema structure — just ask your question and Ana handles the complexity.

Question 2

How does TextQL prevent expensive BigQuery queries?

Accepted Answer

TextQL estimates the bytes each query will scan before execution and compares it against configurable cost thresholds. If a query would exceed your limit, Ana suggests optimizations — like adding partition filters or narrowing date ranges. You can also set hard byte-scan limits per user or per workspace.

Question 3

Can TextQL access BigQuery datasets across multiple GCP projects?

Accepted Answer

Yes. As long as the service account or authenticated user has the necessary IAM permissions, TextQL can discover and query datasets across multiple GCP projects. Ana can even join tables from different projects in a single query, resolving the correct project references automatically.

Question 4

Does TextQL work with BigQuery partitioned tables?

Accepted Answer

Yes. TextQL detects partitioned and clustered tables and generates queries that leverage partition pruning for optimal performance and cost. When you specify time ranges in your question, Ana adds the appropriate partition filter to minimize bytes scanned and query cost.

Question 5

What permissions does the service account need?

Accepted Answer

The service account needs BigQuery Data Viewer and BigQuery Job User roles at minimum. Data Viewer grants read access to table data and metadata, while Job User allows query execution. For cost monitoring, BigQuery Resource Viewer is recommended. TextQL never requires write or admin permissions.