generic-data-index-bundle: CalculatedValue fields are always indexed as text/keyword, ignoring their configured elementType

[andreaswagner-rnab]

Affected Version

2026.2 (verified on 2025.4 LTS as well; the mapping registration has been unchanged since 2024, so all versions are affected)

Affected capability

Data Objects

Steps to reproduce

1. Create a class definition with a CalculatedValue field configured with elementType: 'boolean' (the same applies to numeric and date)
2. Run bin/console generic-data-index:update:index
3. Inspect the field mapping on the new index version: GET <index>/_mapping/field/standard_fields.<fieldname>

Actual Behavior

The field is mapped as text with ngram/keyword/sort subfields — calculatedValue is registered on TextKeywordAdapter in config/services/search/data-object/field-definition-adapters.yml and the configured elementType is never consulted.

As a consequence, typed operations on calculated boolean/numeric/date fields misbehave: terms aggregations are rejected on the text field, and the Studio data object grid boolean filter on such a field stops working.

Expected Behavior

The index mapping honours the configured elementType: boolean → boolean, numeric → float, date → date, with the text-based element types (input/textarea/html) keeping the current text/keyword mapping.

Fix provided in pimcore/generic-data-index-bundle#488.