This is a response to a query from last year; I'm posting this so it will show up in the future if anyone does a web search on "XDMP-PARENTLINK". The query was:
http://developer.marklogic.com/pipermail/general/2015-April/017052.html Dave Cassel replied to say that the error might be connected with fragmentation. For the first time ever, I just ran into this error. The only diagnostic was along the lines of XDMP-PARENTLINK: Invalid parent link node doc("/path/to/mydocument")//body where in fact "body" is defined as a fragment parent. I couldn't see anything obvious wrong with the file, so I basically just chopped out children of doc("/path/to/mydocument")//body until I found the one child that was causing load failure. It looked like <div xsi:schemaLocation="something" xml:id="myid"> ... </div> and it was the @xsi:schemaLocation causing the problem. This was the only <div> in the document with that attribute. I don't know the XML specs well enough to know whether putting @xsi:schemaLocation on an element other than the XML root element is always an error, but evidently it makes MarkLogic unhappy when fragmentation is in effect. (The same document loaded OK into a different database with no fragmentation defined.) David -- David Sewell Manager of Digital Initiatives The University of Virginia Press Email: [email protected] Tel: +1 434 924 9973 Web: http://www.upress.virginia.edu/rotunda _______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
