[littlegrasscao]

Summary

• add GET {prefix}/shares/{share}/schemas/{schema}/tables/{table}/changes (Read Change Data Feed) to OpenSharingProtocolService, following the OSS server's queryCDF and DeltaSharingCDCReader
  • the start comes from startingVersion or startingTimestamp (first version at or after it); the end from endingVersion or endingTimestamp (last version at or before it), or the latest version. Versions take precedence over timestamps, and an end after the latest version is capped
  • a commit with cdc files returns only those; otherwise it returns add and remove files with dataChange=true. MERGE commits whose metrics report no inserted, updated, or deleted rows return no files
  • the Change Data Feed must be enabled at the start, and metadata that disables it within the range returns 400
  • protocol and metaData come from the start version with includeHistoricalMetadata=true, which also returns later metaData with their version; otherwise they come from the latest version. Delta-Table-Version is the start version
  • includeHistoricalProtocol=true adds later protocols to delta responses, as for startingVersion queries in protocol: Query Table startingVersion, endingVersion, and historical protocol #114
  • parquet responses use add, cdf, and remove lines; delta responses wrap them in file.deltaSingleAction as add, cdc, and remove
  • fileidhash, includeendstreamaction, url access checks, and reader feature checks behave as in Query Table
• request validation lives in ProtocolTables.changes, with the parameters in TableChangesRequest
• startingVersion Query Table and the Change Data Feed now share one per-commit reader

Testing

• mvn clean install: 235 tests passed
• DeltaTableQueryReaderTest: a local CDF-enabled Delta log (insert, update with cdc files, delete without cdc, no-op MERGE, CDF disabled) checks that cdc files win, no-op MERGEs are skipped, parquet and delta lines are correct, timestamps resolve to versions, header metaData follows includeHistoricalMetadata, and a missing start, an end before the start, a start after the latest, and ranges without the Change Data Feed are rejected; the existing startingVersion tests still pass
• ProtocolTableChangesTest: on a local Delta log without a Change Data Feed, /changes returns 400 INVALID_PARAMETER_VALUE; a missing start, a malformed timestamp, or a malformed version returns 400, and an ungranted share returns 404
• ProtocolTableChangesIntegrationTest: the S3 CDF test table returns change files in both formats, rejects a range through the version that disables the Change Data Feed, caps an end after the latest version, and rejects an end before the start; table1 on S3, Azure, and GCS rejects the Change Data Feed. Each case is skipped without credentials

Stacked on #114.