lokiore opened a new pull request, #11: URL: https://github.com/apache/phoenix-adapters/pull/11
## What Bump `<phoenix.version>` in `pom.xml` from **5.3.1 → 5.3.2**, now that Apache Phoenix 5.3.2 has been released and published to Maven Central. JIRA: [PHOENIX-7954](https://issues.apache.org/jira/browse/PHOENIX-7954) ## Changes - `pom.xml` (line 46): `<phoenix.version>5.3.1</phoenix.version>` → `<phoenix.version>5.3.2</phoenix.version>` All consumed Phoenix artifacts (`phoenix-core`, `phoenix-core-client`, `phoenix-core-server`, `phoenix-hbase-compat-2.5.4`) resolve at `${phoenix.version}` and are available at 5.3.2 on Maven Central. ## Verification Ran a full `mvn clean install` locally against Maven Central: - All modules (`phoenix-ddb-utils`, `phoenix-ddb-rest`, `phoenix-ddb-assembly`, `coverage-report`) compile and package cleanly against 5.3.2. - Unit + integration suites pass. _(One integration test, `GetRecordsIT.testGetRecordsWithPartitionSplits`, is a known ordering flake — it sorts two independent streams by DynamoDB's second-granularity `approximateCreationDateTime` and compares index-by-index, so tied timestamps can order differently between the streams. It is unrelated to this patch version bump.)_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
