Re: [MarkLogic Dev General] Directory exists but xdmp:directory-delete return xdmp:doc-not-found

[Raghu]

BTW mine was a modify/update trigger that was one reason I didn't suspect
directory delete's behavior. But still it was on a directory and it starts
making sense now!! :)

On Tue, Nov 15, 2011 at 11:34 PM, Raghu wrote:

> No I didn't mean that way. Sorry no offence meant. My point is I suspected
> everything but triggers!
>
>
> On Tue, Nov 15, 2011 at 11:16 PM, Danny Sokolsky <
> danny.sokol...@marklogic.com> wrote:
>
>> I am not sure that is weird behavior.  If you have a delete trigger that
>> has a lot of work to do, for example, that would certainly impact the
>> performance of deletes.  So it all depends on the totality of what is going
>> on in your environment.
>>
>> ** **
>>
>> -Danny 
>>
>> ** **
>>
>> *From:* general-boun...@developer.marklogic.com [mailto:
>> general-boun...@developer.marklogic.com] *On Behalf Of *Raghu
>> *Sent:* Tuesday, November 15, 2011 9:43 AM
>>
>> *To:* General MarkLogic Developer Discussion
>> *Subject:* Re: [MarkLogic Dev General] Directory exists but
>> xdmp:directory-delete return xdmp:doc-not-found
>>
>> ** **
>>
>> Hey Danny,
>>
>> Seems that I'd set triggers to triggers database and this
>> was causing xdmp:directory-delete() not to work. Hope you had fixed this. I
>> would have never suspected that triggers would have such an impact. weird
>> behavior isn't it? 
>>
>> ** **
>>
>> Cheers
>>
>> Raghu
>>
>> On Tue, Oct 25, 2011 at 9:41 PM, Danny Sokolsky <
>> danny.sokol...@marklogic.com> wrote:
>>
>> Hi Raghu,
>>
>>  
>>
>> That sounds right because in 4.2, there were a number of inconsistencies
>> in the way MarkLogic handled directory and property deletes that were
>> fixed.  This was to support standalone properties (a property with no
>> corresponding document at the same URI).
>>
>>  
>>
>> You can use a combination of the URI lexicon (cts:uri-match) and
>> xdmp:document-delete to accomplish the same thing when you do not have the
>> directories in your database.  Something like (this is untested):
>>
>>  
>>
>> for $x in cts:uri-match(“/my/dir/*”)
>>
>> return
>>
>> xdmp:document-delete($x)
>>
>>  
>>
>> -Danny
>>
>>  
>>
>> *From:* general-boun...@developer.marklogic.com [mailto:
>> general-boun...@developer.marklogic.com] *On Behalf Of *Raghu
>> *Sent:* Tuesday, October 25, 2011 6:36 AM
>>
>>
>> *To:* General MarkLogic Developer Discussion
>>
>> *Subject:* Re: [MarkLogic Dev General] Directory exists but
>> xdmp:directory-delete return xdmp:doc-not-found
>>
>>  
>>
>>  
>>
>> HI Danny,
>>
>> 
>>
>> I tried the same in 4.2 version and even though there was no
>> property document for the directory, the directory gets deleted succesfully
>> but in 4.1 it throws a xdmp:doc-not -found. Am I right? is this the root
>> cause or am I missing something? Please help me out 
>>
>>  
>>
>> P.S: Sorry I'd given the version wrong in my previous mail, please ignore
>> it
>>
>>  
>>
>> Thanks in advance
>>
>> Raghu
>>
>>  
>>
>>
>>  
>>
>> On Tue, Oct 25, 2011 at 6:34 PM, Raghu 
>> wrote:
>>
>> HI Danny,
>>
>> 
>>
>> I tried the same in 4.1 version and even though there was no
>> property document for the directory, the directory gets deleted succesfully
>> but in 4.0 it throws a xdmp:doc-not -found. Am I right? is this the root
>> cause or am I missing something? Please help me out 
>>
>>  
>>
>> Thanks in advance
>>
>> Raghu
>>
>>  
>>
>> On Mon, Oct 24, 2011 at 10:25 PM, Danny Sokolsky <
>> danny.sokol...@marklogic.com> wrote:
>>
>> Hi Raghu,
>>
>>  
>>
>> I can think of 2 things to look at:
>>
>>  
>>
>>  
>>
>> 1)  Make sure the directory exists.  A directory is a properties
>> document with the special directory element.  Try running the following,
>> substituting the dir URI for $uri: 
>>
>>  
>>
>> xdmp:document-properties($uri)
>>
>>  
>>
>> this should return a properties document with a directory element.  If it
>> does not, then the directory does not exist.
>>
>>  
>>
>> 2)  Make sure the user who is running the directory-delete has
>> permissions to see the directory.   You can check that by looking at the
>> permissions on the directory: 
>>
>>  
>>
>> xdmp:document-get-permissions($uri)
>>
>>  
>>
>> Also, what version of marklogic are you running (xdmp:version() )?
>>
>>  
>>
>> -Danny
>>
>>  
>>
>>  
>>
>> *From:* general-boun...@developer.marklogic.com [mailto:
>> general-boun...@developer.marklogic.com] *On Behalf Of *Raghu
>> *Sent:* Monday, October 24, 2011 6:20 AM
>> *To:* General MarkLogic Developer Discussion
>> *Subject:* [MarkLogic Dev General] Directory exists but
>> xdmp:directory-delete return xdmp:doc-not-found
>>
>>  
>>
>> Hi All,
>>
>>  
>>
>>I'm  trying to delete a directory usind xdmp:directory-delete; it
>>

Re: [MarkLogic Dev General] Directory exists but xdmp:directory-delete return xdmp:doc-not-found

[Raghu]

No I didn't mean that way. Sorry no offence meant. My point is I suspected
everything but triggers!

On Tue, Nov 15, 2011 at 11:16 PM, Danny Sokolsky <
danny.sokol...@marklogic.com> wrote:

> I am not sure that is weird behavior.  If you have a delete trigger that
> has a lot of work to do, for example, that would certainly impact the
> performance of deletes.  So it all depends on the totality of what is going
> on in your environment.
>
> ** **
>
> -Danny 
>
> ** **
>
> *From:* general-boun...@developer.marklogic.com [mailto:
> general-boun...@developer.marklogic.com] *On Behalf Of *Raghu
> *Sent:* Tuesday, November 15, 2011 9:43 AM
>
> *To:* General MarkLogic Developer Discussion
> *Subject:* Re: [MarkLogic Dev General] Directory exists but
> xdmp:directory-delete return xdmp:doc-not-found
>
> ** **
>
> Hey Danny,
>
> Seems that I'd set triggers to triggers database and this
> was causing xdmp:directory-delete() not to work. Hope you had fixed this. I
> would have never suspected that triggers would have such an impact. weird
> behavior isn't it? 
>
> ** **
>
> Cheers
>
> Raghu
>
> On Tue, Oct 25, 2011 at 9:41 PM, Danny Sokolsky <
> danny.sokol...@marklogic.com> wrote:
>
> Hi Raghu,
>
>  
>
> That sounds right because in 4.2, there were a number of inconsistencies
> in the way MarkLogic handled directory and property deletes that were
> fixed.  This was to support standalone properties (a property with no
> corresponding document at the same URI).
>
>  
>
> You can use a combination of the URI lexicon (cts:uri-match) and
> xdmp:document-delete to accomplish the same thing when you do not have the
> directories in your database.  Something like (this is untested):
>
>  
>
> for $x in cts:uri-match(“/my/dir/*”)
>
> return
>
> xdmp:document-delete($x)
>
>  
>
> -Danny
>
>  
>
> *From:* general-boun...@developer.marklogic.com [mailto:
> general-boun...@developer.marklogic.com] *On Behalf Of *Raghu
> *Sent:* Tuesday, October 25, 2011 6:36 AM
>
>
> *To:* General MarkLogic Developer Discussion
>
> *Subject:* Re: [MarkLogic Dev General] Directory exists but
> xdmp:directory-delete return xdmp:doc-not-found
>
>  
>
>  
>
> HI Danny,
>
> 
>
> I tried the same in 4.2 version and even though there was no
> property document for the directory, the directory gets deleted succesfully
> but in 4.1 it throws a xdmp:doc-not -found. Am I right? is this the root
> cause or am I missing something? Please help me out 
>
>  
>
> P.S: Sorry I'd given the version wrong in my previous mail, please ignore
> it
>
>  
>
> Thanks in advance
>
> Raghu
>
>  
>
>
>  
>
> On Tue, Oct 25, 2011 at 6:34 PM, Raghu 
> wrote:
>
> HI Danny,
>
> 
>
> I tried the same in 4.1 version and even though there was no
> property document for the directory, the directory gets deleted succesfully
> but in 4.0 it throws a xdmp:doc-not -found. Am I right? is this the root
> cause or am I missing something? Please help me out 
>
>  
>
> Thanks in advance
>
> Raghu
>
>  
>
> On Mon, Oct 24, 2011 at 10:25 PM, Danny Sokolsky <
> danny.sokol...@marklogic.com> wrote:
>
> Hi Raghu,
>
>  
>
> I can think of 2 things to look at:
>
>  
>
>  
>
> 1)  Make sure the directory exists.  A directory is a properties
> document with the special directory element.  Try running the following,
> substituting the dir URI for $uri: 
>
>  
>
> xdmp:document-properties($uri)
>
>  
>
> this should return a properties document with a directory element.  If it
> does not, then the directory does not exist.
>
>  
>
> 2)  Make sure the user who is running the directory-delete has
> permissions to see the directory.   You can check that by looking at the
> permissions on the directory: 
>
>  
>
> xdmp:document-get-permissions($uri)
>
>  
>
> Also, what version of marklogic are you running (xdmp:version() )?
>
>  
>
> -Danny
>
>  
>
>  
>
> *From:* general-boun...@developer.marklogic.com [mailto:
> general-boun...@developer.marklogic.com] *On Behalf Of *Raghu
> *Sent:* Monday, October 24, 2011 6:20 AM
> *To:* General MarkLogic Developer Discussion
> *Subject:* [MarkLogic Dev General] Directory exists but
> xdmp:directory-delete return xdmp:doc-not-found
>
>  
>
> Hi All,
>
>  
>
>I'm  trying to delete a directory usind xdmp:directory-delete; it
> returns a   xdmp:doc-not-found but when I do a xdmp:directory of the same
> uri I'm able to see the documents inside the folder. These directories are
> created from a trigger. does it have anything to do with it? Should I set
> any document proerty? Please help me out.
>
>  
>
>  
>
>  
>
> Thanks in advance
>
> Raghu
>
>  
>
>  
>
> ___
> 

Re: [MarkLogic Dev General] Directory exists but xdmp:directory-delete return xdmp:doc-not-found

[Danny Sokolsky]

I am not sure that is weird behavior.  If you have a delete trigger that has a 
lot of work to do, for example, that would certainly impact the performance of 
deletes.  So it all depends on the totality of what is going on in your 
environment.

-Danny

From: general-boun...@developer.marklogic.com 
[mailto:general-boun...@developer.marklogic.com] On Behalf Of Raghu
Sent: Tuesday, November 15, 2011 9:43 AM
To: General MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] Directory exists but xdmp:directory-delete 
return xdmp:doc-not-found

Hey Danny,

Seems that I'd set triggers to triggers database and this was 
causing xdmp:directory-delete() not to work. Hope you had fixed this. I would 
have never suspected that triggers would have such an impact. weird behavior 
isn't it?

Cheers
Raghu
On Tue, Oct 25, 2011 at 9:41 PM, Danny Sokolsky 
mailto:danny.sokol...@marklogic.com>> wrote:
Hi Raghu,

That sounds right because in 4.2, there were a number of inconsistencies in the 
way MarkLogic handled directory and property deletes that were fixed.  This was 
to support standalone properties (a property with no corresponding document at 
the same URI).

You can use a combination of the URI lexicon (cts:uri-match) and 
xdmp:document-delete to accomplish the same thing when you do not have the 
directories in your database.  Something like (this is untested):

for $x in cts:uri-match("/my/dir/*")
return
xdmp:document-delete($x)

-Danny

From: 
general-boun...@developer.marklogic.com
 
[mailto:general-boun...@developer.marklogic.com]
 On Behalf Of Raghu
Sent: Tuesday, October 25, 2011 6:36 AM

To: General MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] Directory exists but xdmp:directory-delete 
return xdmp:doc-not-found


HI Danny,

I tried the same in 4.2 version and even though there was no 
property document for the directory, the directory gets deleted succesfully but 
in 4.1 it throws a xdmp:doc-not -found. Am I right? is this the root cause or 
am I missing something? Please help me out

P.S: Sorry I'd given the version wrong in my previous mail, please ignore it

Thanks in advance
Raghu




On Tue, Oct 25, 2011 at 6:34 PM, Raghu 
mailto:raghupathy.visweswa...@gmail.com>> 
wrote:
HI Danny,

I tried the same in 4.1 version and even though there was no 
property document for the directory, the directory gets deleted succesfully but 
in 4.0 it throws a xdmp:doc-not -found. Am I right? is this the root cause or 
am I missing something? Please help me out

Thanks in advance
Raghu

On Mon, Oct 24, 2011 at 10:25 PM, Danny Sokolsky 
mailto:danny.sokol...@marklogic.com>> wrote:
Hi Raghu,

I can think of 2 things to look at:



1)  Make sure the directory exists.  A directory is a properties document 
with the special directory element.  Try running the following, substituting 
the dir URI for $uri:

xdmp:document-properties($uri)

this should return a properties document with a directory element.  If it does 
not, then the directory does not exist.


2)  Make sure the user who is running the directory-delete has permissions 
to see the directory.   You can check that by looking at the permissions on the 
directory:

xdmp:document-get-permissions($uri)

Also, what version of marklogic are you running (xdmp:version() )?

-Danny


From: 
general-boun...@developer.marklogic.com
 
[mailto:general-boun...@developer.marklogic.com]
 On Behalf Of Raghu
Sent: Monday, October 24, 2011 6:20 AM
To: General MarkLogic Developer Discussion
Subject: [MarkLogic Dev General] Directory exists but xdmp:directory-delete 
return xdmp:doc-not-found

Hi All,

   I'm  trying to delete a directory usind xdmp:directory-delete; it 
returns a   xdmp:doc-not-found but when I do a xdmp:directory of the same uri 
I'm able to see the documents inside the folder. These directories are created 
from a trigger. does it have anything to do with it? Should I set any document 
proerty? Please help me out.



Thanks in advance
Raghu


___
General mailing list
General@developer.marklogic.com
http://developer.marklogic.com/mailman/listinfo/general



___
General mailing list
General@developer.marklogic.com
http://developer.marklogic.com/mailman/listinfo/general

___
General mailing list
General@developer.marklogic.com
http://developer.marklogic.com/mailman/listinfo/general

Re: [MarkLogic Dev General] Directory exists but xdmp:directory-delete return xdmp:doc-not-found

[Raghu]

Hey Danny,

Seems that I'd set triggers to triggers database and this
was causing xdmp:directory-delete() not to work. Hope you had fixed this. I
would have never suspected that triggers would have such an impact. weird
behavior isn't it?

Cheers
Raghu

On Tue, Oct 25, 2011 at 9:41 PM, Danny Sokolsky <
danny.sokol...@marklogic.com> wrote:

> Hi Raghu,
>
> ** **
>
> That sounds right because in 4.2, there were a number of inconsistencies
> in the way MarkLogic handled directory and property deletes that were
> fixed.  This was to support standalone properties (a property with no
> corresponding document at the same URI).
>
> ** **
>
> You can use a combination of the URI lexicon (cts:uri-match) and
> xdmp:document-delete to accomplish the same thing when you do not have the
> directories in your database.  Something like (this is untested):
>
> ** **
>
> for $x in cts:uri-match(“/my/dir/*”)
>
> return
>
> xdmp:document-delete($x)
>
> ** **
>
> -Danny
>
> ** **
>
> *From:* general-boun...@developer.marklogic.com [mailto:
> general-boun...@developer.marklogic.com] *On Behalf Of *Raghu
> *Sent:* Tuesday, October 25, 2011 6:36 AM
>
> *To:* General MarkLogic Developer Discussion
> *Subject:* Re: [MarkLogic Dev General] Directory exists but
> xdmp:directory-delete return xdmp:doc-not-found
>
> ** **
>
> ** **
>
> HI Danny,
>
> 
>
> I tried the same in 4.2 version and even though there was no
> property document for the directory, the directory gets deleted succesfully
> but in 4.1 it throws a xdmp:doc-not -found. Am I right? is this the root
> cause or am I missing something? Please help me out 
>
>  
>
> P.S: Sorry I'd given the version wrong in my previous mail, please ignore
> it
>
>  
>
> Thanks in advance
>
> Raghu
>
>  
>
>
>  
>
> On Tue, Oct 25, 2011 at 6:34 PM, Raghu 
> wrote:
>
> HI Danny,
>
> 
>
> I tried the same in 4.1 version and even though there was no
> property document for the directory, the directory gets deleted succesfully
> but in 4.0 it throws a xdmp:doc-not -found. Am I right? is this the root
> cause or am I missing something? Please help me out 
>
>  
>
> Thanks in advance
>
> Raghu
>
>  
>
> On Mon, Oct 24, 2011 at 10:25 PM, Danny Sokolsky <
> danny.sokol...@marklogic.com> wrote:
>
> Hi Raghu,
>
>  
>
> I can think of 2 things to look at:
>
>  
>
>  
>
> 1)  Make sure the directory exists.  A directory is a properties
> document with the special directory element.  Try running the following,
> substituting the dir URI for $uri: 
>
>  
>
> xdmp:document-properties($uri)
>
>  
>
> this should return a properties document with a directory element.  If it
> does not, then the directory does not exist.
>
>  
>
> 2)  Make sure the user who is running the directory-delete has
> permissions to see the directory.   You can check that by looking at the
> permissions on the directory: 
>
>  
>
> xdmp:document-get-permissions($uri)
>
>  
>
> Also, what version of marklogic are you running (xdmp:version() )?
>
>  
>
> -Danny
>
>  
>
>  
>
> *From:* general-boun...@developer.marklogic.com [mailto:
> general-boun...@developer.marklogic.com] *On Behalf Of *Raghu
> *Sent:* Monday, October 24, 2011 6:20 AM
> *To:* General MarkLogic Developer Discussion
> *Subject:* [MarkLogic Dev General] Directory exists but
> xdmp:directory-delete return xdmp:doc-not-found
>
>  
>
> Hi All,
>
>  
>
>I'm  trying to delete a directory usind xdmp:directory-delete; it
> returns a   xdmp:doc-not-found but when I do a xdmp:directory of the same
> uri I'm able to see the documents inside the folder. These directories are
> created from a trigger. does it have anything to do with it? Should I set
> any document proerty? Please help me out.
>
>  
>
>  
>
>  
>
> Thanks in advance
>
> Raghu
>
>  
>
> ** **
>
> ___
> General mailing list
> General@developer.marklogic.com
> http://developer.marklogic.com/mailman/listinfo/general
>
> ** **
>
> ** **
>
> ___
> General mailing list
> General@developer.marklogic.com
> http://developer.marklogic.com/mailman/listinfo/general
>
>
___
General mailing list
General@developer.marklogic.com
http://developer.marklogic.com/mailman/listinfo/general

Re: [MarkLogic Dev General] Decreased performance afterreindexing database in MarkLogic 3.2

[Damon Feldman]

Mariano,

Re-importing is often easier, but it depends on how fast your overall import 
process is, and if you have scripts or well-documented configuration steps to 
get your databases and app servers configured.

For any product and any version, including MarkLogic, it is a good idea to 
upgrade as part of a development cycle and run your complete suite of 
regression tests before you push to production. If possible, you should have a 
6-8 week testing cycle to allow time for a MarkLogic point release to come out 
if you do encounter a serious bug.

Also, every MarkLogic release has changes listed in the release notes that you 
should be aware of, and the MarkLogic 4.0 release had more than most, so you 
should review them and update your code if necessary. Some of these changes are 
actually bug fixes, but can alter the behavior of programs nonetheless.

Yours,
Damon

From: general-boun...@developer.marklogic.com 
[mailto:general-boun...@developer.marklogic.com] On Behalf Of Michael Sokolov
Sent: Tuesday, November 15, 2011 7:54 AM
To: General MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] Decreased performance afterreindexing 
database in MarkLogic 3.2

Don't you think it would be better to export all data and re-import, rather 
than go through 5 upgrade steps?

Also my impression was that Juan's question was about the advisability of 
moving to 5.0 considering that it's just out and may not be completely stable 
yet.  Juan -  it all depends on your appetite for risk, enthusiasm for new 
features, and willingness to do another upgrade (next year?).   You might want 
to go straight to 5.0, but it is definitely a fresh release, and likely to have 
a few point releases over the next year or so, some of which will include bug 
fixes, if past releases are any indication :)

-Mike

On 11/15/2011 1:46 AM, Geert Josten wrote:
Hi Mariano,

I believe the recommended route for such an upgrade would be to upgrade to the 
latest version within the 3.2 branch first, upgrade from there to the latest 
within the 4.0 branch, upgrade to 4.1, upgrade to 4.2, and then upgrade to 5.0. 
Obviously start off with a backup of your original 3.2 installation..

Kind regards,
Geert

Van: 
general-boun...@developer.marklogic.com
 
[mailto:general-boun...@developer.marklogic.com]
 Namens Mariano Grau Calín
Verzonden: maandag 14 november 2011 11:23
Aan: General MarkLogic Developer Discussion; General MarkLogic Developer 
Discussion
CC: Juan Aurelio Pecino Chacón
Onderwerp: Re: [MarkLogic Dev General] Decreased performance afterreindexing 
database in MarkLogic 3.2


Thanks,

We will undo changes to in-memory tree size and in-memory range index.
Also, will migrate as soon as posible. Do you recomended MarkLogic 5 (just 
released) or 4?


Mariano Grau
Dpto. Sistemas
Grupo Joly



-Mensaje original-
De: 
general-boun...@developer.marklogic.com
 en nombre de Michael Blakeley
Enviado el: dom 13/11/2011 23:29
Para: General MarkLogic Developer Discussion
CC: Juan Aurelio Pecino Chacón
Asunto: Re: [MarkLogic Dev General] Decreased performance afterreindexing   
database in MarkLogic 3.2

I can make a couple of observations that are valid for every version of 
MarkLogic Server to date:

* The changes to in-memory tree size and in-memory range index size were not a 
good idea. Higher limits mean larger in-memory stands, which will increase 
memory utilization. That is not likely to improve performance, and may well 
hurt performance. I would undo those changes.

* The increased database size and memory utilization probably indicate a large 
number of deleted fragments, which should be visible on the database status 
page. Merge the database to get rid of those.

3.2 is indeed very old now, and I would recommend upgrading as quickly as is 
practical. Note that upgrading will require more reindexing. So I would defer 
the full merge, recommended above, until after that upgrade is complete.

-- Mike

On 13 Nov 2011, at 12:32 , Eric Bloch wrote:

> I believe a formal end-of-life notice has been given for MarkLogic 3.2.
>
> -Eric
>
> Eric Bloch
> eric.bl...@marklogic.com
>
>
>
> On Nov 13, 2011, at 11:11 AM, Mariano Grau Calín wrote:
>
>> Hi all:
>>
>> We had to reindexing/refragmenting the database because searchs by trailing 
>> date not working.
>> The new documents was not indexed by date. After reindexing (the operation 
>> takes 40 hours), all works fine. However, searchs by text that previously 
>> took less than a second, now takes between five and ten seconds. Also, 
>> database size increased 30 GB.
>>
>> The database has 12,5 millions documents and 140 GB in two forests. Run on 
>> hp DL385 AMD 64bits Quad Core 2,2 Ghz, 16 GB RAM and one disk 250 GB raid 1 
>> on EVA8000. The operating system is Windows 2003 Standard Edition SP2 a

Re: [MarkLogic Dev General] Decreased performance afterreindexing database in MarkLogic 3.2

[Michael Sokolov]

Don't you think it would be better to export all data and re-import, 
rather than go through 5 upgrade steps?


Also my impression was that Juan's question was about the advisability 
of moving to 5.0 considering that it's just out and may not be 
completely stable yet.  Juan -  it all depends on your appetite for 
risk, enthusiasm for new features, and willingness to do another upgrade 
(next year?).   You might want to go straight to 5.0, but it is 
definitely a fresh release, and likely to have a few point releases over 
the next year or so, some of which will include bug fixes, if past 
releases are any indication :)


-Mike

On 11/15/2011 1:46 AM, Geert Josten wrote:


Hi Mariano,

I believe the recommended route for such an upgrade would be to 
upgrade to the latest version within the 3.2 branch first, upgrade 
from there to the latest within the 4.0 branch, upgrade to 4.1, 
upgrade to 4.2, and then upgrade to 5.0. Obviously start off with a 
backup of your original 3.2 installation..


Kind regards,

Geert

*Van:*general-boun...@developer.marklogic.com 
 
[mailto:general-boun...@developer.marklogic.com 
] *Namens *Mariano 
Grau Calín

*Verzonden:* maandag 14 november 2011 11:23
*Aan:* General MarkLogic Developer Discussion; General MarkLogic 
Developer Discussion

*CC:* Juan Aurelio Pecino Chacón
*Onderwerp:* Re: [MarkLogic Dev General] Decreased performance 
afterreindexing database in MarkLogic 3.2


Thanks,

We will undo changes to in-memory tree size and in-memory range index.
Also, will migrate as soon as posible. Do you recomended MarkLogic 5 
(just released) or 4?



Mariano Grau
Dpto. Sistemas
Grupo Joly



-Mensaje original-
De: general-boun...@developer.marklogic.com 
 en nombre de Michael 
Blakeley

Enviado el: dom 13/11/2011 23:29
Para: General MarkLogic Developer Discussion
CC: Juan Aurelio Pecino Chacón
Asunto: Re: [MarkLogic Dev General] Decreased performance 
afterreindexing   database in MarkLogic 3.2


I can make a couple of observations that are valid for every version 
of MarkLogic Server to date:


* The changes to in-memory tree size and in-memory range index size 
were not a good idea. Higher limits mean larger in-memory stands, 
which will increase memory utilization. That is not likely to improve 
performance, and may well hurt performance. I would undo those changes.


* The increased database size and memory utilization probably indicate 
a large number of deleted fragments, which should be visible on the 
database status page. Merge the database to get rid of those.


3.2 is indeed very old now, and I would recommend upgrading as quickly 
as is practical. Note that upgrading will require more reindexing. So 
I would defer the full merge, recommended above, until after that 
upgrade is complete.


-- Mike

On 13 Nov 2011, at 12:32 , Eric Bloch wrote:

> I believe a formal end-of-life notice has been given for MarkLogic 3.2.
>
> -Eric
>
> Eric Bloch
> eric.bl...@marklogic.com 
>
>
>
> On Nov 13, 2011, at 11:11 AM, Mariano Grau Calín wrote:
>
>> Hi all:
>>
>> We had to reindexing/refragmenting the database because searchs by 
trailing date not working.
>> The new documents was not indexed by date. After reindexing (the 
operation takes 40 hours), all works fine. However, searchs by text 
that previously took less than a second, now takes between five and 
ten seconds. Also, database size increased 30 GB.

>>
>> The database has 12,5 millions documents and 140 GB in two forests. 
Run on hp DL385 AMD 64bits Quad Core 2,2 Ghz, 16 GB RAM and one disk 
250 GB raid 1 on EVA8000. The operating system is Windows 2003 
Standard Edition SP2 and MarkLogic Server 3.2.

>>
>> We modified parameters database for improving performance, now 
Marklogic process in memory is 12 GB (before 9,5GB), with not sucess.

>> BeforeAfter
>> in memory limit 5242881048576
>> in memory list size 1024  1024 (máx.)
>> in memory tree size 256   1024
>> in memory range index size  1664 (máx.)
>>
>>
>> We hope to improve the performance without to buy new hardware and 
licens.

>>
>> Thanks and regards,
>>
>>
>> Mariano Grau
>> Dpto. Systems
>> Grupo Joly
>>
>>
>>
>> ___
>> General mailing list
>> General@developer.marklogic.com 
>> http://developer.marklogic.com/mailman/listinfo/general
>
> ___
> General mailing list
> General@developer.marklogic.com 
> http://developer.marklogic.com/mailman/listinfo/general

___
General mailing list
General@developer.marklogic.com 
http://devel

Re: [MarkLogic Dev General] Retrieving file name/document URI of binary content

[Lee, David]

functions can return sequences to xcc.
try this as a simple example and build on

declare function module:test()
{
[ 1 to 10 ] ,  "HI" , 
}



David A. Lee
Senior Principal Software Engineer
Epocrates, Inc.
d...@epocrates.com
812-482-5224

From: general-boun...@developer.marklogic.com 
[mailto:general-boun...@developer.marklogic.com] On Behalf Of Amar Wakkar
Sent: Tuesday, November 15, 2011 5:59 AM
To: general@developer.marklogic.com
Subject: Re: [MarkLogic Dev General] Retrieving file name/document URI of 
binary content

Yes it does in an .xqy page or in query console.

Now I am trying to get it to work inside XCC Java code but it does not work as 
it is in AdhocQuery class.

Can we get multiple results out from a module which has this piece of code? 
Function can return just single value so that may not work in this case?


Thanks
Amaresh Wakkar

> From: kelly.stir...@marklogic.com
> To: general@developer.marklogic.com
> Date: Mon, 14 Nov 2011 14:25:05 -0800
> Subject: Re: [MarkLogic Dev General] Retrieving file name/document URI of 
> binary content
>
> This works just fine for me on ML5:
>
> let$d := 
> xdmp:document-get("http://www.gotdogsonline.com/chinese-foo-dog-pictures-breeders-puppies-rescue/pictures-photos/chinese-foo-dog-0001.jpg";)
> return
> xdmp:document-insert("/foo.jpg",$d);
> for $i in collection()
> return ($i/document-uri(.),$i)
>
> -Original Message-
> From: general-boun...@developer.marklogic.com 
> [mailto:general-boun...@developer.marklogic.com] On Behalf Of 
> general-requ...@developer.marklogic.com
> Sent: Monday, November 14, 2011 4:28 PM
> To: general@developer.marklogic.com
> Subject: General Digest, Vol 89, Issue 53
>
> Send General mailing list submissions to
> general@developer.marklogic.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://developer.marklogic.com/mailman/listinfo/general
> or, via email, send a message with subject or body 'help' to
> general-requ...@developer.marklogic.com
>
> You can reach the person managing the list at
> general-ow...@developer.marklogic.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of General digest..."
>
>
> Today's Topics:
>
> 1. Re: Retrieving file name/document URI of binary content
> (Amar Wakkar)
>
>
> --
>
> Message: 1
> Date: Mon, 14 Nov 2011 21:27:39 +
> From: Amar Wakkar 
> Subject: Re: [MarkLogic Dev General] Retrieving file name/document URI
> of binary content
> To: 
> Message-ID: 
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> Hello David,
> I tried but no joy...still giving same error about binary nodes not being 
> allowed in element node.
> for $uri in collection("user10")/document-uri(.)return ( $uri , doc($uri) )
> Interestingly, when I created a collection of just text and xml contents both 
> of your suggestions work so the issue is definitely with the binary data and 
> the way it is queried/represented in Marklogic.
> It may sound a silly question, but when I stored a binary image in Marklogic 
> collection along with a document-uri then should there not be some way e.g. 
> Metadata about the resultset which should tell me what is the associated URI 
> for this content when it was stored in Marklogic? It just happened to be a 
> binary image file but should that matter as far as retrieving a document-uri 
> is concerned? It is just a name used to store the data in database, if I can 
> retrieve that name for an XML or TXT file then why not for Binary image?
> ThanksAmaresh Wakkar
> From: d...@epocrates.com
> To: general@developer.marklogic.com
> Date: Mon, 14 Nov 2011 21:09:36 +
> Subject: Re: [MarkLogic Dev General] Retrieving file name/document URI of 
> binary content
>
>
>
>
>
>
>
>
>
>
>
> I still dont understand why this doesnt work:
>
> for $x in collection("user10")
> return
> ( fn:document-uri($x) , $x )
>
>
> But you can always try
>
>
> for $uri in
> collection("user10")/document-uri(.)
> return ( $uri , doc($uri) )
>
>
> 
> David A. Lee
> Senior Principal Software Engineer
> Epocrates, Inc.
> d...@epocrates.com
> 812-482-5224
>
>
>
>
> From: general-boun...@developer.marklogic.com 
> [mailto:general-boun...@developer.marklogic.com]
> On Behalf Of Amar Wakkar
>
> Sent: Monday, November 14, 2011 3:53 PM
>
> To: general@developer.marklogic.com
>
> Subject: Re: [MarkLogic Dev General] Retrieving file name/document URI of 
> binary content
>
>
>
>
>
> Thanks!!!
>
>
>
>
>
> The dot definitely made the difference.. I can now query the content and 
> document-uri in separate queries, but it would have been great if I could
> just fetch them together in single query like other experts pointed out:
>
>
>
>
>
> More importantly, if I query these two separately, is there a guarantee that 
> they will come in correct order everytime? I mean t

Re: [MarkLogic Dev General] Retrieving file name/document URI of binary content

[Amar Wakkar]

Yes it does in an .xqy page or in query console.
Now I am trying to get it to work inside XCC Java code but it does not work as 
it is in AdhocQuery class. 
Can we get multiple results out from a module which has this piece of code? 
Function can return just single value so that may not work in this case?

Thanks Amaresh Wakkar

> From: kelly.stir...@marklogic.com
> To: general@developer.marklogic.com
> Date: Mon, 14 Nov 2011 14:25:05 -0800
> Subject: Re: [MarkLogic Dev General] Retrieving file name/document URI of 
> binary content
> 
> This works just fine for me on ML5:
> 
> let$d := 
> xdmp:document-get("http://www.gotdogsonline.com/chinese-foo-dog-pictures-breeders-puppies-rescue/pictures-photos/chinese-foo-dog-0001.jpg";)
> return
> xdmp:document-insert("/foo.jpg",$d);
> for $i in collection()
> return ($i/document-uri(.),$i)
> 
> -Original Message-
> From: general-boun...@developer.marklogic.com 
> [mailto:general-boun...@developer.marklogic.com] On Behalf Of 
> general-requ...@developer.marklogic.com
> Sent: Monday, November 14, 2011 4:28 PM
> To: general@developer.marklogic.com
> Subject: General Digest, Vol 89, Issue 53
> 
> Send General mailing list submissions to
>   general@developer.marklogic.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   http://developer.marklogic.com/mailman/listinfo/general
> or, via email, send a message with subject or body 'help' to
>   general-requ...@developer.marklogic.com
> 
> You can reach the person managing the list at
>   general-ow...@developer.marklogic.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of General digest..."
> 
> 
> Today's Topics:
> 
>1. Re: Retrieving file name/document URI of binary content
>   (Amar Wakkar)
> 
> 
> --
> 
> Message: 1
> Date: Mon, 14 Nov 2011 21:27:39 +
> From: Amar Wakkar 
> Subject: Re: [MarkLogic Dev General] Retrieving file name/document URI
>   of binary content
> To: 
> Message-ID: 
> Content-Type: text/plain; charset="iso-8859-1"
> 
> 
> Hello David,
> I tried but no joy...still giving same error about binary nodes not being 
> allowed in element node.
> for $uri in collection("user10")/document-uri(.)return ( $uri , doc($uri) )
> Interestingly, when I created a collection of just text and xml contents both 
> of your suggestions work so the issue is definitely with the binary data and 
> the way it is queried/represented in Marklogic.
> It may sound a silly question, but when I stored a binary image in Marklogic 
> collection along with a document-uri then should there not be some way e.g. 
> Metadata about the resultset which should tell me what is the associated URI 
> for this content when it was stored in Marklogic? It just happened to be a 
> binary image file but should that matter as far as retrieving a document-uri 
> is concerned? It is just a name used to store the data in database, if I can 
> retrieve that name for an XML or TXT file then why not for Binary image?
> ThanksAmaresh Wakkar
> From: d...@epocrates.com
> To: general@developer.marklogic.com
> Date: Mon, 14 Nov 2011 21:09:36 +
> Subject: Re: [MarkLogic Dev General] Retrieving file name/document URI of 
> binary content
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> I still dont understand why this doesnt work:
>  
>  for $x in collection("user10")
> return
> ( fn:document-uri($x) , $x )
>  
>  
> But you can always try
>
> 
> for $uri in
> collection("user10")/document-uri(.)
> return ( $uri , doc($uri) )
>  
> 
> 
> David A. Lee
> Senior Principal Software Engineer
> Epocrates, Inc.
> d...@epocrates.com
> 812-482-5224
> 
>  
> 
> 
> From: general-boun...@developer.marklogic.com 
> [mailto:general-boun...@developer.marklogic.com]
> On Behalf Of Amar Wakkar
> 
> Sent: Monday, November 14, 2011 3:53 PM
> 
> To: general@developer.marklogic.com
> 
> Subject: Re: [MarkLogic Dev General] Retrieving file name/document URI of 
> binary content
> 
> 
>  
> 
> 
> Thanks!!!
> 
> 
>  
> 
> 
> The dot definitely made the difference.. I can now query the content and 
> document-uri in separate queries, but it would have been great if I could
>  just fetch them together in single query like other experts pointed out:
> 
> 
>  
> 
> 
> More importantly, if I query these two separately, is there a guarantee that 
> they will come in correct order everytime? I mean the image name at position
>  1 will always correspond to image-1 retrieved in a separate query for that 
> collection?
> 
> 
>  
> 
> 
> If it all was fetched in single query then these issues would not have come, 
> is it not?
> 
> 
>  
> 
> 
> Of course there is one way to do it i.e. a nested query. Get the file 
> names/document-uris and then get the documents but that will be more than 2
>  calls to Marklogic, I think.
> 
> 
>  
> 
> 
> Thanks
> 
> 
>  
> 
> 
> Amaresh