On attribute's SearchFields, there is a list of joinPaths, used for linked contents and repeaters, and the path of the attribute.

This path is the complete path of the attribute in the model. This means that the repeater is in this path. I think it should be the path from the repeater

The path is used to construct the name of the SearchField, the sort and facet query. Each time concatened with the joinPaths.

Example, with an attribute composite/repeater/string:

• joinPaths contains composite/repeater => OK
• path is composite/repeater/string,
• and here are what the created name and queries look like:
  • name: composite/repeater/composite/repeater/string => KO
  • queries:  join(composite/repeater, composite/repeater/string_s_sort => KO

 
Tried to find a functional bug with this, but it seems that it is not possible to sort on data in repeaters