splainer-search
Advanced tools
Changelog
2.13.0 (2022-02-21)
Support an empty explanation hash in the response from either ES or Solr. @A2Kashyap proxied a custom API to look like Elasticsearch response to Quepid, and therefore the explain output looked like "_explanation": {}
, which we hadn't expected. https://github.com/o19s/quepid/issues/465 by @A2Kashyap is fixed by https://github.com/o19s/splainer-search/pull/102 by @epugh.
Handle both id field as _id
(standard) and any alternative ID field in Elasticsearch when comparing Snapshots. Issue opened by @KennyLindahl at https://github.com/o19s/quepid/issues/466 and fixed by @KennyLindahl via https://github.com/o19s/splainer-search/pull/101!
Changelog
2.12.0 (2021-12-17)
doc._url()
) have faceting turned on for ALL of the fields listed. This may be a feature to help you understand about a single document, however I don't quite have a use case that makes sense. @jeffryedvm showed me it taking 30 seconds to query a single Solr doc due to what was blindly being faceted on, and opened https://github.com/o19s/quepid/issues/442.Changelog
2.11.0 (2021-11-05)
null
instead of a {}
array. Now check that situation as well.Changelog
2.10.0 (2021-08-25)
responseHeader.params
if they exist as searcher.parsedQueryDetails
.npm audit
and upgraded dependencies.Changelog
2.9.0 (2021-08-20)
Changelog
2.8.0 (2021-08-16)
/template
for Elasticsearch will be assumed to be a template query. Thanks @danielibars for encouragement and testing. https://github.com/o19s/splainer-search/pull/92 by @epugh.Changelog
2.7.0 (2021-07-28)
searchFactory
the property parsedQueryDetails
that stores details about the query
being processed by the search engine. Works with Solr and Elasticsearch.querqy.infoLog
details in the parsedQueryDetails
property.Changelog
2.6.11 (2021-06-30)
Changelog
2.6.10 (2021-05-27)