Skip to content

Conversation

@S-Saranya1
Copy link
Contributor

@S-Saranya1 S-Saranya1 commented Oct 22, 2025

Add business metrics tracking support for all flexible checksum algorithms and configurations.

   FLEXIBLE_CHECKSUMS_REQ_CRC32("U"),
   FLEXIBLE_CHECKSUMS_REQ_CRC32C("V"),
   FLEXIBLE_CHECKSUMS_REQ_CRC64("W"),
   FLEXIBLE_CHECKSUMS_REQ_SHA1("X"),
   FLEXIBLE_CHECKSUMS_REQ_SHA256("Y"),
   FLEXIBLE_CHECKSUMS_REQ_WHEN_SUPPORTED("Z"),
   FLEXIBLE_CHECKSUMS_REQ_WHEN_REQUIRED("a"),
   FLEXIBLE_CHECKSUMS_RES_WHEN_SUPPORTED("b"),
   FLEXIBLE_CHECKSUMS_RES_WHEN_REQUIRED("c")

Motivation and Context

This change implements business metrics tracking for flexible checksum operations. This enables to track the adoption of flexible checksum algorithms (CRC32, SHA256, etc.) and configurations (WHEN_SUPPORTED, WHEN_REQUIRED) for telemetry and usage analysis.

Modifications

  • Added flexible checksum business metric feature IDs to BusinessMetricFeatureId enum.
  • Modified HttpChecksumStage to add checksum business metrics when flexible checksum algorithms and configurations are used

Testing

Added FlexibleChecksumBusinessMetricTest functional tests to verify User-Agent header contains correct flexible checksum algorithm and configuration metrics.

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed
  • I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

@S-Saranya1 S-Saranya1 requested a review from a team as a code owner October 22, 2025 22:47
@S-Saranya1 S-Saranya1 added the no-api-surface-area-change Indicate there is no API surface area change and thus API surface area review is not required label Oct 24, 2025
@S-Saranya1 S-Saranya1 enabled auto-merge October 27, 2025 18:58
@sonarqubecloud
Copy link

@S-Saranya1 S-Saranya1 added this pull request to the merge queue Oct 27, 2025
Merged via the queue into master with commit 839bbaa Oct 27, 2025
39 checks passed
@github-actions
Copy link

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 27, 2025
@S-Saranya1 S-Saranya1 deleted the somepal/checksums-featureIDs branch October 27, 2025 22:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

no-api-surface-area-change Indicate there is no API surface area change and thus API surface area review is not required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants