Use xdmp:plan to see why your query was slow.
xdmp:plan(/transaction/*[@transInfoRef eq "ti1"])
<qry:final-plan>
<qry:and-query>
<qry:term-query weight="0">
<qry:key>5327439496900942259</qry:key>
<qry:annotation>descendant(doc-root(element(transaction),doc-kind(document))
)</qry:annotation>
</qry:term-query>
</qry:and-query>
</qry:final-plan>
Notice how there's no mention of 'ti1' in the plan? That's because `*[@foo eq
'bar']` isn't resolvable using the indexes.
Don't use '*'. Specify element names, like `/transaction/a[@b eq $value]` or
`/transaction/(a|b|c)[@transInfoRef eq "ti1"]`.
-- Mike
On 21 Aug 2014, at 06:52 , irisDeveloper <developerati...@gmail.com> wrote:
> I split my 1GB xml file and stored in MarkLogic. I faced two issues
>
> 1) it took huge amount of time in hrs. (used MLCP import)
> 2) After spliting and loading activity My ML DB has 10,150,005 documents
> and has occupied 20GB of disk space.
>
> I fired the query again /transaction/*[@transInfoRef eq "ti1"]
> query console gave time out exception.
_______________________________________________
General mailing list
General@developer.marklogic.com
http://developer.marklogic.com/mailman/listinfo/general
