@rasmusengelbrecht/pi-semantic-query 0.1.2 → 0.1.3

package/README.md

@@ -85,6 +85,23 @@ Example request shape for `semantic_compile`:
 }
 ```
 
+For target series, pass `targetTable`. Use `targetProject` and `targetSchema` when the warehouse needs a qualified target relation but you want to keep the table name generic:
+
+```json
+{
+  "metricId": "revenue",
+  "period": "current year",
+  "dialect": "bigquery",
+  "targetProject": "warehouse-project",
+  "targetSchema": "analytics",
+  "targetTable": "metric_targets",
+  "request": {
+    "timeGrain": "monthly",
+    "targetSeries": "budget_current"
+  }
+}
+```
+
 ## Safety boundary
 
 This package is compile-only by design. `semantic_compile` returns SQL; it does not run the SQL. Query execution touches credentials, cost, and data access, so execution should stay in the caller's existing warehouse tooling or a separate explicitly configured integration.

package/extensions/semantic-query.ts

@@ -65,7 +65,9 @@ const CompileParams = Type.Intersect([
       Type.Literal("json"),
       Type.Literal("explain"),
     ], { description: "Output format. Defaults to sql." })),
-    targetTable: Type.Optional(Type.String({ description: "Optional target table for targetSeries requests." })),
+    targetTable: Type.Optional(Type.String({ description: "Optional target table for targetSeries requests. May be fully qualified, or bare when targetProject/targetSchema are supplied." })),
+    targetProject: Type.Optional(Type.String({ description: "Optional target table project/catalog." })),
+    targetSchema: Type.Optional(Type.String({ description: "Optional target table schema/dataset." })),
     targetMetricColumn: Type.Optional(Type.String({ description: "Target metric id column. Defaults to metric_id." })),
     targetSeriesColumn: Type.Optional(Type.String({ description: "Target series column. Defaults to target_series." })),
     targetTimeColumn: Type.Optional(Type.String({ description: "Target time column. Defaults to metric_time." })),
@@ -249,6 +251,8 @@ export default function semanticQueryExtension(pi: ExtensionAPI) {
         if (params.dialect) args.push("--dialect", params.dialect);
         if (params.format) args.push("--format", params.format);
         if (params.targetTable) args.push("--target-table", params.targetTable);
+        if (params.targetProject) args.push("--target-project", params.targetProject);
+        if (params.targetSchema) args.push("--target-schema", params.targetSchema);
         if (params.targetMetricColumn) args.push("--target-metric-column", params.targetMetricColumn);
         if (params.targetSeriesColumn) args.push("--target-series-column", params.targetSeriesColumn);
         if (params.targetTimeColumn) args.push("--target-time-column", params.targetTimeColumn);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rasmusengelbrecht/pi-semantic-query",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Compile and inspect governed semantic metrics from pi coding agent",
   "keywords": [
     "pi-package",

package/skills/semantic-query/SKILL.md

@@ -32,6 +32,23 @@ Prefer period-based requests for CLI/agent workflows:
 }
 ```
 
+For target series, pass `targetTable`. If the warehouse needs qualified table names, prefer generic relation parts instead of hard-coded company presets:
+
+```json
+{
+  "metricId": "revenue",
+  "period": "current year",
+  "dialect": "bigquery",
+  "targetProject": "warehouse-project",
+  "targetSchema": "analytics",
+  "targetTable": "metric_targets",
+  "request": {
+    "timeGrain": "monthly",
+    "targetSeries": "budget_current"
+  }
+}
+```
+
 Use raw `fromDate` / `toDate` only when the user needs exact fixed boundaries or provides a request JSON shape that already has them.
 
 ## Safety boundary