Closed (works as designed)
Project:
Search API sorts
Version:
7.x-1.4
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
25 Sep 2013 at 12:08 UTC
Updated:
1 Dec 2016 at 09:52 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedJust index both values in Search API. Did you try?
Comment #2
preethivv commentedOk I will Check. Thank you for the information.
Comment #3
polWeight value is not available in search API.
I think we need to implement a hook to make it discoverable.
Comment #4
jason.fisher commentedI do this by using aggregate fields -- aggregating content type and date together gives me a single field I can use to display table groupings of type, with the newest at the top of each table.
However, aggregate fields does not let you specify the order of aggregation, and it's only luck if it works out in your favor.
I would recommend using Computed Fields to generate a single compound field ahead of time that you can index for sorting.
Comment #5
Anonymous (not verified) commentedAs designed.
Comment #6
jeroen dost commentedI have the same problem: not finding the weight in the list of fields to index, resulting in not being able to sort on weight in my search api result view. You say it works as designed, but how is it designed to being able to use the weight module for sorting search results?
Thanks in advance.