Environment:
- Dynamicweb.dll: 9.18.1
- Dynamicweb.Ecommerce.dll: 1.18.1
- Dynamicweb.Indexing.Lucene.dll: 1.4.6
- Standard
Dynamicweb.Indexing.Queries.IndexQueryProviderrepository/index query (not custom code) — Ecommerce product index built via the standard repository/index/query XML setup (Repository +.index+.queryfiles).
Problem: A single-word search term shaped like
<one letter><digits>(e.g.M12,B1000) returns a result count that is entirely determined by the letter and completely independent of the digits — including digit strings that don't exist anywhere in the database.Reproduction (via the standard product search page/index query,
qparameter):Query Result count Real DB matches for this exact string m14275 — m124275 804 m994275 0 m7777774275 0 b13725 — b10003725 108 b9999993725 0 a24113 — a10004113 — z6 — z10006 — m99andm777777have zero literal matches inEcomProducts.ProductName/ProductNumber(confirmed via direct SQL against the underlying database), yet return the identical 4275-result set as the genuinely commonm12. Since the result count is invariant across wildly different digit strings — including nonexistent ones — this rules out normal tokenization, stemming, wildcard/prefix expansion, or substring matching, all of which would be sensitive to the actual characters typed. Something in the query pipeline appears to detect the<letter><digits>shape and short-circuit to a per-letter default/fallback bucket, discarding the digits entirely.What we've ruled out on our side:
- Not in our
Products.query(XML query definition) — no regex, branching, or letter-specific logic exists anywhere in its<Expressions>block; it's a plain OR ofEqual/ContainsBinaryExpressions againstProductName_Search,ProductNumber_Search,freetext, and Swedish-stemmedSynSV_*fields. - Not in our
Products.indexfield/analyzer configuration — no custom analyzer beyond a standard synonym dictionary, which itself doesn't affect this (confirmed: identical behavior on synonym-free control terms). - Not in our front-end templates — they only consume the already-populated
ProductListViewModel; none of them construct theeq/qquery parameters or contain any digit/letter-shape logic. - Multi-word combination logic is not the bug — separately confirmed that
Containscorrectly ANDs space-separated words together (e.g.skruvalone: 671 hits,mutteralone: 799,skruv muttertogether: 239 — a proper intersection-sized reduction). The bug is isolated specifically to single alphanumeric tokens matching this<letter><digits>shape. -
Impact: This makes any product-number-style search (a huge fraction of real customer searches in an industrial/fastener catalog, e.g. "B1000", "M12x50") return thousands of irrelevant products mixed in with the handful of real matches, since the query silently ignores the actual number typed.
Question: Is this a known issue in the Lucene indexing query layer? Is there a supported workaround (a different operator, a query/index setting) that avoids this letter/digit collapse, or does this need a platform fix?
Happy to provide a full request/response trace or repo access details on request.