You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Joe Eckard (JIRA)" <ji...@apache.org> on 2007/12/11 22:53:43 UTC

[jira] Commented: (OFBIZ-1514) Duplicates in Search Results

    [ https://issues.apache.org/jira/browse/OFBIZ-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550726 ] 

Joe Eckard commented on OFBIZ-1514:
-----------------------------------

To reproduce this from a clean checkout:

Load demo data, create keywords for all products. In the catalog manager, do a keyword search for "gizmos" with a VIEW_SIZE parameter of 10. You should see "1-10 of 19". Then manually add the keyword "gizmotron" to Big Gizmo (GZ-8544). Do the same search again and you should see "1-10 of 20".

> Duplicates in Search Results
> ----------------------------
>
>                 Key: OFBIZ-1514
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1514
>             Project: OFBiz
>          Issue Type: Bug
>          Components: product
>    Affects Versions: SVN trunk
>            Reporter: Joe Eckard
>            Priority: Minor
>
> If a product has multiple keywords with identical roots and different relevancy weights and the product is within a set of search results that span multiple pages, then it will be duplicated in the results display. This is because ProductSearch is doing a "distinct" on productId, relevancyWeight(s) instead of grouping by the productId.
> I'm attaching a small proof-of-concept patch to make grouping by productId the default - it appears to work well with various combinations of search criteria (multiple keywords, features, feature cats, categories, etc.) but I haven't done a tremendous amount of testing. (Only using PostgreSQL and Derby)
> From the comments in the ProductSearch code it looks like it was done this way once, but it may have caused problems with Oracle. Does anyone know what that problem was, or can anyone check this patch against oracle?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.