Re: [MarkLogic Dev General] Query on fragmentation of xml document

[Geert Josten]

Hi Reecha,

http://stackoverflow.com/questions/33229968/fragment-xml-files/33233119#33233119

Cheers,
Geert

From: 
mailto:general-boun...@developer.marklogic.com>>
 on behalf of Reecha Bhandari 
mailto:reecha.bhand...@niit-tech.com>>
Reply-To: MarkLogic Developer Discussion 
mailto:general@developer.marklogic.com>>
Date: Tuesday, October 20, 2015 at 11:18 AM
To: "general@developer.marklogic.com<mailto:general@developer.marklogic.com>" 
mailto:general@developer.marklogic.com>>
Subject: [MarkLogic Dev General] Query on fragmentation of xml document

Dear All,

We have xml files of this form wherein we have repetitive  node. Can you 
please guide as how I should fragment this xml file. I have posted question in 
stackoverflow and below is the link:

http://stackoverflow.com/questions/33229968/fragment-xml-files


NEWTAFDEFIGCAEIKBEIECJIAEBHHBFEIDJEJ750EAGGDJCBE3E8QWERTYUIOPLK12AIIDJPEOPLEGGICDPEOPLEAISSUERStrueHGE3E8QWERTYUIOPLK12HDEDKPEOPLEEEKIKPEOPLEAISSUERSAHDFIRSTNAMEDKISURNAME1970-08-04AHDDKIFIRSTNAMELASTNAMEIDSCHEMEEUIDC
 Test 
issuerUKEDEFIRSTNAMEEBESURNAME1970-08-04EDEEBEFIRSTNAMELASTNAMEIDSCHEMEEUIDE
 Test 
issuerXPRAUKFHAFIRSTNAMECFCSURNAME1970-08-04FHACFCFIRSTNAMELASTNAMEIDSCHEMEEUIDJ
 Test 
issuerfalse2015-05-18T01:12:05.864MTCH5523570.1892460XOFFDE000CR6Y4E4CASHDJBAPEOPLEFFDCPEOPLE




[cid:image003.png@01D10B28.978E5560]


Please Advice.


Thanks,
Reecha







DISCLAIMER

The information transmitted, including any attachments, is intended only for 
the person or entity to which it is addressed and may contain confidential 
and/or privileged material. Any form of reproduction, dissemination, copying, 
disclosure, modification, distribution and / or publication of this message 
without the prior written consent of the author of this e-mail is strictly 
prohibited. If you receive this email by mistake, please advise the sender and 
delete it immediately. Email transmission cannot be guaranteed to be secure, or 
error free as information could be intercepted, corrupted, lost or destroyed as 
a result of the transmission process. Views or opinions presented in this email 
are solely those of the author and do not necessarily represent those of the 
Company. Through this e-mail, no employee or agent is authorized to 
conclude/commit any new or incidental terms, which are not part of the original 
contract with the client or vendor, other than by way of duly executed and 
signed amendment contract between the parties in accordance with the agreed 
protocol of the contract. Please be aware that the Company monitors e-mail 
communications through our networks for regulatory compliance purposes. NIIT 
Technologies Limited and its related entities consider the privacy of its 
clients to be of utmost importance and works to protect it. The Privacy Policy 
of the Company can be accessed from our website www.niit-tech.com.
___
General mailing list
General@developer.marklogic.com
Manage your subscription at: 
http://developer.marklogic.com/mailman/listinfo/general

[MarkLogic Dev General] Query on fragmentation of xml document

[Reecha Bhandari]

Dear All,

We have xml files of this form wherein we have repetitive  node. Can you 
please guide as how I should fragment this xml file. I have posted question in 
stackoverflow and below is the link:

http://stackoverflow.com/questions/33229968/fragment-xml-files


NEWTAFDEFIGCAEIKBEIECJIAEBHHBFEIDJEJ750EAGGDJCBE3E8QWERTYUIOPLK12AIIDJPEOPLEGGICDPEOPLEAISSUERStrueHGE3E8QWERTYUIOPLK12HDEDKPEOPLEEEKIKPEOPLEAISSUERSAHDFIRSTNAMEDKISURNAME1970-08-04AHDDKIFIRSTNAMELASTNAMEIDSCHEMEEUIDC
 Test 
issuerUKEDEFIRSTNAMEEBESURNAME1970-08-04EDEEBEFIRSTNAMELASTNAMEIDSCHEMEEUIDE
 Test 
issuerXPRAUKFHAFIRSTNAMECFCSURNAME1970-08-04FHACFCFIRSTNAMELASTNAMEIDSCHEMEEUIDJ
 Test 
issuerfalse2015-05-18T01:12:05.864MTCH5523570.1892460XOFFDE000CR6Y4E4CASHDJBAPEOPLEFFDCPEOPLE




[cid:image003.png@01D10B28.978E5560]


Please Advice.


Thanks,
Reecha







DISCLAIMER

The information transmitted, including any attachments, is intended only for 
the person or entity to which it is addressed and may contain confidential 
and/or privileged material. Any form of reproduction, dissemination, copying, 
disclosure, modification, distribution and / or publication of this message 
without the prior written consent of the author of this e-mail is strictly 
prohibited. If you receive this email by mistake, please advise the sender and 
delete it immediately. Email transmission cannot be guaranteed to be secure, or 
error free as information could be intercepted, corrupted, lost or destroyed as 
a result of the transmission process. Views or opinions presented in this email 
are solely those of the author and do not necessarily represent those of the 
Company. Through this e-mail, no employee or agent is authorized to 
conclude/commit any new or incidental terms, which are not part of the original 
contract with the client or vendor, other than by way of duly executed and 
signed amendment contract between the parties in accordance with the agreed 
protocol of the contract. Please be aware that the Company monitors e-mail 
communications through our networks for regulatory compliance purposes. NIIT 
Technologies Limited and its related entities consider the privacy of its 
clients to be of utmost importance and works to protect it. The Privacy Policy 
of the Company can be accessed from our website www.niit-tech.com.
___
General mailing list
General@developer.marklogic.com
Manage your subscription at: 
http://developer.marklogic.com/mailman/listinfo/general

Re: [MarkLogic Dev General] Query on Fragmentation

[Aroul, Pavadai Durai (ELS-CON)]

Hi Justin,

I agree with you. I think fragmentation is not a good choice for my situation, 
since the document doesn’t have large logical sections.

I thought of using fragmentation for performance tuning purpose. But it doesn’t 
help.

Thanks,
Durai.

From: general-boun...@developer.marklogic.com 
[mailto:general-boun...@developer.marklogic.com] On Behalf Of Justin Makeig
Sent: Wednesday, September 16, 2015 5:58 PM
To: MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] Query on Fragmentation

The general rule of fragmentation is "Don't use fragmentation". It is a very 
sharp tool for a very specific use case, where you have large logical sections, 
like chapters, under a parent document. What we've found generally is that 
taking the time to model and split aggregated "fragments" into explicit 
documents is a better approach 9.9 times out of 10.

Can you say a little more about what you're trying to accomplish? What do your 
queries look like?

Justin

On Sep 16, 2015, at 3:30 AM, Pavadaidurai A 
mailto:pavadaidura...@infosys.com>> wrote:

Dear All,

I have taken the below example from Marklogic documentation. I have couple of 
questions reg Fragmentation. I understand from below example that “Citation”, 
will need to defined as the fragement root


1)  Assuming that we few other elements under CitationSet besides Citation 
element, what happens to the Misc elemens? In other words, if I am using 
Fragment root, what happens to the left over elements in the document?

2)  I understand that after setting Fragmentation rule, existing documents 
will remain unfragmented unless re-indexed (or re-loaded). Does 
xdmp:document-set-collection API, takes care of fragmenting the document. I am 
asking this question because xdmp:document-set-collection API internally 
rewrites the document into the database.

3)  Is there anyway to find out if a given document is fragmented or not?


citation1
citation2
citation3
citation4
citation5
misc1
misc2
misc3



Fragment Roots<https://docs.marklogic.com/guide/admin/fragments#id_34807>
If a document contains many instances of an XML structure that share a common 
element name, then these structures make sensible fragments. With MarkLogic 
Server, you can use this common element name as a fragment root.
The following diagram shows an XML document rooted at  that 
contains many instances of a  node. Each  node contains 
further XML and averages between 15K and 20K in size. Based on this 
information,  is a sensible element to use as a fragment root:



Thanks,
Durai.


 CAUTION - Disclaimer *

This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely

for the use of the addressee(s). If you are not the intended recipient, please

notify the sender by e-mail and delete the original message. Further, you are 
not

to copy, disclose, or distribute this e-mail or its contents to any other 
person and

any such actions are unlawful. This e-mail may contain viruses. Infosys has 
taken

every reasonable precaution to minimize this risk, but is not liable for any 
damage

you may sustain as a result of any virus in this e-mail. You should carry out 
your

own virus checks before opening the e-mail or attachment. Infosys reserves the

right to monitor and review the content of all messages sent to or from this 
e-mail

address. Messages sent to or from this e-mail address may be stored on the

Infosys e-mail system.

***INFOSYS End of Disclaimer INFOSYS***

___
General mailing list
General@developer.marklogic.com<mailto:General@developer.marklogic.com>
Manage your subscription at:
http://developer.marklogic.com/mailman/listinfo/general

___
General mailing list
General@developer.marklogic.com
Manage your subscription at: 
http://developer.marklogic.com/mailman/listinfo/general

Re: [MarkLogic Dev General] Query on Fragmentation

[Justin Makeig]

The general rule of fragmentation is "Don't use fragmentation". It is a very 
sharp tool for a very specific use case, where you have large logical sections, 
like chapters, under a parent document. What we've found generally is that 
taking the time to model and split aggregated "fragments" into explicit 
documents is a better approach 9.9 times out of 10.

Can you say a little more about what you're trying to accomplish? What do your 
queries look like?

Justin

> On Sep 16, 2015, at 3:30 AM, Pavadaidurai A  
> wrote:
> 
> Dear All,
>  
> I have taken the below example from Marklogic documentation. I have couple of 
> questions reg Fragmentation. I understand from below example that “Citation”, 
> will need to defined as the fragement root
>  
> 1)  Assuming that we few other elements under CitationSet besides 
> Citation element, what happens to the Misc elemens? In other words, if I am 
> using Fragment root, what happens to the left over elements in the document?
> 2)  I understand that after setting Fragmentation rule, existing 
> documents will remain unfragmented unless re-indexed (or re-loaded). Does 
> xdmp:document-set-collection API, takes care of fragmenting the document. I 
> am asking this question because xdmp:document-set-collection API internally 
> rewrites the document into the database.
> 3)  Is there anyway to find out if a given document is fragmented or not?
>  
> 
> citation1
> citation2
> citation3
> citation4
> citation5
> misc1
> misc2
> misc3
> 
>  
>  
> Fragment Roots 
> If a document contains many instances of an XML structure that share a common 
> element name, then these structures make sensible fragments. With MarkLogic 
> Server, you can use this common element name as a fragment root.
> 
> The following diagram shows an XML document rooted at  that 
> contains many instances of a  node. Each  node contains 
> further XML and averages between 15K and 20K in size. Based on this 
> information,  is a sensible element to use as a fragment root:
> 
> 
> 
>  
>  
> Thanks,
> Durai.
>  
>  CAUTION - Disclaimer *
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
> for the use of the addressee(s). If you are not the intended recipient, 
> please 
> notify the sender by e-mail and delete the original message. Further, you are 
> not 
> to copy, disclose, or distribute this e-mail or its contents to any other 
> person and 
> any such actions are unlawful. This e-mail may contain viruses. Infosys has 
> taken 
> every reasonable precaution to minimize this risk, but is not liable for any 
> damage 
> you may sustain as a result of any virus in this e-mail. You should carry out 
> your 
> own virus checks before opening the e-mail or attachment. Infosys reserves 
> the 
> right to monitor and review the content of all messages sent to or from this 
> e-mail 
> address. Messages sent to or from this e-mail address may be stored on the 
> Infosys e-mail system.
> ***INFOSYS End of Disclaimer INFOSYS***
> ___
> General mailing list
> General@developer.marklogic.com
> Manage your subscription at: 
> http://developer.marklogic.com/mailman/listinfo/general



smime.p7s
Description: S/MIME cryptographic signature
___
General mailing list
General@developer.marklogic.com
Manage your subscription at: 
http://developer.marklogic.com/mailman/listinfo/general

Re: [MarkLogic Dev General] Query on Fragmentation

[David Ennis]

HI.

You can always test the items in question in a small controlled experiment:

- new database, document without fragmenting
- look at the document count vs the fragment count in admin interface for
that document
- then do the collection step
- then look again. If the add collection step does what you expect, the
number of fragments would have increased.





Kind Regards,
David Ennis


David Ennis
*Content Engineer*

[image: HintTech]  <http://www.hinttech.com/>
Mastering the value of content
creative | technology | content

Delftechpark 37i
2628 XJ Delft
The Netherlands
T: +31 88 268 25 00
M: +31 63 091 72 80

[image: http://www.hinttech.com] <http://www.hinttech.com>
<https://twitter.com/HintTech>  <http://www.facebook.com/HintTech>
<http://www.linkedin.com/company/HintTech>

On 16 September 2015 at 13:51, Pavadaidurai A 
wrote:

> Hi Geert,
>
>
>
> Thanks for responding! For the questions No.2 , yes the re-indexer is
> disabled. We do fire xdmp:document-set-collection on these documents on a
> regular basis. So, I am just curious if this API will take care of
> fragmentation for existing documents, since it internally rewrites the
> whole document.
>
>
>
> Thanks,
>
> Durai.
>
>
>
> *From:* general-boun...@developer.marklogic.com [mailto:
> general-boun...@developer.marklogic.com] *On Behalf Of *Geert Josten
> *Sent:* Wednesday, September 16, 2015 4:19 PM
> *To:* MarkLogic Developer Discussion
> *Subject:* Re: [MarkLogic Dev General] Query on Fragmentation
>
>
>
> Hi Durai,
>
>
>
> Ad 1. There will always be a top-level fragment. Fragment root elements
> and their contents will be recorded as separate fragments. This works
> recursively, so a Citation in a Citation would get its own fragment, and
> the contents of the inner Citation would not be considered part of the same
> fragment.
>
> Ad 2. To my knowledge fragmentation changes are normally applied
> automatically by triggering a reindexation. Unless you have disabled that
> of course.
>
> Ad 3. There is a cts query that allows crossing fragment boundaries, but I
> don’t think you’d normally need that.
>
>
>
> Kind regards,
>
> Geert
>
>
>
> *From: * on behalf of
> Pavadaidurai A 
> *Reply-To: *MarkLogic Developer Discussion <
> general@developer.marklogic.com>
> *Date: *Wednesday, September 16, 2015 at 12:30 PM
> *To: *MarkLogic Developer Discussion 
> *Subject: *[MarkLogic Dev General] Query on Fragmentation
>
>
>
> Dear All,
>
>
>
> I have taken the below example from Marklogic documentation. I have couple
> of questions reg Fragmentation. I understand from below example that
> “Citation”, will need to defined as the fragement root
>
>
>
> 1)  Assuming that we few other elements under CitationSet besides
> Citation element, what happens to the Misc elemens? In other words, if I am
> using Fragment root, what happens to the left over elements in the document?
>
> 2)  I understand that after setting Fragmentation rule, existing
> documents will remain unfragmented unless re-indexed (or re-loaded). Does
> xdmp:document-set-collection API, takes care of fragmenting the document. I
> am asking this question because xdmp:document-set-collection API internally
> rewrites the document into the database.
>
> 3)  Is there anyway to find out if a given document is fragmented or
> not?
>
>
>
> 
>
> citation1
>
> citation2
>
> citation3
>
> citation4
>
> citation5
>
> misc1
>
> misc2
>
> misc3
>
> 
>
>
>
>
> Fragment Roots <https://docs.marklogic.com/guide/admin/fragments#id_34807>
>
> If a document contains many instances of an XML structure that share a
> common element name, then these structures make sensible fragments. With
> MarkLogic Server, you can use this common element name as a fragment root.
>
> The following diagram shows an XML document rooted at  that
> contains many instances of a  node. Each  node
> contains further XML and averages between 15K and 20K in size. Based on
> this information,  is a sensible element to use as a fragment
> root:
>
> [image:
> https://docs.marklogic.com/media/apidoc/8.0/guide/admin/fragments/fragments-1.gif]
>
>
>
>
>
> Thanks,
>
> Durai.
>
>
>
>  CAUTION - Disclaimer *
>
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
>
> for the use of the addressee(s). If you are not the intended recipient, please
>
> notify the sender by e-mail and delete the original message. Further, you are 
> not
>
> to copy, disclose, or distribute this e-mail or its contents to any other 
>

Re: [MarkLogic Dev General] Query on Fragmentation

[Pavadaidurai A]

Hi Geert,

Thanks for responding! For the questions No.2 , yes the re-indexer is disabled. 
We do fire xdmp:document-set-collection on these documents on a regular basis. 
So, I am just curious if this API will take care of fragmentation for existing 
documents, since it internally rewrites the whole document.

Thanks,
Durai.

From: general-boun...@developer.marklogic.com 
[mailto:general-boun...@developer.marklogic.com] On Behalf Of Geert Josten
Sent: Wednesday, September 16, 2015 4:19 PM
To: MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] Query on Fragmentation

Hi Durai,

Ad 1. There will always be a top-level fragment. Fragment root elements and 
their contents will be recorded as separate fragments. This works recursively, 
so a Citation in a Citation would get its own fragment, and the contents of the 
inner Citation would not be considered part of the same fragment.
Ad 2. To my knowledge fragmentation changes are normally applied automatically 
by triggering a reindexation. Unless you have disabled that of course.
Ad 3. There is a cts query that allows crossing fragment boundaries, but I 
don't think you'd normally need that.

Kind regards,
Geert

From: 
mailto:general-boun...@developer.marklogic.com>>
 on behalf of Pavadaidurai A 
mailto:pavadaidura...@infosys.com>>
Reply-To: MarkLogic Developer Discussion 
mailto:general@developer.marklogic.com>>
Date: Wednesday, September 16, 2015 at 12:30 PM
To: MarkLogic Developer Discussion 
mailto:general@developer.marklogic.com>>
Subject: [MarkLogic Dev General] Query on Fragmentation

Dear All,

I have taken the below example from Marklogic documentation. I have couple of 
questions reg Fragmentation. I understand from below example that "Citation", 
will need to defined as the fragement root


1)  Assuming that we few other elements under CitationSet besides Citation 
element, what happens to the Misc elemens? In other words, if I am using 
Fragment root, what happens to the left over elements in the document?

2)  I understand that after setting Fragmentation rule, existing documents 
will remain unfragmented unless re-indexed (or re-loaded). Does 
xdmp:document-set-collection API, takes care of fragmenting the document. I am 
asking this question because xdmp:document-set-collection API internally 
rewrites the document into the database.

3)  Is there anyway to find out if a given document is fragmented or not?


citation1
citation2
citation3
citation4
citation5
misc1
misc2
misc3



Fragment Roots<https://docs.marklogic.com/guide/admin/fragments#id_34807>

If a document contains many instances of an XML structure that share a common 
element name, then these structures make sensible fragments. With MarkLogic 
Server, you can use this common element name as a fragment root.

The following diagram shows an XML document rooted at  that 
contains many instances of a  node. Each  node contains 
further XML and averages between 15K and 20K in size. Based on this 
information,  is a sensible element to use as a fragment root:

[https://docs.marklogic.com/media/apidoc/8.0/guide/admin/fragments/fragments-1.gif]


Thanks,
Durai.


 CAUTION - Disclaimer *

This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely

for the use of the addressee(s). If you are not the intended recipient, please

notify the sender by e-mail and delete the original message. Further, you are 
not

to copy, disclose, or distribute this e-mail or its contents to any other 
person and

any such actions are unlawful. This e-mail may contain viruses. Infosys has 
taken

every reasonable precaution to minimize this risk, but is not liable for any 
damage

you may sustain as a result of any virus in this e-mail. You should carry out 
your

own virus checks before opening the e-mail or attachment. Infosys reserves the

right to monitor and review the content of all messages sent to or from this 
e-mail

address. Messages sent to or from this e-mail address may be stored on the

Infosys e-mail system.

***INFOSYS End of Disclaimer INFOSYS***


___
General mailing list
General@developer.marklogic.com
Manage your subscription at: 
http://developer.marklogic.com/mailman/listinfo/general

Re: [MarkLogic Dev General] Query on Fragmentation

[Geert Josten]

Hi Durai,

Ad 1. There will always be a top-level fragment. Fragment root elements and 
their contents will be recorded as separate fragments. This works recursively, 
so a Citation in a Citation would get its own fragment, and the contents of the 
inner Citation would not be considered part of the same fragment.
Ad 2. To my knowledge fragmentation changes are normally applied automatically 
by triggering a reindexation. Unless you have disabled that of course.
Ad 3. There is a cts query that allows crossing fragment boundaries, but I 
don’t think you’d normally need that.

Kind regards,
Geert

From: 
mailto:general-boun...@developer.marklogic.com>>
 on behalf of Pavadaidurai A 
mailto:pavadaidura...@infosys.com>>
Reply-To: MarkLogic Developer Discussion 
mailto:general@developer.marklogic.com>>
Date: Wednesday, September 16, 2015 at 12:30 PM
To: MarkLogic Developer Discussion 
mailto:general@developer.marklogic.com>>
Subject: [MarkLogic Dev General] Query on Fragmentation

Dear All,

I have taken the below example from Marklogic documentation. I have couple of 
questions reg Fragmentation. I understand from below example that “Citation”, 
will need to defined as the fragement root


1)  Assuming that we few other elements under CitationSet besides Citation 
element, what happens to the Misc elemens? In other words, if I am using 
Fragment root, what happens to the left over elements in the document?

2)  I understand that after setting Fragmentation rule, existing documents 
will remain unfragmented unless re-indexed (or re-loaded). Does 
xdmp:document-set-collection API, takes care of fragmenting the document. I am 
asking this question because xdmp:document-set-collection API internally 
rewrites the document into the database.

3)  Is there anyway to find out if a given document is fragmented or not?


citation1
citation2
citation3
citation4
citation5
misc1
misc2
misc3



Fragment Roots<https://docs.marklogic.com/guide/admin/fragments#id_34807>

If a document contains many instances of an XML structure that share a common 
element name, then these structures make sensible fragments. With MarkLogic 
Server, you can use this common element name as a fragment root.

The following diagram shows an XML document rooted at  that 
contains many instances of a  node. Each  node contains 
further XML and averages between 15K and 20K in size. Based on this 
information,  is a sensible element to use as a fragment root:

[https://docs.marklogic.com/media/apidoc/8.0/guide/admin/fragments/fragments-1.gif]


Thanks,
Durai.


 CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are 
not
to copy, disclose, or distribute this e-mail or its contents to any other 
person and
any such actions are unlawful. This e-mail may contain viruses. Infosys has 
taken
every reasonable precaution to minimize this risk, but is not liable for any 
damage
you may sustain as a result of any virus in this e-mail. You should carry out 
your
own virus checks before opening the e-mail or attachment. Infosys reserves the
right to monitor and review the content of all messages sent to or from this 
e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS End of Disclaimer INFOSYS***

___
General mailing list
General@developer.marklogic.com
Manage your subscription at: 
http://developer.marklogic.com/mailman/listinfo/general

[MarkLogic Dev General] Query on Fragmentation

[Pavadaidurai A]

Dear All,

I have taken the below example from Marklogic documentation. I have couple of 
questions reg Fragmentation. I understand from below example that "Citation", 
will need to defined as the fragement root


1)  Assuming that we few other elements under CitationSet besides Citation 
element, what happens to the Misc elemens? In other words, if I am using 
Fragment root, what happens to the left over elements in the document?

2)  I understand that after setting Fragmentation rule, existing documents 
will remain unfragmented unless re-indexed (or re-loaded). Does 
xdmp:document-set-collection API, takes care of fragmenting the document. I am 
asking this question because xdmp:document-set-collection API internally 
rewrites the document into the database.

3)  Is there anyway to find out if a given document is fragmented or not?


citation1
citation2
citation3
citation4
citation5
misc1
misc2
misc3



Fragment Roots

If a document contains many instances of an XML structure that share a common 
element name, then these structures make sensible fragments. With MarkLogic 
Server, you can use this common element name as a fragment root.

The following diagram shows an XML document rooted at  that 
contains many instances of a  node. Each  node contains 
further XML and averages between 15K and 20K in size. Based on this 
information,  is a sensible element to use as a fragment root:

[https://docs.marklogic.com/media/apidoc/8.0/guide/admin/fragments/fragments-1.gif]


Thanks,
Durai.


 CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are 
not
to copy, disclose, or distribute this e-mail or its contents to any other 
person and
any such actions are unlawful. This e-mail may contain viruses. Infosys has 
taken
every reasonable precaution to minimize this risk, but is not liable for any 
damage
you may sustain as a result of any virus in this e-mail. You should carry out 
your
own virus checks before opening the e-mail or attachment. Infosys reserves the
right to monitor and review the content of all messages sent to or from this 
e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS End of Disclaimer INFOSYS***
___
General mailing list
General@developer.marklogic.com
Manage your subscription at: 
http://developer.marklogic.com/mailman/listinfo/general