AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Migrate Aggregate To Struct

skill-mondaycom-duckdb-claude-migrate-aggregate-to-struct · by mondaycom

Migrate a DuckDB aggregate function from opaque EXPORT_STATE to struct-based EXPORT_STATE using SetStructStateExport

No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-mondaycom-duckdb-claude-migrate-aggregate-to-struct

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-mondaycom-duckdb-claude-migrate-aggregate-to-struct)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Migrate Aggregate To Struct? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Migrate Aggregate Function to Struct-Based State Export

Migrate the $ARGUMENTS aggregate function from legacy opaque (binary blob) EXPORT_STATE to the new struct-based format using SetStructStateExport.

Step 1: Locate the implementation

Find the aggregate function's source file. Common locations:

  • extension/core_functions/aggregate/distributive/ (bit aggregates, bool, approx_count, kurtosis, skew)
  • extension/core_functions/aggregate/algebraic/ (avg, stddev, corr, covar)
  • extension/core_functions/aggregate/regression/ (regr_*)
  • src/function/aggregate/distributive/ (count, first/last, min/max)

Read the full implementation file.

Step 2: Verify eligibility

Check against the requirements in src/function/scalar/system/aggregate_export.cpp (the ExportAggregateFunction::Bind method). A function CANNOT use EXPORT_STATE if it has:

  • A custom binder (HasBindCallback()) - e.g. argmin/argmax
  • A destructor (HasStateDestructorCallback()) - e.g. string_agg, list, BIT-type variants using UnaryAggregateDestructor
  • No combine callback

If the function has multiple overloads (e.g. one for integral types, one for BIT type with a destructor), only the eligible overloads can get SetStructStateExport. Skip the overload with a destructor.

Stop and inform the user if the function is not eligible.

Step 3: Identify the state struct

Find the C++ struct that holds the aggregate state. Note the exact field order and types as declared — the LogicalType struct fields MUST match the C++ memory layout. For reference, read already-migrated examples in [examples/](examples/).

Step 4: Create the GetExportStateType callback

Add a function that maps the C++ state struct to a LogicalType::STRUCT. Place it in the same .cpp file, inside the anonymous namespace if one exists, before the function registration.

Use the type mapping from [reference.md](reference.md) to convert C++ types to LogicalTypes.

If the state struct is templated and the concrete type depends on the input, use function.return_type or the appropriate argument type dynamically:

LogicalType GetMyStateType(const AggregateFunction &function) {
    child_list_t children;
    children.emplace_back("is_set", LogicalType::BOOLEAN);
    children.emplace_back("value", function.return_type);
    return LogicalType::STRUCT(std::move(children));
}

For nested struct states, create nested LogicalType::STRUCT values — see the corr example in [examples/](examples/).

Step 5: Wire up SetStructStateExport

Chain .SetStructStateExport(YourCallback) onto each eligible AggregateFunction in the registration function (GetFunction() or GetFunctions()).

For function sets with multiple overloads, add it to each eligible overload individually. Do NOT add it to overloads that have destructors or bind callbacks.

Step 6: Add tests to teststateexport_struct.test

Add the function to test/sql/aggregate/aggregates/test_state_export_struct.test. Follow the existing patterns:

  1. Add to ungrouped aggregate queries (res0 nosort group) — both the plain query and the finalize(...EXPORT_STATE) query
  2. Add to grouped aggregate queries (res1 nosort group) — with GROUP BY g ORDER BY g
  3. Add to the persisted state table (CREATE TABLE state AS ...) and corresponding finalize() query
  4. Add to empty group tests (res4), null-scanned tests (res5, res6)

Update the query type strings to reflect the new column count.

Step 7: Add an EXPORT_STATE validation test

Verify the exported state values are correct by selecting the EXPORT_STATE result directly (without casting):

query T
SELECT your_func(42) EXPORT_STATE;
----
{'field1': value1, 'field2': value2}

Run the query first to get the actual output, then use that as the expected result.

Step 8: Remove from opaque tests (if applicable)

If the function was tested in test/sql/aggregate/aggregates/test_state_export_opaque.test, remove it from there. The opaque test file should only contain functions that have NOT been migrated.

Step 9: Build and run tests

cd build/debug && ninja -j8
./test/unittest "test/sql/aggregate/aggregates/test_state_export_struct.test"

Checklist

  • [ ] GetExportStateType field order matches C++ struct declaration order
  • [ ] LogicalTypes match the C++ types exactly (see [reference.md](reference.md))
  • [ ] SetStructStateExport chained on ALL eligible overloads (skip overloads with destructors/binders)
  • [ ] Tests added to teststateexport_struct.test
  • [ ] Tests removed from teststateexport_opaque.test (if applicable)
  • [ ] Build succeeds and tests pass

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.