Due to a common pattern in GCP in which customers use one project for billing and other projects for data, the Fabric Factory Copy Activity Destination tab does not expose enough properties to permit successful writes. The UI currently only exposes dataset-id and table name entered manually. For proper billing, the Fabric Connection is setup to use the GCP billing project. Due to the fact that the UI does not permit setting of the data project to define the fully-qualified name of the target write table, at runtime, the target write table becomes {billing project}.{dataset}.{table}. The billing project intentionally contains no tables at all and is strictly for purposes of allocating egress costs correctly. Extending the Fabric Factory Copy Activity Destination tab by adding the project context for the write would allow Fabric Copy Activity to align with the common pattern of usage in GCP. An alternative that might be considered would be to make the Billing Project Id, and Project Id in the Fabric Connector for BigQuery actually permit runtime override of the project default. Were this change made then the Copy Activity UI change would be unnecessary.
No CommentsBe the first to comment
