You can cross check on the below to narrow down the cause
If it is reproducible in we-retail if its reproducible in all your environments for your project contentIf it is project specific,
check if you have amended the grid.css and/or custom device options as part of emulatorcheck if y...
For boosting search results based on a specific field, you can do the following
we have a property called boost -> set it to a higher value say 2.0 (on tags field in this case) within the index definition.
for a query like the below, OOTB cqPageLucene is used
The URL samples you have shared is path with suffix not selectors and in cache structure, path till my-component.json will be in htdocs folder (since it is a file, no more further structure will be created unlike a directory) - In other words, /product1-3 will not be cached.
You can try the following
Given your existing assets set up, in one of the path itself you have the max result set - But the query checks both the paths (using OR)
Try with one path
See if you can consider additional parameters for refining the search results.
Ex: Refining search results ...
Please find below for the response for your questions inline in green
Is it possible to search for keywords inside a text file (such as a .txt or .css file)?
Yes, Apache Tika config is responsible for the same - https://myaemlearnings.blogspot.com/2020/06/apache-tika-config-in-lucene-in...
Please note that the message that you have shared is of "DEBUG" type and not an ERROR.
property [imageFeatures] doesn't have namespace prefix, skipping. metadata node:
which is logged when there is no namespace prefix (Ex: something like dc:title - In this case, dc is the namespac...
Per the error statement you have shared, looks like problem is with content package - /mchp.ui.content-1.0-SNAPSHOT.zip
I suggest to try the following to narrow down the issue :
Run just "mvn clean install" without ant specific profile Then try with with autoInstallBundle profile / In ...
Please note that suggest queries used with ISDESCENDANTNODE has very limited support to subset the suggestions under that path.
The subset is done by filtering top 10 suggestions. So, it's possible to get no suggestions for a subtree query, if top 10 suggestions are not part of that subtr...