Hi Ian,
I found your question perfectly clear (though I may have been the only
one). The way to achieve this is as I described, write a new external
handler and add it to couchdb. For comparison, couchdb-lucene uses a
Python script
was restarted? Is
there any way of knowing how long it's been up for?
Martin
On 25 Apr 2012, at 14:00, Robert Newson wrote:
Have you seen /_stats ?
B.
On 25 April 2012 13:57, Martin Hewitt mar...@thenoi.se wrote:
Hi all,
We're in the process of adding a load of instrumentation to our
-d is the data mangling option. Use --data-binary or, better, -T filename
B.
On 26 April 2012 15:37, Paulo Carvalho pjcarva...@gmail.com wrote:
Hello,
I have a json file, which I think is valid, with the following content:
{docs:[{comm:Taille éoyenne pour les structures -- Échantillons :
A few things are happening here;
1) URL dispatching on the front port (5984) is done in code, not the
configuration file.
2) couchdb-lucene doesn't yet understand the new BigCouch 0.4 update
sequence format (I will have a word with the author).
B.
On 26 April 2012 16:38, Martin Hewitt
Point 2 is fixed.
On 26 April 2012 17:08, Robert Newson rnew...@apache.org wrote:
A few things are happening here;
1) URL dispatching on the front port (5984) is done in code, not the
configuration file.
2) couchdb-lucene doesn't yet understand the new BigCouch 0.4 update
sequence format (I
Newson wrote:
Point 2 is fixed.
On 26 April 2012 17:08, Robert Newson rnew...@apache.org wrote:
A few things are happening here;
1) URL dispatching on the front port (5984) is done in code, not the
configuration file.
2) couchdb-lucene doesn't yet understand the new BigCouch 0.4 update
and test again. I'm assuming I have to install and configure
couchdb-lucene identically on all nodes?
Martin
On 26 Apr 2012, at 22:39, Robert Newson wrote:
I can reproduce it. You have not brought up a full cluster, right?
Local docs don't have quorum, so the attempt to make _local/lucene
Paulo,
What encoding is your file stored in? My suggestion applies only if
it's already in UTF-8 encoding (-d would mangle that but --data-binary
or -T would not). I think it's clear that the file is not stored in
UTF-8 encoding (I'm guessing iso-8859-1 btw) so you'll need to convert
it as dch
Have you seen this?
http://wiki.apache.org/couchdb/Replication#Replicator_database
B.
On 27 April 2012 11:03, Daniel Gonzalez gonva...@gonvaled.com wrote:
Hello,
I will describe my problem in a general way. If more details are needed, I
will try to gather them from my production
From http://wiki.apache.org/couchdb/Formatting_with_Show_and_List:
The request and response objects are of the same format used by
_external functions, as documented in [[ExternalProcesses]].
As http://wiki.apache.org/couchdb/ExternalProcesses documents, the req
object has a userCtx member.
B.
Views are sorted by their full key and provide efficient lookup of a
single row or a single slice. When using startkey and endkey, couchdb
will return all rows equal to or greater than startkey that are also
less than endkey.
Array key ordering is defined as compared element by element until
Hi Rory,
Yes, it should be possible and you appear to be using correct syntax
(assuming your sort parameter is actually reaching the couchdb-lucene
server). What results are you getting? What version of couchdb-lucene
are you using? If you try the query again and add debug=true, you
should get
. Testing this with other fields works
like a charm. Sorry for wasting your time!
Rory
On Friday, 4 May 2012 at 12:05, Robert Newson wrote:
Hi Rory,
Yes, it should be possible and you appear to be using correct syntax
(assuming your sort parameter is actually reaching the couchdb
done.
On 6 May 2012 19:22, Simon de boer sdeb...@ingamer.com wrote:
Hi,
Could I (SimonDeBoer) be added to the wiki please?
In particular I would like to add some information to the
Update Handlers page to reference the X-Couch-Update-NewRev header
which took awhile to find and I think
_utils is a futon url (an admin application that ships with couch),
not a couchdb url.
http://host:port/testdb/_all_docs?include_docs=true
B.
On 9 May 2012 17:35, d...@danmyersconsulting.com wrote:
Bryan/others,
Using the following I get a list of the documents:
the partial update feature would have the same semantics as a
document updated mediated by an update handler anyway, though more
efficient (no need to call javascript when the transformation function
is defined).
B.
On 10 May 2012 08:24, Alon Keren alon.ke...@gmail.com wrote:
Compared to the
(moving this to user@)
You need to change the database_dir, and index_dir properties under
[couchdb] in local.ini as this is where couchdb looks to find where it
should write data. You can either edit the files and restart couchdb
or you can do it via http (e.g, curl -X PUT
{error, eacces} is pointing to a file permission error. It looks like
the user that couchdb is running as does not have permission to create
the _users database.
B.
On 10 May 2012 16:45, Mike Kimber mkim...@kana.com wrote:
Hi,
Were on Couchdb 1.2 and in couch.log we have the following
-Original Message-
From: Robert Newson [mailto:rnew...@apache.org]
Sent: 10 May 2012 16:56
To: user@couchdb.apache.org
Subject: Re: Couchdb 1.2 crash_report in log file every 4 secounds - why?
{error, eacces} is pointing to a file permission error. It looks like
the user
Hi Mike,
I just verified the Index Everything snippet at
https://github.com/rnewson/couchdb-lucene locally, it worked fine for
me. Perhaps you missed off a character when you pasted it into futon?
B.
On 16 May 2012 21:20, Mike Kimber mkim...@kana.com wrote:
Ive built/installed couch-lucene and
This just means couchdb-lucene has encountered a document that doesn't
have a headers element. In general you should add guard clauses
anyway;
function(doc) {
if (doc.headers doc.headers.core doc.headers.core.user) {
var res = new Document();
res.add( doc.headers.core.user );
Nope, you just had to escape the embedded double quote since you're
inside a string already.
B.
On 17 May 2012 08:33, Mike Kimber mkim...@kana.com wrote:
Nope I had to change attachment to 'attachment'
Mike
-Original Message-
From: Robert Newson [mailto:rnew...@apache.org]
Sent
Very nice! But perhaps you could note that 1.3 will switch from the
simple SHA1 scheme to PBKDF2 with configurable work factor?
B.
On 20 May 2012 21:27, Miles Pomeroy pomeroymi...@gmail.com wrote:
I wrote a post about the new features in 1.2.0. Check it out and let
me know if there are any
Hi Cory,
The simple answer is that compaction is an intense process (it reads
the latest versions of all documents and writes them to a new file)
and that your production system appears to have been spec'ed without
testing it with user load and compaction load.
Making compaction more manageable
I think we check for the cookie first. Just don't send it when you
'send a request as user2'.
B.
On 23 May 2012 18:27, Gregor Martynus gre...@martynus.net wrote:
Hey couch folks,
let's say there is a database user2, which has Readers: [user2] in its
security settings.
Now let's say user1
That sounds ok as a workaround, but what you're doing, obviously, is
sending authentication details for two different users. You can't
depend on every couchdb server evaluating them in an order that lets
you get away with that.
I don't understand your assertion that you can't control the requests
Or use a list function;
http://wiki.apache.org/couchdb/Formatting_with_Show_and_List
You can use one with _all_docs and you can POST an array of ids too.
http://wiki.apache.org/couchdb/HTTP_view_API
Since 0.9 you can also issue POST requests to views where you can send the
following JSON
-Original Message-
From: Robert Newson [mailto:rnew...@apache.org]
Sent: 24 May 2012 12:08
To: user@couchdb.apache.org
Subject: Re: Am I doing something fundamentally wrong?
Or use a list function;
http://wiki.apache.org/couchdb/Formatting_with_Show_and_List
You can use one with _all_docs
solve the
issue (although it would seem 10 big couch nodes would still take an hour)
Looks like you work at Cloudant, so hopefully you might be able to provide
some answers based on real world experience?
Mike
-Original Message-
From: Robert Newson [mailto:rnew...@apache.org
I can't think of a solid objection to this idea. The result of a
validate_doc_update can already vary based on the local security
object. Being able to inspect not only the new document, but any other
property of the request seems useful.
B.
On 25 May 2012 12:43, Luca Matteis lmatt...@gmail.com
http://jersey.576304.n2.nabble.com/Is-Jersey-Jersey-client-duplicating-requests-td6570645.html
On 26 May 2012 13:26, Robert Newson rnew...@apache.org wrote:
Jersey can use either the JDK's http client or Apache HttpClient,
which are you using?
I know that the Apache HttpClient will resubmit
Jersey can use either the JDK's http client or Apache HttpClient,
which are you using?
I know that the Apache HttpClient will resubmit requests under some
conditions (and you can disable it).
http://hc.apache.org/httpcomponents-client-ga/tutorial/html/fundamentals.html#d5e281
The default retry
Hi Patrick,
Logical OR is straightforward in couchdb views, Martin Higman's answer
shows how to do that (though I suggest you don't emit the full doc
into your view, emit null as the value instead and use
include_docs=true).
The other suggestions are techniques that would apply if you were
by a firewall instead, though.
B.
On 28 May 2012 14:03, Benoit Chesneau bchesn...@gmail.com wrote:
On Fri, May 25, 2012 at 1:49 PM, Robert Newson rnew...@apache.org wrote:
I can't think of a solid objection to this idea. The result of a
validate_doc_update can already vary based on the local
That looks like file corruption to me. CouchDB is attempting to walk
the by_seq tree to update your new view and finds it cannot decode
what it's reading from your database. What OS/filesystem/hardware is
this? Have you previously run out of disk space on the machine in
question? Anything else you
May 2012 14:38, Simon Metson si...@cloudant.com wrote:
Hi,
On Monday, 28 May 2012 at 14:12, Robert Newson wrote:
The other proposal might be to allow the granting of
rights by IP address, much as MySQL does. In fact, I believe this idea
is part of the Summit proposal to enhance our security
.
Martin
On 28 May 2012, at 14:42, Robert Newson wrote:
That looks like file corruption to me. CouchDB is attempting to walk
the by_seq tree to update your new view and finds it cannot decode
what it's reading from your database. What OS/filesystem/hardware is
this? Have you previously run out
: no_db_file
}
Martin
On 28 May 2012, at 14:57, Robert Newson wrote:
You specifically read the changes feed for
shards/-5554/rock_events.1334876515 on the node that
logged the error to completion?
B.
On 28 May 2012 14:54, Martin Hewitt mar...@thenoi.se wrote:
Hi Robert
hm, you're quite sure you were on the right node?
On 28 May 2012 15:23, Martin Hewitt mar...@thenoi.se wrote:
Hi Robert,
I can load that _changes feed no problem, I get 200 OK with the full response.
Martin
On 28 May 2012, at 15:18, Robert Newson wrote:
http://host:5986/shards%2f
account and re-vote for that item. This defeats the purpose of the
voting system.
My solution would be to check based on the IP of the voter, no matter
what user they're logged in with.
Does this make sense? Thanks.
On Mon, May 28, 2012 at 3:50 PM, Robert Newson rnew...@apache.org wrote:
I
the replicator runs as _admin.
On 28 May 2012 23:12, Luca Matteis lmatt...@gmail.com wrote:
On Mon, May 28, 2012 at 11:52 PM, Paul Davis
paul.joseph.da...@gmail.com wrote:
This would be nice but not every replication request happens through
the HTTP layer. Local replications have no notion of
http://wiki.apache.org/couchdb/HTTP_Document_API#Standalone_Attachments
It's quite easy (and efficient) to stream large attachments in and out
of couchdb. What difficulty are you having?
B.
On 31 May 2012 09:02, Nils Breunese n.breun...@vpro.nl wrote:
Op 29 mei 2012, om 17:50 heeft Googcheng
Yep, you can use show and list functions from foreign design documents;
http://wiki.apache.org/couchdb/Formatting_with_Show_and_List
I appreciate the inconvenience of a design document having a single
language, there are underlying architectural reasons for that but
perhaps there's a useful
Are you sure couchdb's startup script isn't su'ing to a different
user, though?
On 31 May 2012 16:22, CGS cgsmcml...@gmail.com wrote:
Dear lists,
I recently installed CouchDB 1.2.0 from source on CentOS 5.8 (final) with
Erlang/OTP R15B01 (installed from source with no errors at installation).
cgsmcml...@gmail.com wrote:
Very sure as I am logged in as root when I start CouchDB (the same terminal
session I used for make install which worked without any error).
CGS
On Thu, May 31, 2012 at 5:33 PM, Robert Newson rnew...@apache.org wrote:
Are you sure couchdb's startup script isn't
CouchDB only remembers the last 1000 _rev values by default (even
after compaction). The reason it remembers past _rev values at all is
so we can determine common ancestry when merging due to replication.
The reason we cut off at 1000 is to avoid the unbounded storage
problem of keeping them all.
You can increase that timeout with;
curl -XPUT localhost:5984/_config/couchdb/os_process_timeout -d '6'
B.
On 5 June 2012 12:18, Robert Newson rnew...@apache.org wrote:
Sounds like https://issues.apache.org/jira/browse/COUCHDB-994
B.
On 5 June 2012 11:07, Sami Sierla sami.sie
is periodically re-triggered by our java application so the
views will get eventually finished after multiple resumes.
Regards,
Sami
On Jun 5, 2012, at 2:20 PM, Robert Newson wrote:
You can increase that timeout with;
curl -XPUT localhost:5984/_config/couchdb/os_process_timeout -d '6
The signature for validate_doc_update is;
(newDoc, oldDoc, userCtx, secObj)
The request is not exposed (and thus you can't find the IP of the client).
B.
On 7 June 2012 15:25, Pulkit Singhal pulkitsing...@gmail.com wrote:
I would like to add an additional field to incoming documents in the
Sure, the built-in _sum reduce function works for lists of numbers too.
B.
On 11 Jun 2012, at 11:29, Rory Franklin wrote:
Hi,
Is it possible to have a view that emits out something like the following:
(key1, [1,1,0,1])
(key1, [1,1,1,0])
(key1, [1,0,0,0])
(key2, [0,1,0,0])
which can
The alarms can be ignored, they're a side-effect of a new feature in couchdb
that monitors disk consumption.
The test suite failures below look like the usual ones caused by browser cache
issues. Clear your cache and try again.
B.
On 11 Jun 2012, at 11:39, laurie.tur...@talktalk.net wrote:
-d will load the whole file into memory and also interpret it as ascii, which
might make it invalid.
use -T filename instead.
B.
On 11 Jun 2012, at 12:29, Mohammad Prabowo wrote:
Hi. I need to do bulk-insert of document in my CouchDB database.
I'm trying to follow the manual here:
why not use a show or list function that removes that field?
B.
On 12 June 2012 01:37, Jens Alfke j...@couchbase.com wrote:
On Jun 11, 2012, at 4:29 PM, bryan rasmussen wrote:
Does couchdb have some sort of higher level way of doing this that
will have better performance than just looping
in the view and then emitting the doc?
I don't know why it would work, but I don't know why it wouldn't
either. Just an idea.
-zh
On Mon, Jun 11, 2012 at 8:45 PM, Robert Newson rnew...@apache.org wrote:
why not use a show or list function that removes that field?
B.
On 12 June 2012 01
* is not correct.
To bind to all interfaces use 0.0.0.0
B.
On 12 June 2012 16:49, Shea Doug (Nokia-LC/Chicago) doug.s...@nokia.comwrote:
Hey folks. I’m setting up my first CouchDB instance for an internal
project, and am running into an error on start-up. I was wondering if
anybody could
CouchDB's ACID properties apply at the single document level for this
reason (among others). The replicator has some parallelism and so the
order of updates on the target will not always match that of the
source. There is also no transaction around a replication process (by
design). Another reason
Do you eventually delete every document you add?
If so, consider using a rolling database scheme instead. At some
point, perhaps daily, start a new database and write new transaction
logs there. Continue deleting old logs from the previous database(s)
until they're empty (doc_count:0) and then
, Jun 14, 2012 at 2:54 PM, Robert Newson rnew...@apache.org
wrote:
Do you eventually delete every document you add?
If so, consider using a rolling database scheme instead. At some
point, perhaps daily, start a new database and write new transaction
logs there. Continue deleting old logs
above is really a coping mechanism for
using the wrong tool.
B.
On 14 June 2012 15:47, Robert Newson rnew...@apache.org wrote:
The scheme I suggest avoids compaction entirely, which I thought was
your main struggle.
You still need to delete the documents in the old database so that you
can detect
to use
compaction or auto-compaction (as in 1.2.0). What would be the best
schedule? Trigger it a lot, or trigger it as less as possible (while still
making sure I have enough disk). And what if I use the strict_window?
On Thu, Jun 14, 2012 at 4:49 PM, Robert Newson rnew...@apache.org wrote
emfile means you've run out of file descriptors.
B.
On 19 June 2012 09:59, Dave Cottlehuber d...@muse.net.nz wrote:
On 19 June 2012 10:02, Niels Boldt nielsbo...@gmail.com wrote:
Hi
Couchdb 1.2.0 on ubuntu 12.04 stopped responding. Its build using
https://github.com/iriscouch/build-couchdb
Hi,
You could look at our twig project (https://github.com/cloudant/twig). We use
this to make CouchDB send its log information to a remote syslog server, which
is what I presume you meant rather that directing data to /var/log/syslog.
Further, you should *not* tell couchdb to write to
Hi Rory,
It seems the default for numeric fields change to exclude norms by default
between the version of Lucene used between 0.7 and 0.9;
SOLR-3140: https://issues.apache.org/jira/browse/SOLR-3140
File a ticket at https://github.com/rnewson/couchdb-lucene/issues, if you
supply a patch it'll
anyway, I fixed it.
You'll need to delete the index already built, though, and I'd love to hear
back from you when you try it.
B.
On 20 Jun 2012, at 12:05, Rory Franklin wrote:
Hi,
We've got a machine with couchdb-lucene 0.9 on it and various machines that
use 0.7 and there seems to be
for :)
From: Robert Newson [rnew...@apache.org]
Sent: Wednesday, June 20, 2012 6:04 PM
To: user@couchdb.apache.org
Subject: Re: CouchDB log to Syslog
Hi,
You could look at our twig project (https://github.com/cloudant/twig). We use
this to make CouchDB
isn't
taking effect or that my query doesn't manually boost that field?
Rory
On Wednesday, 20 June 2012 at 13:21, Robert Newson wrote:
anyway, I fixed it.
You'll need to delete the index already built, though, and I'd love to hear
back from you when you try it.
B.
On 20 Jun
Do GET /dbname and the return JSON blob should have the current sequence under
the update_seq key.
B.
On 20 Jun 2012, at 17:30, Daniel Gonzalez wrote:
Hello,
I am subscribing to the _changes API. My database is quite big, and each
time I restart my client, I get all old notifications. I
Do you get a 200 when you GET that same doc id? I suspect you get a 404. If so,
check you have the right id, perhaps you need to escape some fields. Better,
try deleting it from Futon which handles the escaping for you.
If you're deleting an admin user, then you need to modify your .ini files
The replicator is just a client, so if your validate_doc_update doesn't allow
it to update, it won't be able to update.
That said, 401 means you failed to pass a valid user:pass combination. You
failed to *authenticate*, though the standard description of 401 is notoriously
misleading.
B.
CouchDB doesn't have a cache unless you mean that it has an open file
descriptor on that file (which, obviously, would not be affected by the removal
of a hard link). All the effects you've noticed seem to follow naturally from
POSIX filesystem semantics.
CouchDB is a database server and
If you're running continuous replication, then the process isn't going to reach
100% (since that would imply all future changes have been replicated, which is
clearly impossible). I suspect it's just a reporting anomaly. I didn't reply
earlier because I hadn't had time to verify the code but
The extra debug information isn't helpful. What we actually need is the rest of
the Reason for termination.
I suspect the returned binary is shorter than the number of bytes we expected
to read but I can't confirm that from a partial log. If that turns out to be
the case then it's one of two
2012 at 18:45, Robert Newson wrote:
Do you get a 200 when you GET that same doc id? I suspect you get a 404. If
so, check you have the right id, perhaps you need to escape some fields.
Better, try deleting it from Futon which handles the escaping for you.
If you're deleting an admin
for you?
I'm on couchDB 1.2, tested locally and on IrisCouch
--
Gregor Martynus
On Wednesday, 20. June 2012 at 18:45, Robert Newson wrote:
Do you get a 200 when you GET that same doc id? I suspect you get a 404. If
so, check you have the right id, perhaps you need to escape some
a 404 as well. Is that not the
case for you?
I'm on couchDB 1.2, tested locally and on IrisCouch
--
Gregor Martynus
On Wednesday, 20. June 2012 at 18:45, Robert Newson wrote:
Do you get a 200 when you GET that same doc id? I suspect you get a 404. If
so, check you have
eacces indicates a file permission problem.
On 29 Jun 2012, at 07:03, Martin Hewitt wrote:
eacces
It should, yes. Mochi *does* but there have been some spots in our handling
where we misbehaved. If there *are* bugs, I would really like to squish them.
On 1 Jul 2012, at 15:10, Jens Alfke wrote:
Does the HTTP server in CouchDB [MochiWeb?] support HTTP pipelining? I'd like
to enable it in
This could be a bug, could you report it our jira at
issues.apache.org/jira/browse/COUCHDB?
It appears to be down right now, le sigh, but should be back soon.
B.
On 2 Jul 2012, at 14:27, Antonino Murador wrote:
Hi,
I notice a behaviour of the update_notification process that I cannot
I'd love to hear if IrisCouch is slower an a micro EC2 instance, I'd be
astonished. Using a micro for anything serious, like a production database, is
penny wise, pound foolish imo.
B.
On 2 Jul 2012, at 18:28, Douglas Turner wrote:
Hello
Let's see if I can articulate this sufficiently.
Hi Thomas,
The JSON encoder/decoder changed between 1.1 and 1.2. Both of the results you
show are valid JSON (and equivalent). If you could describe the processing
problems you encountered, perhaps we can help more.
B.
On 3 Jul 2012, at 13:41, thomas.b...@ptb.de wrote:
Dear list,
we have
I mean that both results are the same. \u00e4 is the same as ä. You'll notice
that the rev value is the same regardless of which is displayed, and the rev
is calculated from all the bytes of the document. Therefore, we can conclude
that the doc is byte-for-byte identical. The only thing that
Both forms are valid Unicode (in UTF-8 encoding). The character in question can
be represented directly or as a unicode escape sequence. Both answers are
correct and equivalent.
B.
On 3 Jul 2012, at 16:16, Marten Feldtmann wrote:
From http://www.ietf.org/rfc/rfc4627.txt:
...
JSON text
I should note that BC (and cloudant.com, even more so) generally contain more
than the advertised couchdb release.
On 4 Jul 2012, at 14:11, Simon Metson wrote:
IIRC it's currently built of v1.0.2
On Wednesday, 4 July 2012 at 13:49, Gabriel Mancini wrote:
Hi Guys any one knows if
BigCouch will be merged into CouchDB this year, and merging the 1.1.1-1.2
changes is an important part of that.
B.
On 4 Jul 2012, at 14:55, Gabriel Mancini wrote:
Thanks. U know if Will BE a update and when?
Em 04/07/2012 10:12, Simon Metson si...@cloudant.com escreveu:
IIRC it's
This sounds like COUCHDB-1415
(https://issues.apache.org/jira/browse/COUCHDB-1415). Did you sometimes compact
while testing?
B.
On 5 Jul 2012, at 00:12, Matt Cheers wrote:
OK.
Formatting will get ugly but you'll be able to re-produce this just by
running the .sh script. In running this
Remember that the erlang view server has no sandbox (an erlang map function can
do anything, read/write/delete files, open sockets, etc)
B.
On 5 Jul 2012, at 18:50, Albin Stigö wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I had completely forgotten it's possible to write
Yes, you'll need to enable term vectors, add
{termvector:with_positions_offsets} to the your add call or tweak the
defaults object for the index for all fields.
B.
On 6 Jul 2012, at 18:52, Michael Bykov wrote:
Hi,
I add in pom.file
dependency
That's a bit strange, couchdb shouldn't be sending duplicate keys. Do you go
through the Python script? You can see what couchdb-lucene sees if you query
GET /dbname/_changes?feed=continuousinclude_docs=true
What version of couchdb and couchdb-lucene? If the latest of each, then you can
avoid
Firstly, are you sure you increased file descriptor max? If, on debian or
ubuntu, you simply tweaked /etc/security/limits.conf then you did not make the
change. By default, PAM does not consult that file for processes that 'su' to a
user as the couchdb startup scripts do. Look in /etc/pam.d/su
Hi Martin,
If you mean some kind of rate-limiting for authentication requests, no (though
that's a neat idea). The next release of couchdb brings PBKDF2 as an
enhancement to the SHA1 passwords hashes. This brings a configurable work
factor which effectively limits the rate of authentication
Hi Paul,
Yes, Lookup1 will be created for every call to your function (once per updated
document). There's no equivalent to commonjs includes here. You might get away
with sticking it in the process dictionary but I doubt it takes long to create
the variable anyway, perhaps measure your
It's not a transaction in any useful sense.
B.
On 12 Jul 2012, at 14:47, Matthieu Rakotojaona wrote:
Just a precision :
On Thu, Jul 12, 2012 at 1:07 PM, Bernhard Gschwantner
bernh...@unserwein.at wrote:
With that construction, you can be sure that it will never happen that you
deduct an
from our INSTALL.Unix file;
Security Considerations
---
You should create a special `couchdb` user for CouchDB.
On many Unix-like systems you can run:
adduser --system \
--home /usr/local/var/lib/couchdb \
--no-create-home \
--shell
https://issues.apache.org/jira/browse/CouchDB
B.
On 13 Jul 2012, at 07:55, Mathias Leppich wrote:
Oh, now I'm getting you point!
The issue is that a filtered replication doesn't periodically checkpoint if
no changes match the filter. This looks like a gap in the continuous
replication
Correct, numeric precision using the javascript view engine is limited to the
64-bit floating point numbers that spidermonkey supports.
For arbitrary precision math, encode your values as strings and use a bignum
library.
As an aside, if you're using floating-point numbers in an accounting
will impose some data type
limitations... it seems like a language with built in support for big
integers would be ideal, e.g. Python, Ruby, rather than JavaScript.
Kind regards,
Samuel
On 17 July 2012 02:27, Robert Newson rnew...@apache.org wrote:
Correct, numeric precision using
An update to a couchdb document is atomic, whether done directly or via an
update handler. An update handler can fail with a 409 just the same as a direct
update can. The only difference between the two update methods is where the
logic runs. The update handler is merely returning the new
Your design document looks wrong to me (or you've omitted important parts of
it). Here's the one from the README for comparison;
{
_id:_design/foo,
fulltext: {
by_subject: {
index:function(doc) { var ret=new Document();
ret.add(doc.subject); return ret }
},
From the README:
Note: The urls via the proxy have a different form:
http://127.0.0.1:5984/_fti/local/db1/_design/cl-test/idx?q=hello
Adapted to your example;
curl
http://root:xxx@localhost:5984/_fti/local/fi/_design/aaa/**name?q=The+Buddy+Group
B.
On 20 Jul 2012, at 18:15, Mark Hahn
then retyping everything may fix some typo.
It's a shame everything has to work all at once to get anywhere. I wish
there was some way to take it a step at a time and debug it. The error
messages are useless.
On Fri, Jul 20, 2012 at 4:31 PM, Robert Newson rnew...@apache.org wrote:
From
601 - 700 of 1233 matches
Mail list logo
