I played around in my test repository and I was able to produce that funky array with two scenarios: 1 - if I give it a depth that doesn't exist, which doesn't seem to be your case, that shows me an array with each element counting down from the number I gave it to 0 2 - if the depth that I give it includes nt:file
Not sure if it's because the node type nt:file, or the binary property attached to it, but it may be something for you to look into. If you're case is the same as mine, I'd expect http://<host>/xxx.2.json to show a similar array, perhaps ["xxx/yyy.1.json","xxx/yyy.0.json"]. Btw, 500k child nodes? I thought the recommended maximum was 10-20k. -----Original Message----- From: Phil Rice [mailto:[email protected]] Sent: Wednesday, October 19, 2011 3:25 PM To: [email protected] Subject: Strange result returned from the '.1.json' servlet. Returned a list instead of a map. 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://<host>/xxx/yyy/anything.1.json I get a result that looks like: {"jcr:primaryType":"nt:unstructured","artifact":{"jcr:primaryType":"nt:unstru ctured"}} In this case artifact is the name of a node under /xxx/yyy/anything. As stated there are a lot of nodes under /xxx/yyy and my tests indicate that all of them return a Json map, and as far as I can tell the data matches the properties of the nodes. When I do a get to http://<host>/xxx/yyy.1.json I get a strange result back: ["xxx/yyy.0.json"] When I do a get to http://<host>/xxx.1.json, I get the normal map. So of my half a million nodes, only this one is unusual. The nodes above it behave correctly, the nodes below it behave correctly. Only this one is strange. When I inspect the node /xxx/yyy with the explorer, it has only the default jcr:primaryType property. As further information the response to http://<host>/xxx/yyy.0.json return a map: {"jcr:primaryType":"nt:unstructured"} What is even more disturbing is that while I was testing it, initially xxx/yyy.1.json behaved as normal, but about 2 days into the testing it changed. I have been able to reproduce this, although with a cycle time of many hours, it is hard to be certain what actions caused the behavior to change. I would appreciate any advice on: * What the result: ["xxx/yyy.0.json"] actually means * Is this a bug, or is it a "feature" that I need to know about As this is on a server running live on the internet, I can pass ip address/port details and username/password details in private emails but I am loath to do that over an open email.
