Skip to content

Fix/idempotency key storage width - #6404

Closed
mcc0nnell wants to merge 3 commits into
apache:developfrom
mcc0nnell:fix/idempotency-key-storage-width
Closed

mcc0nnell wants to merge 3 commits into
apache:developfrom
mcc0nnell:fix/idempotency-key-storage-width

Conversation

@mcc0nnell

@mcc0nnell mcc0nnell commented Sep 6, 2026 •

Copy link
Copy Markdown

Fineract currently has inconsistent storage limits for idempotency keys across its command-processing paths.

The legacy m_portfolio_command_source.idempotency_key column and CommandSource JPA mapping are limited to 50 characters, while the newer JDBC command store uses VARCHAR(255).

The HTTP idempotency layer does not impose the legacy 50-character limit before command processing, so the effective storage constraint can differ depending on the command-storage path.

Proposed change:

  • widen m_portfolio_command_source.idempotency_key to VARCHAR(255)
  • update the CommandSource JPA mapping to match
  • preserve existing idempotency behavior and existing keys

This is separate from FINERACT-2485 / PR #6231, which concerns idempotency semantics and concurrency behavior in the newer command-processing path.

@mcc0nnell mcc0nnell closed this Sep 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant