Hello, Yash.
The syntax you come up with makes sense. It's important to don't prepend it
with space; probably bracket may be redundant; you can also resolve syntax
ambiguity with local params.
fq={!cache=false v="filter(planName:all_features) OR zipCode:1234"}
debugQuery=true shows how it's parsed.
Hi Rajani,
the issues you mentioned are very old and superseded by more recent works
in the vector-based search domain.
The 'knn' query parser that Kumar detailed is the official way of doing
vector search in Solr.
Function queries for vector similarities and the possibility of better
Hybrid searc
: Hmm. That doesn’t seem consistent with the format change added in
: SOLR-5980, where each ID can have a _route_ attribute.
:
: { "id":"ID" , "_route_":"route”}
I think you may be getting confused between the syntactic sugar of sending
a single delete command as the entire JSON payload + the
I wouldn’t call it semantic sugar, more like a different compact format. The
compact format also avoids duplicate keys, which are legal in JSON but hard to
create in some systems.
The XML command format is working fine.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.or
On 2023-05-26 1:19 PM, Walter Underwood wrote:
I wouldn’t call it semantic sugar, more like a different compact format. The
compact format also avoids duplicate keys, which are legal in JSON but hard to
create in some systems.
It's not they're hard to create, it's that you can't create a data
: For e.g. - Current FQ -
: fq: planName:all_features OR zipCode:1234 (in this case entire FQ is cached)
:
: I don't want to cache the entire FQ given it's very unique , but I
: want to cache the first part (plan_name:all_features) to improve
: performance . How do I achieve this?
:
:
: My und
