Version 3.7.3 of Eclipse Ditto, released on 11.04.2025
Edit this page

This is a bugfix release, no new features since 3.7.2 were added.

Changelog

Compared to the latest release 3.7.2, the following changes and bugfixes were added.

Bugfixes

This is a complete list of the merged pull requests.

Aggregation metrics support exists(/path/to/field) RQL operator

PR #2155 fixes that aggregation metrics didn’t support the exists() RQL operator.

We apologize for the breaking change, but it was necessary to adjust in order to fix bug #2154.

custom-aggregation-metrics {
    online_status {
        namespaces = []
        filters {
            online_filter {
                filter = "gt(features/ConnectionStatus/properties/status/readyUntil,time:now)"
                inline-placeholder-values  {
                    "health" = "good"
                }
            }
            offline_filter {
                filter = "lt(features/ConnectionStatus/properties/status/readyUntil,time:now)"
                inline-placeholder-values = {
                    "health" = "bad"
                }
            }
        }
        group-by {...}
        tags {
            "health" = "{{ inline:health }}"
        }
        
    }
}

becomes (has to be migrated to):

custom-aggregation-metrics {
    online {
        namespaces = []
        filter = "gt(features/ConnectionStatus/properties/status/readyUntil/,time:now)"
        group-by {}
        tags {
            "health" = "good"
        }
    }
    offline {
        namespaces = []
        filter = "lt(features/ConnectionStatus/properties/status/readyUntil/,time:now)"
        group-by {}
        tags {
            "health" = "bad"
        }
    }
}

Fix WoT based validation rejecting message API calls if content-type was not application/json

When the configuration log-warning-instead-of-failing-api-calls was enabled to not fail API calls after failed WoT model validation, but only log a warning message, the API calls were still rejected if the content type was not application/json.
This was fixed in PR #2157.

Stabilize pre-defined extraFields enrichment, treating occurring exceptions by not pre-enriching

PR #2158 stabilizes the pre-defined extraFields enrichment which was added in Ditto 3.7. It could happen that - even if the pre-defined extraFields enrichment was not configured - the mechanism was still active and caused trouble (timeouts of messages in combination with acknowledgements were observed by a Ditto adopter).
The stabilization fixes this issue.

Tags: release_notes