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:unstructured"}}
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.
