1. Overview

This system automates the mapping of Tags to Jackpot Groups based on their Studio and Category. It replaces manual tagging with a configuration-driven approach, ensuring that whenever a group's metadata changes, its tags are synchronised automatically.

2. Database Schema Changes

Changes applied via Flyway migrations:

• jackpot_game_tag_conf: Reference table for Studio/Category/Tag mappings. (Unique Constraint on all three columns).
• jackpot_group_table: Added studio and category columns.

3. The "Mando" Logic (Automatic Sync)

When an operator updates a Jackpot Group's Studio or Category:

1. Lookup: BE queries jackpot_game_tag_conf for matching entries.
2. Atomic Transaction:
   • Existing tags for that group are deleted.
   • New matching tags are inserted.
3. Result: The group tags are always perfectly in sync with the master configuration.

4. Bulk Configuration API

To manage high volumes of data (up to 30k+ rows), use the bulk upload endpoint.

Endpoint Details

• URL: POST /api/v1/jackpot-tags/upload
• Auth: Bearer Token required.
• Format: Accepts .csv or .csv.gz (Gzip).
• Logic:
  • Dynamic Header Mapping: The system reads the first row to determine the position of category, studio, and tag columns. This allows the CSV columns to be in any order.
  • Duplicate Detection: The API identifies duplicates (by row number) and returns them in the response body.
  • Upsert Performance: Uses JdbcTemplate with ON CONFLICT DO NOTHING logic to handle large datasets rapidly without failing on existing records.

Testing Template (curl)