I think in recent versions of ML it's the case that calling merge won¹t
necessarily merge right down to 0 deleted fragments?
But anyway, you shouldn¹t see deleted fragments in queries. It¹s more
likely because all the tests run in one transaction. Are you using the
setup/teardown annotations in xray to insert/delete? The general pattern
is like this:
declare %test:setup insert-data()
{
xdmp:document-insert('foo.xml', <foo/>)
};
declare %test:teardown delete-data()
{
xdmp:document-delete('foo.xml')
};
declare %test:case should-see-foo()
{
assert:true(fn:doc-available('foo.xml'))
};
From: Geert Josten <[email protected]>
Reply-To: MarkLogic Developer Discussion <[email protected]>
Date: Monday, 13 July 2015 13:55
To: MarkLogic Developer Discussion <[email protected]>
Subject: Re: [MarkLogic Dev General] element-word-match
That should disappear once below merge completes. Perhaps give it time to
finish by adding a xdmp:sleep somewhere..
Cheers
From: <[email protected]> on behalf of Andreas
Hubmer <[email protected]>
Reply-To: MarkLogic Developer Discussion <[email protected]>
Date: Monday, July 13, 2015 at 2:46 PM
To: MarkLogic Developer Discussion <[email protected]>
Subject: Re: [MarkLogic Dev General] element-word-match
Hi Geert,
Thanks for your fast reply.
Unfortunately, xdmp:merge does not make a difference.
In the Administration UI I can see that 1 deleted fragment gets added
every time I run the unit test.
Cheers,
Andreas
2015-07-13 14:13 GMT+02:00 Geert Josten
<[email protected]>:
Hi Andreas,
I suspect DOC-A is still among the deleted fragments, and if you run
certain (unfiltered?) queries as an admin user, you could see results from
deleted documents. Try running this in between to see if that makes a
difference:
xdmp:merge(
<options xmlns="xdmp:merge">
<merge-timestamp>{xdmp:request-timestamp()}</merge-timestamp>
</options>)
Cheers,
Geert
From: <[email protected]> on behalf of Andreas
Hubmer <[email protected]>
Reply-To: MarkLogic Developer Discussion <[email protected]>
Date: Monday, July 13, 2015 at 2:00 PM
To: MarkLogic Developer Discussion <[email protected]>
Subject: [MarkLogic Dev General] element-word-match
Hi,
In a unit test (using xray) I insert a document DOC-A and delete it
afterwards. The administration UI shows afterwards that the database
contains 0 documents.
Afterwards (in another unit test) I use cts:element-word-match for
auto-completion purposes. Now I have the strange issue that
cts:element-word-match returns values even though my database is empty.
The values it returns are from DOC-A. To me it seems
that the document got deleted but its values were not properly removed
from the element word lexicon.
Even waiting for 10 minutes didn't help.
As I understand it this should not happen.
Is there something I miss?
The reindexer is enabled on the database. Manually calling "merge" on the
database's only forest doesn't help. Disabling and enabling the forest
doesn't help either. Only calling "clear" on the forest helps to get rid
of the wrong lexicon values.
I can consistently reproduce the problem.
I am using MarkLogic 8.0-2.
Best regards,
Andreas
--
Andreas Hubmer
IT Consultant
EBCONT enterprise technologies GmbH
Millennium Tower
Handelskai 94-96
A-1200 Vienna
Email:
[email protected] <mailto:[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
--
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] <mailto:[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
