Re: [MarkLogic Dev General] batch delete

I think the new manage REST api would be helpful here, but you could also have a look at Roxy (https://github.com/marklogic/roxy). It allows Œwiping¹ arbitrary forests, databases, and servers. It is designed to wipe things in the correct order, so you could put all in a single command. Something

[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

Re: [MarkLogic Dev General] element-word-match

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

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 geert.jos...@marklogic.com: Hi Andreas,

Re: [MarkLogic Dev General] Can node libraries be installed server-side?

Thanks, Erik. It helped me get in the right frame of mind when thinking critically on where certain ingestion logic should reside. And thanks for digging into the example of node-xslx and pointing out that it's async built on an underlying sync library. I definitely looked at the binary extract

Re: [MarkLogic Dev General] element-word-match

On Mon, Jul 13, 2015 at 9:30 AM, Andreas Hubmer andreas.hub...@ebcont.com 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

Re: [MarkLogic Dev General] element-word-match

Deleted fragments are only visible to admin, as security is bypassed for that user. That also gives you a slight performance gain. As a general rule of thumb, never run tests as admin.. Cheers, Geert From: general-boun...@developer.marklogic.commailto:general-boun...@developer.marklogic.com

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: general-boun...@developer.marklogic.commailto:general-boun...@developer.marklogic.com on behalf of Andreas Hubmer

Re: [MarkLogic Dev General] element-word-match

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. But anyway, you shouldn¹t see deleted fragments in queries. It¹s

Re: [MarkLogic Dev General] element-word-match

Regarding merge and not flushing all deleted fragments, passing in request timestamp is supposed to fix that: xdmp:merge( options xmlns=xdmp:merge merge-timestamp{xdmp:request-timestamp()}/merge-timestamp /options) Cheers From:

Re: [MarkLogic Dev General] element-word-match

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

Re: [MarkLogic Dev General] element-word-match

I can’t tell exactly either, but your observations could be right that it only occurs with word and value lexicon lookups. Those start with values, and only look at fragments later (if you provide a cts:query for instance). A cts:search starts with fragments, so easier to ignore deleted

[MarkLogic Dev General] mlcp.sh help with filtering to ingest only XML files in zip files

Dear all, We need help in ingesting a directory of many* zip files, each with many* XML files. We are using the mlcp (Mark Logic Content Pump) out of the box to import content as-is from a directory of zip files. In particular, we are using these options: -mode local \ -input_file_path [a

Re: [MarkLogic Dev General] element-word-match

Can you elaborate on Deleted fragments are only visible to admin ? In what case are deleted fragments visible to the admin? So far I haven't seen deleted fragments in query results, except for the lexicon lookup with cts:element-word-match. In two additional tests I've just seen that * words of

Re: [MarkLogic Dev General] mlcp.sh help with filtering to ingest only XML files in zip files

Addendum: We actually send this regular expression, to escape the dot, yet mlcp.sh import still does not filter our desired files -input_file_pattern '.*\.xml' From: Morales-Martin, Kristina Sent: Monday, July 13, 2015 11:43 AM To: 'general@developer.marklogic.com' Subject: mlcp.sh help with

Re: [MarkLogic Dev General] element-word-match

I don't think that it should make a difference running as admin. I think that used to be the case but it has worked that way for quite a while. Andreas, do you have a simple test case you can share that shows this? Thanks, -Danny From: general-boun...@developer.marklogic.com

[MarkLogic Dev General] search chinese word can not work when used wildcard query

some node of xml document is: product dept=ACC tmp=哈哈 number563/number name language=enFloppy Sun Hat/name /product the language of attribute tmp is chinese. the query : cts:search(collection()/catalog/product,