Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
7.0.X, Master
Description
For User search, when you are doing custom sql joins that can return duplicate results, the search results return the duplicates rather than the distinct set of users. The results returned back should be a distinct set of user objects.
This only occurs when:
- users.search.with.index=false (doing a database search)
- you are invoking UserLocalServiceUtil.search(..) where the params references a custom join that returns duplicate results
This ticket LPS-66811 removed the "DISTINCT" because of a DB2 issue where ORDER BY columns did not match up with the SELECT columns. However, code has changed where ORDER by cols now match SELECT columns, so that is no longer an issue to include DISTINCT back in.