[MGNLEESOLR-123] Solr search view produce different results than default search view Created: 28/Feb/18  Updated: 26/Mar/18  Resolved: 23/Mar/18

Status: Closed
Project: Solr Search Provider
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2

Type: Task Priority: Neutral
Reporter: Milan Divilek Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2018-02-28 at 13.41.22.png     PNG File Screen Shot 2018-02-28 at 13.43.15.png     PNG File Screen Shot 2018-02-28 at 13.51.57.png    
Issue Links:
causality
caused by MGNLEESOLR-120 Use Solr for search indexing a large ... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: High asset load
Sprint: Kromeriz 138, Kromeriz 139, Kromeriz 140
Story Points: 8

 Description   

Results when default SearchPresenter is used:

Results when Solr SearchPresenter is used:

Folders are not visible in solr search view. This is because indexer is configured to index "mgnl:assets". This can be fixed by using another indexer for folders

Field 'path' is used when searching in solr indexes, but field path doesn't exist in magnolia.



 Comments   
Comment by Antti Hietala [ 05/Mar/18 ]

Solr results are too noisy. Exclude asset path from Solr indexing by default. Add a second indexer for mgnl:folder node type. A customer can provide their own indexing configuration if they want to index also the path.

The goal is to provide a results view that is not too different from what the user has learned in other Magnolia apps and is not too different from well known search tools such as Google Drive.

You would typically expect to see:

  • Folders that contain the search term
  • Assets whose name contains the search term
  • Assets whose metadata properties ("content") contains the search term

But not:

  • Assets whose path contains the search term. This is too much and makes the results list unnecessarily long.
Comment by Karel de Witte [ 05/Mar/18 ]

Note that you can also use negative filtering with solr for instance -path:travel* best regards

 

https://lucene.apache.org/solr/guide/7_1/the-standard-query-parser.html#differences-between-lucene-query-parser-and-the-solr-standard-query-parser

Generated at Mon Feb 12 11:00:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.