My appologies. By 500K child nodes, I meant that this was a root, and
that the sum of the descendants were 500K. xxx/yyy has 5 children.
Most nodes have a small number (<20) of children. Part of the testing
was to see how I needed to change the data structure so that I
minimized the number of chil
Correction - the default maximum is 200, not 1000. Not sure what I was
looking at there.
Justin
On Wed, Oct 19, 2011 at 4:18 PM, Justin Edelson
wrote:
> Phil-
> If the JSON object requested contains more than the maximum number of
> nodes, an array is returned indicating which requests can be ma
Phil-
If the JSON object requested contains more than the maximum number of
nodes, an array is returned indicating which requests can be made to
return fewer than the max number of nodes.
The typical use case for this is where /xxx contains /xxx/yy0 through
/yy9 and each of /xxx/yy0 through /xxx/y
n/java/org/apache/sling/servlets/get/impl/helpers/ResourceTraversor.java?hb=true
--
View this message in context:
http://apache-sling.73963.n3.nabble.com/Strange-result-returned-from-the-1-json-servlet-Returned-a-list-instead-of-a-map-tp3435408p3435560.html
Sent from the Sling - Users mailing list archive at Nabble.com.
quot;,"xxx/yyy.0.json"].
Btw, 500k child nodes? I thought the recommended maximum was 10-20k.
-Original Message-
From: Phil Rice [mailto:phil.r...@softwarefm.com]
Sent: Wednesday, October 19, 2011 3:25 PM
To: users@sling.apache.org
Subject: Strange result returned from the '
I have a version of sling running that now has between 250K and 500K
nodes underneath a node called "/xxx/yyy".
When I do a get to http:///xxx/yyy/anything.1.json I get a
result that looks like:
{"jcr:primaryType":"nt:unstructured","artifact":{"jcr:primaryType":"nt:unstructured"}}
In this case
