I have not heard of anyone using XInclude for this purpose, but I have for
similar things, so it seems to me like a good use case for it. You can
probably also write some XQuery relatively easily that can create your
serialized version of the document. Something like:
<Document>{
/Document/Folder/name,
/Document/Folder/Schema,
/Document/Folder/Placemark}
</Document>
From: [email protected]
[mailto:[email protected]] On Behalf Of Charles Greer
Sent: Tuesday, August 16, 2011 12:09 PM
To: General MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] Is KML a good candidate for fragment
parent configuration?
Excellent response. So let's say the scenario did involve a lot of updates.
But that the serialized integrity of the KML file is good to preserve.
XInclude could provide both small documents and the structure of the macro
document. Have you heard of people using that approach?
Charles
On Aug 16, 2011 11:35 AM, "Danny Sokolsky"
<[email protected]<mailto:[email protected]>> wrote:
Hi Charles,
I would say the answer to your question lies with:
a) how do you want to query your documents?
and
b) how do you want to update your documents?
In general, you want to query at a fragment root. So if you will be doing
queries on /Document/Folder/name,
/Document/Folder/Schema, and /Document/Folder/Placemark, then you should be
good for the query side.
As for updates, you can have a lot of contention on that URI during updates if
multiple threads will be updating that document at the same time (for example,
to update different parts of it). If these were different documents, then
there would be no such contention.
The issue with querying documents with fragmentation lies with the indexes
being fragment-based, so if you are searching above a fragment root, that can
become an issue with index resolution accuracy. If you are searching at the
fragment root, it should be fine.
Now it might be that none of these things matter to you, in which case this
approach would be fine. I don't really know enough about KML to say for sure
what the answer is here, but all other things being the same, I would say that
the ideal is to keep each kml document as its own document, but that the
fragment strategy might also work just fine.
-Danny
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Charles Greer
Sent: Tuesday, August 16, 2011 9:28 AM
To: General MarkLogic Developer Discussion
Subject: [MarkLogic Dev General] Is KML a good candidate for fragment parent
configuration?
I've been working with InfoStudio to try out various load scenarios with big
KML files, very please...
_______________________________________________
General mailing list
[email protected]<mailto:[email protected]>
http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general
