mammoth-cli 2.0.51__tar.gz → 2.0.52__tar.gz

{mammoth_cli-2.0.51 → mammoth_cli-2.0.52}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.51
+Version: 2.0.52
 Summary: Command-line interface for the Mammoth Analytics platform
 Project-URL: homepage, https://mammoth.io
 Project-URL: repository, https://github.com/EdgeMetric/mammothsdk

{mammoth_cli-2.0.51 → mammoth_cli-2.0.52}/mammoth_cli/__init__.py

@@ -6,7 +6,7 @@ not implement a second HTTP client and does not call private SDK members.
 
 from __future__ import annotations
 
-__version__ = "2.0.51"
+__version__ = "2.0.52"
 
 # The versioned machine output envelope contract.
 SCHEMA_VERSION = 1

{mammoth_cli-2.0.51 → mammoth_cli-2.0.52}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mammoth-cli
-version: 2.0.51
+version: 2.0.52
 description: "Use Mammoth Analytics from a terminal: install or authenticate the CLI, discover its live command contract, and safely manage projects, data, views, pipelines (join, merge, pivot, filter, clean), dashboards, exports, and handoffs."
 ---
 

{mammoth_cli-2.0.51 → mammoth_cli-2.0.52}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/transforms.md

@@ -52,6 +52,21 @@ only signal is the task's own `transform_status` (`view task get`/`view task
 list` always read it at full detail). `DONE` means the step actually
 produced output; `ERROR` or `REFERROR` means it did not, even though the
 mutation "succeeded".
+- `split` makes new columns and `unnest` turns columns into label/value
+  rows; neither gives one row per delimited value. For one row per value,
+  use `add-sql` over `"view:VIEW_ID"`, selecting the other columns plus
+  `TRIM(UNNEST(string_split(COALESCE(tags, ''), ','))) AS tag`. Keep every
+  row -- a blank or NULL value stays as one row with an empty tag, and
+  `COALESCE` is what keeps the NULL rows, since DuckDB's `UNNEST` of NULL
+  yields zero rows (verified: drop the `COALESCE` and a NULL row vanishes).
+  Never add a `WHERE` that drops rows the user did not ask to drop. Verify
+  by row count: the result should equal the sum of each row's value count,
+  with a blank or NULL counting as 1.
+
+```bash
+mammoth view transform add-sql VIEW_ID --project PROJECT_ID \
+  --input '{"dataset_id":DATASET_ID,"query":"SELECT event_id, user_id, event_time, payload, TRIM(UNNEST(string_split(COALESCE(tags, '\'''\''), '\'','\''))) AS tag FROM \"view:VIEW_ID\""}'
+```
 
 These examples use the released route IDs and input shapes documented by the
 command manifest; substitute only observed view IDs and display names:

{mammoth_cli-2.0.51 → mammoth_cli-2.0.52}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mammoth-cli"
-version = "2.0.51"
+version = "2.0.52"
 description = "Command-line interface for the Mammoth Analytics platform"
 authors = [{name = "Mammoth Analytics", email = "support@mammoth.io"}]
 readme = "README.md"

{mammoth_cli-2.0.51 → mammoth_cli-2.0.52}/spec/manifests/commands/view.yaml

@@ -2474,8 +2474,9 @@ commands:
   - CT-VIEW-EXPORT-POWERBI-ERROR
   draft_test: null
   undo_test: null
-  known_restrictions: The handler enum and helper exist, but the pure contract omits it; confirm camel-case
-    clientId against the pinned server before enabling. See IO-EXPORT-HANDLERS blocker.
+  known_restrictions: Needs the Power BI account username and password, the Azure AD app's client_id, and
+    the target Power BI dataset and table; the password is a secret field, so pass it in the request file,
+    never in argv.
   reviewed_by: primary
 - command_id: view.export.publish-db
   command_path: view export publish-db

{mammoth_cli-2.0.51 → mammoth_cli-2.0.52}/spec/manifests/sdk-catalog.source.yaml

@@ -4185,8 +4185,9 @@ sdk_methods:
   wait_policy: returns_job
   pagination_policy: null
   openapi_operation_ids: []
-  notes: The handler enum and helper exist, but the pure contract omits it; confirm camel-case clientId
-    against the pinned server before enabling. See IO-EXPORT-HANDLERS blocker.
+  notes: Needs the Power BI account username and password, the Azure AD app's client_id, and the target
+    Power BI dataset and table; the password is a secret field, so pass it in the request file, never in
+    argv.
 - sdk_symbol: mammoth.view.ViewExport.to_redshift
   canonical_command: view.export.redshift
   alias_of: null
@@ -4281,10 +4282,8 @@ notes_on_dispositions:
   a reviewed typed fixture." No SDK method backs this handler.'
 - 'email export handler: "Outbound email stays contract-only until a dedicated sink and recipient allowlist
   exist" (acceptance class contract_only_high_impact).'
-- 'powerbi export handler: "The handler enum and helper exist, but the pure contract omits it. Confirm
-  camel-case clientId against the pinned server before enabling."'
-- 'IO-EXPORT-HANDLERS blocker: "csv_file, powerbi, and any server-rejected handler ... never infer support
-  from the enum."'
+- 'IO-EXPORT-HANDLERS blocker: "csv_file and any server-rejected handler ... never infer support from the
+  enum."'
 - 'B04 SERVER_VARIANCE (doc 09): "project browse and dashboard sources are documented as returning HTTP
   500 on some servers; schedule list may return 405. A permission or 5xx response is not server_unavailable;
   retain the live exemption evidence."'