Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-24173

Indexable field type implementation needs dedicated sort field

    Details

      Description

      With Solr and Elasticsearch search engines, in case when field type stores multivalued field data (for example RelationList), such field will not be usable for sorting.

      For this reason Indexable interface needs additional method like getDefaultSortField(), that will enable providing single-valued field that can be used for sorting.

        Issue Links

          Activity

          Hide
          Petar Spanja (Inactive) added a comment -

          Considering this a bit more, the issue might actually be invalid. Field criterion supports all available operators, and using GT, GTE, LT, LTE and RANGE on a mutlivalued field does not make sense.
          The mentioned use case for RelationList is already handled by dedicated FieldRelation criterion (supporting IN and CONTAINS operators), so in this line of thinking Field criterion would work only on single valued fields. FieldType's Indexable implementation could of course index multivalued fields, which would be handled by dedicated criteria (FieldRelation in this example).

          Show
          Petar Spanja (Inactive) added a comment - Considering this a bit more, the issue might actually be invalid. Field criterion supports all available operators, and using GT, GTE, LT, LTE and RANGE on a mutlivalued field does not make sense. The mentioned use case for RelationList is already handled by dedicated FieldRelation criterion (supporting IN and CONTAINS operators), so in this line of thinking Field criterion would work only on single valued fields. FieldType's Indexable implementation could of course index multivalued fields, which would be handled by dedicated criteria (FieldRelation in this example).
          Hide
          André Rømcke added a comment -

          Closing as invalid, we need to tackle/improve the modeling in Solr/ES most likely rather then exposing the current modeling in API as suggested here.

          Show
          André Rømcke added a comment - Closing as invalid, we need to tackle/improve the modeling in Solr/ES most likely rather then exposing the current modeling in API as suggested here.

            People

            • Assignee:
              Unassigned
              Reporter:
              Petar Spanja (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: