Hi @nitesh_kumar ,
Thanks for your suggestion. I tried all the options you provided, none was working.
I tried
{
loader: 'ts-loader',
transpileOnly: true
}
in webpack.common.js
"typescript": "^4.8.2" and "typescript": "^4.8.4" in ui.frontend/package.json
They all failed at "npm install pr...
Hi All,
I recently start a project with archetype 32. After creating it, I tried to build it using maven as:
mvn clean install, I got following error:
[INFO] WARNING in ./src/main/webpack/site/main.ts
[INFO] Module Warning (from ./node_modules/glob-import-loader/index.js):
[INFO] (Emitted valu...
/crx/explorer is shipped with AEM as part of the jar so it's there is no Sling configuration associated with it. You may need to go to /system/console/bundles, search "Adobe Granite CRX Explorer" and stop the bundle. For other paths, you can go to /system/console/configMgr, search "Apache Sling Auth...
I made our own index as shown in the screenshot. A lucene-type index with many other indexing keys also. The issue is that when using cq:tags, oak-1.0.22 always picks up the OOTB one. I tried to make an alternative by getting rid of the OOTB one, which is always a bad idea, it turned out that there ...
That's correct, but it will consume a lot of cpu power if the site gets hit at a certain level. Plus, when it drops the query at the limit, say, 100k nodes, the result set is not always accurate because the more precise records may be left behind.
Hi @aanchal-sikka,
It looks like oak doesn't know how to limit the query size for some reason. My understanding is that if a query limits to a certain path, say, /jcr:root/a/b/c, the space complexity shouldn't be more than the total nodes under that path. I issue a query to a certain path with onl...
Hi Kiran,
No the path is very specific. I actually did a very simple query as:
/jcr:root/content/site/departments/film-tvs/courses/2022-fall//element(*, cq:PageContent)
It traverses 80000 nodes even if there are less than 100 pages under that directory. The similar issue you are referring is a h...
Hi all,
We have an issue for the AEM6.0/oak-1.0.22 indexing issue. There a lot of warning messages like:
org.apache.jackrabbit.oak.plugins.index.property.strategy.ContentMirrorStoreStrategy Traversed 80000 nodes (280221 index entries) using index cq:tags with filter Filter(query=select [jcr:path],...