Solr Learning to Rank - Trailing slash in path behavior differences, expected?

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Solr Learning to Rank - Trailing slash in path behavior differences, expected?

Doug Turnbull
Hello everyone,

I encountered some surprising behavior that got be stuck on Solr LTR for a
good hour. I wanted to share it, and you can decide if its a bug (I suspect
it's a bug)

I wanted to list all the feature stores on my Solr 7.7.1 instance. So I
visited

GET http://localhost:8983/solr/tmdb/schema/feature-store/

And I scratched my head, because I thought I would find a list of
featureStores like:

{
  "responseHeader":{
    "status":0,
    "QTime":0},
  "featureStores":["title"]}


Instead, I got the response for a feature store with empty features,
which was quite perplexing:

  "responseHeader":{
    "status":0,
    "QTime":6},
  "features":[]}

Once I removed the trailing / from my URL, I got the expected response:

{
  "responseHeader":{
    "status":0,
    "QTime":0},
  "featureStores":["title"]}


Feels like this is a really easy mistake to make and lose a lot of time on.
But is there a reason this is actually somehow expected behavior? It seems
that with a / my request is interpreted as for a feature store (of name
space or /?!?), which I'm guessing would not be what someone wanted.

Thoughts?

--
*Doug Turnbull **| CTO* | OpenSource Connections
<http://opensourceconnections.com>, LLC | 240.476.9983
Author: Relevant Search <http://manning.com/turnbull>
This e-mail and all contents, including attachments, is considered to be
Company Confidential unless explicitly stated otherwise, regardless
of whether attachments are marked as such.