t
> Sent: Thursday, March 18, 2010 9:34 AM
> To: General Mark Logic Developer Discussion
> Subject: RE: [MarkLogic Dev General] "Hot Swapping" large data sets.
>
> Another way to allow you to load and update sets and then only make them
> visible when you are done i
:48 AM
To: General Mark Logic Developer Discussion
Subject: RE: [MarkLogic Dev General] "Hot Swapping" large data sets.
The URI privilege does not control access to the document, it specifies whether
you can create a document in that URI space.
You can do what Keith suggests b
ark Logic Developer Discussion
Subject: RE: [MarkLogic Dev General] "Hot Swapping" large data sets.
Another way to allow you to load and update sets and then only make them
visible when you are done is to load the content with a unique URI privilege
that is assigned to your loader/enricher
er.marklogic.com
[mailto:general-boun...@developer.marklogic.com] On Behalf Of Jason Hunter
Sent: Thursday, March 18, 2010 12:10 AM
To: General Mark Logic Developer Discussion
Subject: Re: [MarkLogic Dev General] "Hot Swapping" large data sets.
On Mar 17, 2010, at 5:23 AM, Lee, David wrote:
I need t
On Mar 17, 2010, at 5:23 AM, Lee, David wrote:
> I need to be updating some largish (1G+) sets of documents fairly atomically.
> That is, I'd like to update all the documents and perform some operations
> like adding properties etc,
> then all at once make the updates visible. The update proces
;
>
> *From:* general-boun...@developer.marklogic.com [mailto:
> general-boun...@developer.marklogic.com] *On Behalf Of *Wayne Feick
> *Sent:* Wednesday, March 17, 2010 3:54 PM
> *To:* General Mark Logic Developer Discussion
> *Subject:* Re: [MarkLogic Dev General] "Hot Swapp
PM
To: General Mark Logic Developer Discussion
Subject: Re: [MarkLogic Dev General] "Hot Swapping" large data sets.
I'd suggest looking into collections or directories to constrain queries to one
set or the other such that one is the live set you're serving up and the other
ion
Subject: Re: [MarkLogic Dev General] "Hot Swapping" large data sets.
I'd suggest looking into collections or directories to constrain queries to one
set or the other such that one is the live set you're serving up and the other
is the set you're updating.
You might
I'd suggest looking into collections or directories to constrain queries
to one set or the other such that one is the live set you're serving up
and the other is the set you're updating.
You might also consider using the Library Services API where the updates
operate on the most recent version of
