Document transfer size restrictions

[Rob Pettefar <rp...@gpslsolutions.com>]

  Hi again guys
Got a bit of a conundrum here:
We have been trying to pull out data from the database but it has failed 
with the error
"InternalError: script stack space quota is exhausted"
We have been doing fine with documents of about 80 to 90 kb in size. 
However we now have documents in the region of 300 to 400 kb now. We are 
using a key filtered view to get the specific document we need.
Using a web browser to access the data using the view and key has been 
successful though.
I am not entirely convinced that CouchDB would limit the return size of 
data to a matter of KBs.

Had a look through the documentation for this but all I could find was 
something on Futon being limited by JSON document sizes.

Any ideas?
Rob
-- 

GPSL Logo

	



*      Robert Pettefar *

/  t /   +44 1793 344191
/ m /   +44 7900 263799

Re: Document transfer size restrictions

[Justin Walgran <jw...@azavea.com>]

Rob,

My team was getting this error when loading a big view result via an AJAX
call from the browser, but in our experience it is exclusive to Firefox 3 on
Ubuntu 10. Have you tried your request in another browser or OS?


Justin

On Thu, Feb 17, 2011 at 4:10 AM, Rob Pettefar
<rp...@gpslsolutions.com>wrote:

>  Hi again guys
> Got a bit of a conundrum here:
> We have been trying to pull out data from the database but it has failed
> with the error
> "InternalError: script stack space quota is exhausted"
> We have been doing fine with documents of about 80 to 90 kb in size.
> However we now have documents in the region of 300 to 400 kb now. We are
> using a key filtered view to get the specific document we need.
> Using a web browser to access the data using the view and key has been
> successful though.
> I am not entirely convinced that CouchDB would limit the return size of
> data to a matter of KBs.
>
> Had a look through the documentation for this but all I could find was
> something on Futon being limited by JSON document sizes.
>
> Any ideas?
> Rob
> --
>
>
>
>
>
>  [image: GPSL Logo]
>
>
>
> *      Robert Pettefar *
>
>  *  t  *   +44 1793 344191
>  * m *   +44 7900 263799
>
>
>
>
>
>
>
>
>
>
>

Re: Document transfer size restrictions

[Rob Pettefar <rp...@gpslsolutions.com>]

  It appears this issue was being caused by another module we had 
running alongside CouchDB
This is a non-issue for couch.

On 17/02/2011 09:10, Rob Pettefar wrote:
> Hi again guys
> Got a bit of a conundrum here:
> We have been trying to pull out data from the database but it has 
> failed with the error
> "InternalError: script stack space quota is exhausted"
> We have been doing fine with documents of about 80 to 90 kb in size. 
> However we now have documents in the region of 300 to 400 kb now. We 
> are using a key filtered view to get the specific document we need.
> Using a web browser to access the data using the view and key has been 
> successful though.
> I am not entirely convinced that CouchDB would limit the return size 
> of data to a matter of KBs.
>
> Had a look through the documentation for this but all I could find was 
> something on Futon being limited by JSON document sizes.
>
> Any ideas?
> Rob
> -- 

Re: Document transfer size restrictions

[Kristian Rink <ka...@googlemail.com>]

Folks;

Am Thu, 17 Feb 2011 09:10:03 +0000
schrieb Rob Pettefar <rp...@gpslsolutions.com>:

> Got a bit of a conundrum here:
> We have been trying to pull out data from the database but it has
> failed with the error
> "InternalError: script stack space quota is exhausted"

Can't really offer help on that but just throw in a "me-too", as I ran
into this a while ago as well. Used to play with an application to rip
file metadata off actual files (using the aperture framework) and throw
metadata content into documents, including the "full text" dump
aperture does provide in example while dealing with PDF files. Working
with such documents on a "naked" Couch worked pretty smoothly (GET,
POST, ...), yet futon failed to show them exactly because of the error
you also ran into... Failed to hunt it down by now, though, resolved
this by moving the "large" text stuff into attachments...

Cheers,
K.