Skip to content
Snippets Groups Projects
  1. Sep 03, 2024
  2. Aug 28, 2024
  3. Aug 27, 2024
  4. Aug 26, 2024
  5. Aug 23, 2024
  6. Aug 22, 2024
  7. Aug 20, 2024
  8. Aug 19, 2024
  9. Aug 18, 2024
    • Daniel Bimschas's avatar
      HOLI-9527: add fields `matchedTopics`, `matchedSkills` and `matchedGeoLocationDistanceInMeters` · a32553f3
      Daniel Bimschas authored
      This commit extends the `Engagement` type by three new fields that are set if used in a
      recommendation query response:
      
      * `matchedTopics`
      * `matchedSkills`
      * `matchedGeoLocationDistanceInMeters`
      
      The first two fields contain topics and skills that a recommendation query asked for if (and only
      if) those were the reason for the recommendation to include a given engagement in the response.
      A match will only be included if it surpasses a certain threshold (set to 0.5 in this commit).
      
      If `geoLocationId` is passed as a query parameter`matchedGeoLocationDistanceInMeters` contains the
      distance in meters from the geolocation resolved from `geoLocationId`to the geolocation of the
      engagement opportunity.
      a32553f3
  10. Aug 16, 2024
  11. Aug 15, 2024
    • Daniel Bimschas's avatar
      HOLI-9524: use index and fix distance calculation · d34b474f
      Daniel Bimschas authored
      * query now (implicitly) uses the HNSW index on embedding_array
      * query now uses the `<#>` operator to sort by distance which can (and will) take advantage of the
        index for the newly introduced `location_gps` column which combines (`longitude`,`latitude`) into
        a PostGIS geometry
      * distance calculation is fixed - it calculated before with two different units (distance in
        "angle" (RSID 4326) vs. distance in meters (RSID 3857, Pseudo-Mercator plane projection))
      d34b474f
  12. Aug 14, 2024
  13. Aug 13, 2024
  14. Aug 12, 2024
Loading