xdmp:merge with
<merge-timestamp>{xdmp:request-timestamp()}</merge-timestamp> does not make
a difference on my local Windows machine. Afterwards there are still
deleted fragments in the database.
I've also tested it on a Linux cluster and there xdmp:merge with
<merge-timestamp>{xdmp:request-timestamp()}</merge-timestamp> does indeed
remove the deleted fragments. Afterwards cts:element-word-match returns the
expected empty list.
Nevertheless I am surprised that cts:element-word-match returns values from
deleted fragments.
Cheers,
Andreas
2015-07-13 15:42 GMT+02:00 Christopher Hamlin <[email protected]>:
> On Mon, Jul 13, 2015 at 9:30 AM, Andreas Hubmer
> <[email protected]> wrote:
> > Hi,
> >
> >> I think in recent versions of ML it's the case that calling merge won¹t
> >> necessarily merge right down to 0 deleted fragments?
> > Yes, that seems to be the case. Even long after calling xdmp:merge the
> > deleted fragments exist.
>
> It won't normally discard deleted fragments right away:
>
>
> https://help.marklogic.com/Knowledgebase/Article/View/193/0/unable-to-merge-all-deleted-fragments-on-forest-with-32gb-max-merge-size
> _______________________________________________
> General mailing list
> [email protected]
> Manage your subscription at:
> http://developer.marklogic.com/mailman/listinfo/general
>
--
Andreas Hubmer
IT Consultant
EBCONT enterprise technologies GmbH
Millennium Tower
Handelskai 94-96
A-1200 Vienna
Mobile: +43 664 60651861
Fax: +43 2772 512 69-9
Email: [email protected]
Web: http://www.ebcont.com
OUR TEAM IS YOUR SUCCESS
UID-Nr. ATU68135644
HG St.Pölten - FN 399978 d
_______________________________________________
General mailing list
[email protected]
Manage your subscription at:
http://developer.marklogic.com/mailman/listinfo/general
