Hi Anil, I tend to the assumption that productive eCommerce sites will use the Solr search and that the database search should be a documented fallback.
Maybe we should fix this anyway and use the old bugfix suggestion. If someone with access to an up-to-date Oracle instance reports a problem with it we still can find a worksround . Best regards, Michael > Am 01.07.2026 um 13:13 schrieb Anil Patel <[email protected]>: > > Hi all, > > Going through old bugs I hit OFBIZ-1514, a duplicate-results bug in the > database product keyword search: > https://issues.apache.org/jira/browse/OFBIZ-1514 > > I started out thinking this was a "don't bother, use Solr" case. But the > Solr plugin was moved to the Attic during the Jakarta migration > (OFBIZ-13220) because of its javax dependency, with the suggestion to run > Solr as a standalone instance. So we no longer ship an integrated Solr > product search, and the database keyword search is the only built-in > product search left. > > That changes the question. The bug is real - the search does a DISTINCT > that doesn't group by productId, so a product with more than one matching > keyword can be counted and shown more than once. There is even a fix from > 2007 (group by productId), still sitting commented out in ProductSearch, > blocked all this time on a never-confirmed worry that it broke Oracle. > > So I would like the community's view on direction: > > - Now that integrated Solr is gone, is the database product search the path > forward for ecommerce? If so, it should work, and we should fix this and > finally settle the old Oracle question. > - Or is the intent that serious sites run standalone Solr, and the built-in > DB search is just a basic fallback? If so, we should say that clearly and > set expectations for what it needs to do. > > Either way, an 18-year-old bug in the only built-in product search we have > deserves a decision. What do people think? > > > > Thanks and Regards > Anil Patel > CEO > HotWax Systems > http://www.hotwaxsystems.com
