VoltDB Development

This skill creates complete VoltDB client applications with optimized partitioning. It generates Maven project scaffolding, analyzes data models for partitioning strategy, creates DDL schemas and stored procedures, and produces integration tests with testcontainer support.

Rules

Rules are organized in the rules/ directory. Read only the rule files needed for the current phase — do NOT read all rules upfront.

Priority	Category	Impact	Rule Files
1	Partitioning Strategy	HIGH	rules/part-critical-rules.md, rules/part-choose-column.md, rules/part-colocation.md, rules/part-lookup-tables.md
2	DDL & Stored Procedures	HIGH	rules/ddl-procedures.md
3	Project Setup	MEDIUM	rules/proj-setup.md
4	Integration Testing	MEDIUM	rules/test-base-class.md, rules/test-data-and-patterns.md
5	Workflow & Templates	MEDIUM	rules/workflow-readme-template.md

Workflow

Use the AskUserQuestion tool for each question. This provides clickable options for the user.

Step 1: Verify Docker is Running (silent — no user prompt on success)

Run a single silent check. If Docker is running, proceed directly to Step 2 without any output.

docker info > /dev/null 2>&1 && echo "OK" || echo "FAIL"

• Docker not running: Use AskUserQuestion:
  • question: "Docker is required but not running. Please start Docker and let me know when it's ready."
  • header: "Docker"
  • options:
    • Docker is running now - I've started Docker
    • Help me start Docker - Show me how to start it
  • If user selects "Help me start Docker": macOS: open -a Docker / Linux: sudo systemctl start docker
  • Re-verify with docker info before proceeding.

Java and Maven are not checked upfront — missing or wrong versions produce clear errors at build time (Step 7).

Step 2: Ask License Location

VoltDB Enterprise requires a license file. Use AskUserQuestion with:

• question: "Where is your VoltDB Enterprise license file?"
• header: "License"
• options:
  • VOLTDB_LICENSE env var (Recommended) - I have VOLTDB_LICENSE environment variable set
  • /tmp/voltdb-license.xml - License is at the default location
  • Specify path - I'll provide the path to my license file

After the user responds:

1. If VOLTDB_LICENSE env var: run echo $VOLTDB_LICENSE and verify the file exists at that path using test -f "$VOLTDB_LICENSE".
2. If /tmp/voltdb-license.xml: verify the file exists using test -f /tmp/voltdb-license.xml.
3. If Specify path: ask the user for the path, then verify the file exists.

If the license file is not found at the specified location, inform the user and ask them to correct the path. Do not proceed until a valid license file is confirmed.

Save the confirmed license path — it will be used when generating test.properties.

Step 3: Ask Application Name

Use AskUserQuestion with:

• question: "What should the application be called?"
• header: "App name"
• options:
  • my-voltdb-app (Recommended)
  • voltdb-client
  • data-service

User can select an option or type their own.

Step 4: Ask Output Directory

Use AskUserQuestion with:

• question: "Where should I create the project?"
• header: "Directory"
• options:
  • Current directory (Recommended)
  • Specify path - I'll provide a path

Step 5: Ask Data Model

Use AskUserQuestion with:

• question: "What type of data model do you need?"
• header: "Data model"
• options:
  • Describe custom tables - I'll describe my tables and columns
  • Use example model - Customer/Orders/Product example
  • Key-Value store - Simple key-value table (no partitioning analysis needed)

If user selects "Describe custom tables", ask them to describe their tables in a follow-up message.

Step 6: Analyze and Generate

Phase 1 — Partitioning Analysis (skip for Key-Value):

1. Read rules/part-critical-rules.md and rules/part-choose-column.md
2. If co-location is needed, read rules/part-colocation.md
3. If cross-domain queries exist, read rules/part-lookup-tables.md
4. Recommend partition column, co-location groups, lookup tables, and procedure types
5. Present strategy for user confirmation using AskUserQuestion:
   • question: "Does this partitioning strategy work for you? [strategy summary]"
   • header: "Strategy"
   • options:
     • Yes, proceed (Recommended)
     • Modify strategy - I want to change something
     • Explain more - Tell me more about the trade-offs

Phase 2 — Code Generation:

1. Read rules/proj-setup.md → create Maven project structure + pom.xml
2. Read rules/ddl-procedures.md → generate:
   • src/main/resources/ddl.sql (with DROP PROCEDURE IF EXISTS pattern)
   • src/main/resources/remove_db.sql (DROP in dependency order)
   • Stored procedures under src/main/java/[package]/procedures/
3. Generate [AppName]App.java — main client app (rules/proj-setup.md template)
4. Generate VoltDBSetup.java — schema deployment (rules/proj-setup.md template)
5. Generate CsvDataLoader.java — CSV loading utility (rules/test-data-and-patterns.md template)
6. Generate CSV data files in src/main/resources/data/ (rules/test-data-and-patterns.md)
7. Read rules/test-base-class.md → generate IntegrationTestBase.java
8. Read rules/test-data-and-patterns.md → generate [TestName]IT.java
9. Generate test.properties at src/test/resources/test.properties with testcontainer mode, shutdown enabled, and the confirmed license path from Step 2
10. Read rules/workflow-readme-template.md → generate project README.md

Auto-derived defaults (no questions asked):

• Package name: com.example.voltdb
• VoltDB connection mode: testcontainer
• Testcontainer shutdown: yes

Step 7: Build and Test

After generating the project, automatically build and test:

cd <project-name> && mvn clean package -DskipTests && mvn verify

If the build fails, diagnose the error and fix it. If it succeeds, report the results to the user.