In MDEX 6.2.0, the Why Did It Match feature has been renamed to Why Match to better align with other features such as Why Rank and Why Precedence Rule Fired.
In MDEX 6.1.4 and earlier, the Why Did It Match feature is enabled by
specifying the
--whymatch flag or the
--whymatchConcise flag to the Dgraph. In MDEX 6.2.0,
the
--whymatch and
--whymatchConcise flags are deprecated.
In 6.2.0, the Why Match feature is now enabled on a per query basis
using a new
Nx (Navigation search options) query parameter. The
feature in 6.2.0 behaves essentially like Why Match Concise mode in 6.1.4. For
details about using this query parameter, see the
MDEX Engine Developer's Guide and the
Presentation API References (Javadoc or .NET help).
If you want to continue using the 6.1.4 behavior, you can specify
either the
--whymatch or
--whymatchConcise flags without implementing the
Nx parameter in your application. For details about
using the 6.1.4 Why Did It Match feature, see the 6.1.4 version of the
MDEX Engine Developer's Guide. For details
about using the 6.2.0 Why Match feature, see the 6.2.0 version of the
MDEX Engine Developer's Guide.
In MDEX 6.1.4 and earlier, the Why Did It Match feature returns
information in a property named
Dgraph.WhyDidItMatch.
In MDEX 6.2.0, the Why Match feature returns a property named
Dgraph.WhyMatch.
In MDEX 6.1.4 and earlier, the Why Did It Match feature returned a
DGraph.WhyDidItMatch property that indicated the
single field that matched the query terms, the query terms themselves, and
information about how the terms matched a field.
In addition to the 6.1.4 information, the
DGraph.WhyMatch property in MDEX 6.2.0 also includes
multiple field names if a cross field match occurred for the query terms, and
the
DGraph.WhyMatch property also includes any query
expansion that may have been applied during query processing.
