Note:- During conversion to Xpath query * is converted to % and ? is converted to _ . For Example ‘metadata%’ (metadata node is considered, will return result for metadata,metadata1,metadata2 etc) but for ‘metadata_’ (metadata node is ignored, will only return result for metadata1, metadata2). Choose your wildcards very wisely. Hope it clears your doubt.
Blogs (slightly outdated but good historical content)
A2. There are other node types as well. such as dam:Asset, nt:unstructured, etc. please visit this URL: http://localhost:4502/crx/explorer/nodetypes/index.jsp and youll find all the registered node types you can query on.
Please go through https://hashimkhan.in/aem-adobecq5-code-templates/query-builder/ to learn more about querybuilder and available predicates and possibilities to achieve using the query builder
now to your questions:Q1. None of the results are actually pages from the site? The site we have locally is the wknd starter site. How do you return pages from the site hosted in AEM?A1. Because you are searching at root (/) these are all cq:Page results, but in order to get specific results from your site, you need to specify your specific project path(like path=/content/we-retail). This is the way you return the intended pages from your AEM instance.
By default, 10 results are returned. If you specifiy “p.limit=-1”, it will bring in entire matching/applicable results.
Continuous Integration and Delivery – DevOps
(* not sure if this is still being updated)
The real lesson here is: If your content is hierarchical, by all means, capitalize on that fact! Don’t try to treat your content as a Big Flat List, especially if you’ll be doing a lot of updates. (If you’re doing mostly reads and few writes, on the other hand, it doesn’t much matter.) Introducing a bit of hierarchy to your content organization scheme will go a long way toward promoting fast update performance.
It is common to have multiple CQ Publisher instances in different environments (DEV, QA, PROD, etc.). When you make user administration and security changes toward users and groups on the production server, you may want to bring them down to the lower DEV and QA environments so they don’t go out of sync. In such scenario, you have to copy over both user/group definition and the permission definition. This post shows you how to copy users and groups you set up on one CQ instance (source CQ) to another instance (destination CQ), and how to bring over the permissions (resource-based ACLs) from the source CQ to the destination CQ.
Although read performance remains good, write performance can suffer in the case where you need to store, say, thousands of sibling nodes under one parent node. This has to do with the fact that TarPM is an append-only store in which objects are immutable and never overwritten, only rewritten. What it means is that the cost of adding (or updating) Node No. N-thousand-plus-one can be quite high.
Q3.) You might be aware that whenever I upload a DAM asset in AEM, a back-end workflow gets triggered. Now I have to upload approx 3000 dam assets of various sizes in my AEM instance and I don’t want to burden my instance with thousands of workflows at once. How shall I go about it?
Friends, this blog post might be somewhat tricky and thought-provoking . The questions which are mentioned below are basically business scenarios which are asked in an interview and you are required to ponder over it and come up with the most feasible solution. The answers to these questions might differ approach to approach. There could be a possibility that you may come up with a better solution or maybe the answers which I have written below might broaden the scope of your thinking. Do let me know if you have a better solution for them. I would be happy to add it here.