v0.0.28

Full Changelog: v0.0.27...v0.0.28

v0.0.27

What's Changed

• test: ensures lock doesn't affect the message removal by @cezar-tech in #42
• build(deps): bump golang.org/x/crypto from 0.5.0 to 0.17.0 by @dependabot in #46

New Contributors

• @cezar-tech made their first contribution in #42

Full Changelog: v0.0.26...v0.0.27

v0.0.26

What's Changed

• feat: allow dynamic ack deadline by @lucasoares in #41

Full Changelog: v0.0.25...v0.0.26

v0.0.25

What's Changed

• feat(helm): allow modify service annotations by @lucasoares in #40

Full Changelog: v0.0.24...v0.0.25

v0.0.24

What's Changed

• Apline security fixes, building with latest Alpine version.

Full Changelog: v0.0.23...v0.0.24

v0.0.23

What's Changed

• ci: release Java artifact to maven central by @lucasoares in #38

Full Changelog: v0.0.19...v0.0.23

v0.0.19

What's Changed

• build(deps): bump Grpc.Net.Client from 2.51.0 to 2.52.0 in /csharp by @dependabot in #36
• build(deps): bump grpc-protobuf from 1.52.1 to 1.53.0 in /java by @dependabot in #37

Full Changelog: v0.0.18...v0.0.19

v0.0.18

What's Changed

• feat(#24): diagnostic fields to track ACKs and NACKs by @lucasoares in #35

Detailed changes of #35

This release adds a new field called diagnostics to the message. It was created to provide diagnostic information about each message to the applications.

Example of Pull request of a message that was acked successfully three times in a row:

{
    "messages": [
        {
            "metadata": [],
            "payload": [],
            "id": "2",
            "description": "",
            "queue": "1",
            "string_payload": "",
            "score": 1688414529848,
            "breakpoint": "",
            "diagnostics": {
                "acks": "3",
                "nacks": "0",
                "consecutive_acks": "3",
                "consecutive_nacks": "0"
            }
        }
    ]
}

The diagnostics field contains the following fields:

• acks - to track the number of times the message was acknowledge since its creation
• nacks - to track the number of times the message was (not)acknowledge since its creation
• consecutive_acks - to track the number of times the message was acknowledge since the last NACK signal
• consecutive_nacks - to track the number of times the message was (not)acknowledge since the last ACK signal

Full Changelog: v0.0.17...v0.0.18

v0.0.17

What's Changed

• refactor: rename message_pool package to queue by @lucasoares in #28
• docs: add proto file documentation in markdown by @lucasoares in #31
  • Check it out!
• feat(#27): address ambiguity for score fields, allow assign the priority manually by @lucasoares in #29

Detailed changes of #29

• Allow users to assign priority while adding message
  • If the score is not set, the value will be set with the current timestamp in milliseconds at the moment of the message creation.
  • Negative scores will be converted to 0, adding the message with the lowest score (and highest priority)
• Add max_score and min_score score filtering for Pull requests
  • score_filter is now deprecated and should not be used. Prefer using max_score now but remember that it behaves differently: The max_score field is the upper threshold itself, but the score_filter will result in an upper score threshold of the current timestamp minus the score_filter value.
  • max_score: Sets the upper threshold for the priority score of a message to be returned in the pull request.
    • Only messages with a priority score equal to or lower than the max_score value will be returned.
    • The maximum score accepted by Deckard is 9007199254740992, any value higher than this will be capped to the maximum score.
    • To set this value to the minimum score accepted by Deckard, use any negative number.
    • This parameter will be ignored if set to 0 (default value) and the Pull request will not have an upper threshold for filtering scores (the upper threshold will be the maximum score).
  • min_score: Sets the lower threshold for the priority score required for a message to be returned.
  • Only messages with a priority score equal to or higher than the min_score value will be returned.
  • The minimum score accepted by Deckard is 0 which is also the default value
• Allow users manually set the score field on Ack requests
  • If used at the same time with the 'lock_ms' attribute, the message will be locked for the specified time and then returned to the queue with the specified score.
  • For ACK requests, if the score is not provided (or set to 0), the message will return to the queue with the default score algorithm which is the current timestamp in milliseconds.
  • For NACKs requests, if the score is not provided (or set to 0), the message will return to the queue with the minimum score accepted by Deckard which is 0.
  • Negative values will be converted to 0, which is how to set the highest priority to a message in an ACK/NACK request.

Full Changelog: v0.0.16...v0.0.17

v0.0.16

What's Changed

• fix: helm chart storage and cache uri for non standalone is now working by @lucasoares in #23
• docs: added exposed metrics documentation @lucasoares in #23

Full Changelog: v0.0.15...v0.0.16