> We've hit the 1024 limit on parameters for the query api.
Do you know which limit this is? I'm not aware of such a limit in Oak.
Jut to ensure we talk about the same issue, I made an example, could you
check if this is correct?
Assuming you have 3 nodes:
/a @tag = 'color'
/b @tag = 'color/red'
/c @tag = 'color/blue'
Now you expect the following queries to return:
where @tag = 'color'
where @tag in ('color')
-> /a, /b, /c
where @tag = 'color/red'
where @tag in ('color', 'color/red')
-> /a, /b
where @tag = 'color/blue'
where @tag in ('color', 'color/blue')
-> /a, /c
Is this what you are looking for?
On 13/10/16 18:02, "rachna" <rachana.me...@telegraph.co.uk> wrote:
>Hi Clay & Thomas,
>Thanks for your replies.
>We have previously developed a feature that uses the tag management system
>inside of AEM. The current business logic performs a search against the
>repository using the tags associated with the content page. As part of
>business logic, the decendants of the tags (and decendants of these tags
>until the bottom of the tree is reached) are also added to the query. This
>creates a large query that isn't very efficient. We've hit the 1024 limit
>parameters for the query api.
>Our custom indexer analyses the decendants of the tags when the reindex
>operation is triggered so we can precompute this and store it efficently
>(We store the page path against the decendant tags in the index)
>Ideally we would want to query our index directly (e.g. native query) to
>return the results. From looking at the documentation for the lucene
>I can see this is possible.
>The documentation for the property index does not have the same query
>Is it possible to run a native query against a custom indexer?
>Otherwise, can we programmtically access a new NodeState?
>We've hit the 1024 limit on parameters for the query api. Also we've hit
>the 1024 limit on parameters for the query api.
>View this message in context:
>Sent from the Jackrabbit - Users mailing list archive at Nabble.com.