adityamparikh commented on PR #184:
URL: https://github.com/apache/solr-mcp/pull/184#issuecomment-5357238019
Updated to assume #185 is merged — **this PR now depends on it.**
With the empty-facet fix in place, Step 2 no longer throws. The schemaless
facet returns:
```json
{ "numFound": 61, "documents": [], "facets": { "platform": {} } }
```
Which is a better illustration of the point than the exception was. A stack
trace reads as
"something is broken and it isn't your fault." A query that succeeds against
61 documents and
returns an empty breakdown is exactly the trap schemaless sets: nothing
tells you the data is
fine and the field type is the problem.
Changes:
- Step 2 rewritten around the empty result rather than the crash
- the `#182` entry dropped from Known issues (`#183` and the `sortClauses`
note remain)
- the `platform` row sharpened with a concrete consequence — searching
`platform:prime`
matches all 20 Amazon Prime Video shows, so the category has stopped being
one value
Re-verified against a build of the #185 branch, driven over the MCP
protocol: the empty facet,
the 20-hit token match, the three guessed types (`text_general` / `pdoubles`
/ `plongs`), and
the array-wrapped documents.
If #185 is rejected or reworked, say so and I'll restore the previous
wording — the earlier
revision documented the exception and is still in this branch's history.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
