Before indexing, you can add this field in your manage_schema and refresh collection. Then do indexing by sending required page or properties to your collection. Custom Manipulation logic you need to write at index service.

You can check error logs. It will give you descriptive info. Share logs.

Go to code module path like cd <project>/core and run below command. It will deploy only core module. mvn clean install -PautoInstallBundle You can also do skiptests for local work: mvn clean install -PautoInstallBundle -DskipTests=true  

Refer https://levelup.gitconnected.com/aem-creating-a-color-picker-with-a-predefined-palette-c4a03c1eddc5  

Check bundles are active or not at http://localhost:4502/system/console/bundles and verify error logs. Might be issue with core bundles not available at runtime.  Share logs.

try  unregister this service from http://localhost:4502/system/console/components

Did you adapt model with SlingHttpServletRequest? @Model(adaptables = { SlingHttpServletRequest.class}  Can you share your model?

Use below query to get all assets and metadata from dam path.    type=dam:Asset path=/content/dam/<project> p.hits=selective p.properties=jcr:content/metadata/dc:format jcr:content/metadata/dam:size In above query i am fetching format and size. Click on JSON QueryBuilder Link to view metadata json ...

In Sling model, take request object @Self private SlingHttpServletRequest request; and call request.getRequestURI() to get domain

If you are using querybuilder api, it will return all results with p.limit=-1 (this might be a high number depending on your instance). If you want to implement pagination then you can use offset and limit like this path=/content/<project>/us/en/products type=cq:Page property=jcr:content/@commerceTy...