v2025.2.0

What’s Changed

⛓️‍💥 Breaking changes

• Ability to define the order constraint for ordering groups in 1:N ordering by @novoj (#160)

Backward incompatible behavior change:

A sortable attribute compound is only created if at least one of its attributes is present in the entity. This fact is
crucial for the standard sorting mechanism of evitaDB, where such entities are passed to the next sorter defined in
the query (or sorted by the primary key in ascending order if no other sorter is defined).

🚀 Features

• Accept labels in HTTP headers (#802)
• Allow overriding serviceName for OpenTelemetry in configuration (#805)
• Allow engine start even if configuration contains unknown property (#806)
• Facet summary integration with hierarchical entities (#352)
• Provide means for accessing reference count without actually fetching the entities (#650)
• Update facet summary impact calculations (#775)
• The REST / GraphQL documentation examples contain superfluous arguments (#808)
• Request metrics: success, error, timeout (#823)
• New metric that would capture current evitaServer version (#829)
• Update evitaLab to v2025.1.1 (#804)

🐛 Bug Fixes

• Data files might have been removed before backup is finished (#816)
• Invalid SemVer comparison result (#827)
• ContextMissingException when accessing group not matching query locale (#766)
• Referenced entities might not be returned when multiple scopes are requested in the query (#830)
• Method removeAllReferences doesn't really clear all insert reference mutations from EntityBuilder (#832)

Full Changelog: v2025.1.0...v2025.2.0