: Hoss, for some reason this doesn't work when I pass the latlong value via
: query..
...
: fl=*,score&rows=10&qt=findperson&fps_latlong=26.22084,-80.29&fps_fname=peter
Hmmm, are these appends & invariants on your "findperson" requestHandler?
What does debugQuery=true show you the pplied filters are?
: <lst name="invariants">
: <str name="fq_bbox">_query_:"{!bbox pt=$fps_latlong sfield=geo
: d=$fps_dist}"</str>
: </lst>
Why do you have the _query_ hack in there? i haven't had a chance to test
this, but perhaps that hack doesn't play nicely with localparam variable
substitution? it should just be...
<str name="fq_bbox">{!bbox pt=$fps_latlong sfield=geo d=$fps_dist}</str>
: This works fine when the latlong value is passed via custom component. We
: have a custom component which gets the location name via query, calculates
: the corresponding lat long co-ordinates stored in TSV file and passes the
: co-ordinates to the query.
Ok wait a minute -- all bets are off about this working if you have a
custom component in the mix adding/removing params. you need to provide
us with more details about exactly how your component works, where it's
configured in the component list, and how it is adding the "fps_latlong"
param it generates to the query, becuase my guesses are one of two things
are happening:
1) your component is doing it's logic after the query parsing has already
happened and the variables have been evaluated -- at which point
fps_latlong isn't set yet, so you get the case='*:*' behavior
2) your component is doing it's logic before the query parsing happens,
but it is setting the value of fps_latlong in a way that the query parsing
code doens't see it hen resolving the local variables.
-Hoss
