Validate Table Edm.Int64 writes and preserve legacy reads

[Akanksha Jain (jainakanksha-msft)]

Summary

Azure Table Storage accepts only signed 64-bit values for Edm.Int64, but Azurite previously accepted any string, including ulong.MaxValue. This allowed local writes that later failed against Azure with 400 InvalidInput.

This change:

• validates Edm.Int64 as a decimal integer within the signed 64-bit range on insert, update, and merge paths
• uses BigInt for exact boundary checks without changing the persisted string representation
• returns Azure-compatible 400 InvalidInput responses for underflow, overflow, and ulong.MaxValue
• preserves GET and collection-query access to out-of-range values persisted by earlier Azurite versions
• documents the behavior change in the upcoming Table release notes

Fixes #2558

Compatibility and test coverage

• unit coverage for signed boundaries, values beyond JavaScript's safe-integer range, malformed values, underflow, overflow, and ulong.MaxValue
• insert and upsert REST coverage for 400 InvalidInput
• handler-level legacy metadata coverage through both single-entity and collection-query REST paths
• Table PR checks pass across Ubuntu, Windows, and macOS on Node.js 22, 24, and 26

Validation

npx mocha --require ts-node/register --no-timeouts --exit tests/table/unit/serialization.unit.test.ts
NODE_TLS_REJECT_UNAUTHORIZED=0 npx mocha --require ts-node/register --no-timeouts --grep "signed Edm.Int64 range|legacy out-of-range Edm.Int64" --exit tests/table/apis/table.validation.rest.test.ts
npm run lint
npm run build

CI note

The linked upgrade compatibility run ran against main at unrelated commit 25c459a, not this PR's head. Its Table upgrade compatibility tests passed on Ubuntu and Windows. The run failed because the VSIX job timed out connecting to the Marketplace while resolving the published version (ETIMEDOUT/ENETUNREACH), and the Windows Blob upgrade setup exceeded its 600-second hook timeout. These failures are unrelated to the Table changes in this PR.

[Copilot]

Copilot review overview

🟡 Changes recommended

Address legacy persisted-value compatibility and add the required changelog entry.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1 · 1

Open (2)

• Prevent read-path failures for legacy out-of-range Edm.Int64 data · New
• Add changelog entry for rejecting out-of-range Edm.Int64 values · New

What changed in this PR

Fixes Table Edm.Int64 validation using exact signed 64-bit range checks.

Changes:

• Added BigInt boundary validation while preserving string serialization.
• Added unit and REST coverage for valid, invalid, and overflow values.
• Reports Azure-compatible 400 InvalidInput behavior.

File	Summary
tests/​table/​unit/​EdmInt64.unit.test.ts	Tests boundaries, overflow, underflow, and invalid formats.
tests/​table/​apis/​table.entity.int64.rest.test.ts	Verifies REST validation responses.
src/​table/​entity/​EdmInt64.ts	Implements signed 64-bit range validation.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Copilot review overview

🔵 Needs a closer look

Unresolved validation, legacy-read, serialization-coverage, and release-note issues remain.

Review effort: Lite
Findings: 1 · 1

Open (2)

• Prevent read-path failures for legacy out-of-range Edm.Int64 data
• Add changelog entry for rejecting out-of-range Edm.Int64 values

[Copilot]

Copilot review overview

🟡 Changes recommended

Legacy-read compatibility, REST error-path coverage, and the required changelog entry remain unresolved.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 2 · 1

Open (3)

• Missing insert/upsert regression tests for Int64 bounds · New
• Prevent read-path failures for legacy out-of-range Edm.Int64 data
• Add changelog entry for rejecting out-of-range Edm.Int64 values

[Copilot]

Copilot review overview

🔵 Needs a closer look

Legacy-read compatibility, changelog coverage, and the documented test command remain unresolved.

Review effort: Lite
Findings: 2 · 1

Open (3)

• Missing insert/upsert regression tests for Int64 bounds
• Prevent read-path failures for legacy out-of-range Edm.Int64 data
• Add changelog entry for rejecting out-of-range Edm.Int64 values

[Copilot]

Copilot review overview

🟡 Changes recommended

Add handler-level read-path regression coverage and correct the documented targeted test command.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1 · 1

Open (2)

• Add handler-level regression coverage for legacy Int64 compatibility · New
• Update documented validation command to use actual test paths · New

Resolved since last review (3)

• Missing insert/upsert regression tests for Int64 bounds
• Prevent read-path failures for legacy out-of-range Edm.Int64 data
• Add changelog entry for rejecting out-of-range Edm.Int64 values

[Copilot]

Copilot review overview

🟢 Approval recommended

No unresolved blocking issues were identified.

Review effort: Lite
Findings: None

Resolved since last review (2)

• Add handler-level regression coverage for legacy Int64 compatibility
• Update documented validation command to use actual test paths