Well, we know for sure that an external can output a very large
response, so I suggest comparing couchdb-lucene's code to your own and
see what's different.
If you hop on #couchdb sometime, I'm sure we could track the bug down.
B.
On Fri, Nov 20, 2009 at 3:02 AM, Jim Woodgate jdwo...@gmail.com
Sadly I can't access chat from work, is there a log I can check to see
exactly what it's choking on? When I run the program by hand I get
one line that looks like this (though it's all on one line):
{code : 200,headers : {Content-Type : text/plain},json :
{numRows : 60,rows :
Bah problem solved sorry to bother everyone, I made a really bad
assumption that it would just run my program one time, I see now that
it is starting my program once and expecting it to stay up. (this
will also greatly simplify my code for handling partial search
results)
On Fri, Nov 20, 2009 at
I finally have a basic external program running, but I find that if I
return 57 ids it works, but if I return 58 ids or more I get an error.
Is there a way to tell what the actual error is? The text that comes
back says:
{error_info,
{exit,
{exit_status,0},
Did you emit your JSON response on a single line?
On Thu, Nov 19, 2009 at 10:42 PM, Jim Woodgate jdwo...@gmail.com wrote:
I finally have a basic external program running, but I find that if I
return 57 ids it works, but if I return 58 ids or more I get an error.
Is there a way to tell what
On Thu, Nov 19, 2009 at 5:10 PM, Robert Newson robert.new...@gmail.com wrote:
Did you emit your JSON response on a single line?
Yes it's all one line.
On Thu, Nov 19, 2009 at 10:42 PM, Jim Woodgate jdwo...@gmail.com wrote:
I finally have a basic external program running, but I find that if I
