Does the new node created searchable from any query tools like crxde, querydebug?
My first suspect would be is node getting indexed. Verify the index settings if by any chance you are restricting.
Yes, I do see the new node in CRXDE and in the Query Debugger. Did you mean your "first suspect is that the node is NOT getting indexed?" Could you provide any advice as to what I should be looking for in the index settings?
Indexing nodes is a synchronous acitivity during the write (exception to that rule: large binaries are index async).
Sham, I checked out the indexing settings. The only thing that jumped out at me was the <aggregate primaryType="cq:PageContent"> tag that contains a bunch of children which describe how "deep" to index a page node. It's possible this is affecting the system's ability to index these "new" nodes added by the PostProcessor, because they are created 6 levels beneath a cq:PageContent (jcr:content) node and the default setting here was 4 levels. I added a few more levels to this aggregate node, so that it can index 7 levels deep and it did not seem to have an effect.
I'm wondering, though, if this is still the right track. First, when I change indexing settings in this file, all I should have to do is restart the instance, right? Is there anything else I would need to do to ensure the changes are taken into efffect? Second, I'm thinking that I can use the <aggregate /> tag to be a bit more specific about expecting the system to index my "new" nodes. The problem is, the big data structure my new nodes are part of is made up of only "nt:unstructured" nodes. Is there a way to specify an aggregate using node name or some identifier other than "primaryType"? I didn't see this readily explained in the Jackrabbit indexing documentation. If I could specify an aggregate based on primaryType="nt:unstructured" and node name="my:NodeName", I think I could create a specific enough aggregate tag to possibly resolve the problem.
Does any of this sound valid, or am I going down a rabbit hole? I appreciate the help guys.
By the way, firstname.lastname@example.org, I'm with you on the synchronous indexing. That's what I expected, which is why I'm confused as to why subsequent JCR queries do not account for the "new" nodes.
If you are able to get results by searching from CRXDE and in the Query Debugger. It should be correct because be default all nodes & properties are indexed.Does not make sense to look into indexing configuration.
This looks strange, it should work. Could you please post a code or file a daycare so that i can take a look.