Jeff
08/31/2024, 5:25 PMcreatedAt:desc,_vector_distance:asc
the first result is always this one, and is completely wrong
Rightfoot
Backend Engineer - Platform <----- completely irrelevant to the query
San Francisco, USA
9 hours ago
11-50 employees
Skills: backend services, Java, Series-A startup, quick learner, Spring framework, Kafka, RESTful APIs, Infrastructure as Code, Fintech Show Less <----- completely irrelevant to the query
query
{
"indexName": "listings",
"query": "Frontend Engineer React Python GraphQL JavaScript",
"queryBy": "embedding",
"vectorQuery": "embedding:([], k:10000, distance_threshold:1.0)",
"sortBy": "createdAt:desc,_vector_distance:asc",
"includeFields": [
"*"
],
"page": 1,
"perPage": 10,
"filterBy": [
{
"jobCategory": "Software Development"
},
{
"status": "active"
}
]
}
Jeff
08/31/2024, 5:25 PMJeff
08/31/2024, 5:27 PMall-MiniLM-L12-v2
model, not sure if anyone has better experience with other modelsJason Bosco
08/31/2024, 9:15 PMcreatedAt:desc
as the first field in sort by results in a hard sort on created_at and only if created_at is tied, then the vector distance is used for tie breakingJason Bosco
08/31/2024, 9:16 PMJason Bosco
08/31/2024, 9:16 PMIs there a way to prioritize certain parts strings when doing vector search?Not it's not possible to do this. The model completely determines ranking