[Sylvie-P]

HCK-18331 [BBVA][Couchbase7+] Add maxTTL to collections in the CouchbaseV7Plus plugin

## Content

Jira: HCK-18331 (parent HCK-18316)

Collections get a new Max TTL property (seconds), as described in the CREATE COLLECTION docs (WITH clause, Couchbase Server 7.6+, Enterprise Edition).

• Properties Pane: maxTTL numeric property on the collection, min value -1. Always visible; the tooltip says it needs 7.6+ and Enterprise Edition. No filtering by version or edition: if the server does not support the value, it rejects the statement.
• Forward-engineering: CREATE COLLECTION ... [IF NOT EXISTS] WITH {"maxTTL": n} when the value is an integer different from 0. Empty or 0 (inherit from bucket) gives no WITH clause, so existing models generate the same script as before.
• Alter script: created and renamed collections (drop + create) keep their maxTTL.
• Reverse-engineering from an instance: reads maxExpiry of each collection from getAllScopes(), once per bucket. 0 is not kept in the model.

Out of scope:

• Reverse-engineering from a N1QL file with a WITH clause (the ANTLR grammar does not support it yet).
• Changing the maxTTL of an existing collection in the alter script: SQL++ has no ALTER COLLECTION, so nothing is generated (open question in the ticket).

Technical details

• getCollectionScript gets a maxTTL param, the clause is built in getMaxTTLClause.
• New clusterHelper.getCollectionsMaxExpiryMap and schemaHelper.addMaxTTLToDbCollectionData. If getAllScopes() fails, the error is logged and RE continues without maxTTL.
• No test runner in this repo. Checked with a local Node smoke test (empty, 0, 3600, -1, 1.5, with and without IF NOT EXISTS, alter script for an added collection), oxlint (no new error), Prettier and npm run package.
• Studio feature tests for CouchbaseV7Plus (FE script, alter script, RE on a 7.1.1 Docker instance) should stay green since models without maxTTL are unchanged. Studio tests covering maxTTL will come in a second PR, after this plugin is published.
• To check manually: RE on a 7.6 Enterprise instance, especially that the bundled SDK returns -1 for "never expire".

Made with Cursor

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud