Hello (CouchDB)-World!
Ive just completed uploading my sample CouchApp to IrisCouch.
The preliminary documentation (yes, there is some already) is on my web
space at:
http://www.eddelbuettel.net/html5/cornercouch.html
I am a complete open source noob. Learning CouchDB and AngularJS
On Wed, Dec 12, 2012 at 4:23 PM, Alon Keren wrote:
> couch-incarnate author here.
>
> You described the way it works pretty well.
Thanks Alon, I did a lot of source inspection and poking and prodding
to make sure I understood what was going on. :) couch-incarnate was
very helpful for me to unde
Yes, our chained map-reduce is incremental.
On 12 December 2012 22:07, nicholas a. evans wrote:
> On Wed, Dec 12, 2012 at 4:03 PM, James Marca
> wrote:
>> I feel your pain but cannot offer any help. I also use your option 5:
>> I use node.js to manually store view output into a separate db, wit
On Wed, Dec 12, 2012 at 4:03 PM, James Marca
wrote:
> I feel your pain but cannot offer any help. I also use your option 5:
> I use node.js to manually store view output into a separate db, with
> the doc _ids equal to the key of the view output, so that I can limit
> updates to only those things
On Wed, Dec 12, 2012 at 4:22 PM, svilen wrote:
> i dont know if it can help, but i found that u can include
> local_seq=true in the view options, and that will expose
> doc._local_seq as the last change# of the doc. which eventualy
> can skip some steps below..
Thanks. I had completely forgotten
Hi Nick,
couch-incarnate author here.
You described the way it works pretty well. Btw, I suspect also cloudant do
their chaining incrementally.
I started working on incarnate following my own frustration with the lack
of chained-mapreduce.
I'm a bit biased here, but I find the end solution to be
i dont know if it can help, but i found that u can include
local_seq=true in the view options, and that will expose
doc._local_seq as the last change# of the doc. which eventualy
can skip some steps below..
>.
> 1) GET changes to SourceDB.
> 2) query view using ["metadata", changed.id] k
I feel your pain but cannot offer any help. I also use your option 5:
I use node.js to manually store view output into a separate db, with
the doc _ids equal to the key of the view output, so that I can limit
updates to only those things that change.
This is one feature I really want in CouchDB..
On Wed, Nov 28, 2012 at 03:54:24PM -0700, Ryan Ramage wrote:
> I was asked by Jan to send this email.
>
> Please help us collect the version of Erlang shipping with various distros.
> Respond to this email with the following format:
>
Late reply, but I didn't see these yet in the thread:
Slackwa
Thank you Robert. I have created
https://issues.apache.org/jira/browse/COUCHDB-1627
Best,
- Nestor
On Wed, Dec 12, 2012 at 12:58 PM, Robert Newson wrote:
> Hi Nestor,
>
> The ssh command you showed should create a couchdb process completely
> daemonized and immune to the exit of your shell, can
I've got some views that simply must use iterative map reduce. The
greatest need is simply to sort based on the value of the first reduction.
I'm looking over my options, and I'm going to list them here. I'm looking
for someone to tell me that I've missed an option, or recommend a
modification t
Hi Nestor,
The ssh command you showed should create a couchdb process completely
daemonized and immune to the exit of your shell, can you file a ticket
at https://issues.apache.org/jira/browse/CouchDB please?
B.
On 12 December 2012 17:30, Nestor Urquiza wrote:
> Hi Shane,
>
> CFEngine is doing
Hi Shane,
CFEngine is doing the magic behind scenes. Try it please with:
$ ssh -t remoteserver sudo /etc/init.d/couchdb restart
Once the ssh command finishes couchdb dies.
I am starting couchdb just with the command above. It works from
command line when I am logged in the server but it fails wh
Hi Dave,
Restarting though APIs would demand an extra overhead on the scripts,
certainly doable but there should be IMO an easier way for a sysadmin
to remotely restart. But even if that works you still have the problem
of hanging or dying instances, it simply can happen. Most of the
services (dae
I've restarted CouchDB using the supplied init.d script via ssh and also
automatically with CFEngine many, many times and I've never had a
problem with it killing the couchdb process when I logout.
The nohup command disconnects a process from the terminal's stardard
input, error and output fil
On 12 December 2012 15:51, Nestor Urquiza wrote:
> Hi Robert,
>
> For maintenance purposes you might want to remotely restart couchdb.
> For example you remotely install couchdb and after that you remotely
> harden it (changing configuration files) which demands a restart.
Applying changes via th
If you're reporting a bug in our init.d script (namely, that it fails
to daemonize couchdb correctly), then please open a JIRA ticket.
You do not need to restart couchdb just to change configuration,
though. Just use PUT's to :5984/_config/section/key -d 'value', and
couchdb will change internally
Hi Robert,
For maintenance purposes you might want to remotely restart couchdb.
For example you remotely install couchdb and after that you remotely
harden it (changing configuration files) which demands a restart.
We prefer to maintain the servers remotely rather than login into them
and manuall
CouchDB includes a script to launch it as a daemon, a standard init.d
script. I'm confused why you'd ssh to a machine, run couchdb in the
foreground, and log off.
On 12 December 2012 13:34, Wayne Conrad wrote:
> On 12/11/2012 11:53 AM, Nestor Urquiza wrote:
>> As other users have asked in the pa
On 12/11/2012 11:53 AM, Nestor Urquiza wrote:
> As other users have asked in the past to this list couchdb will not
> run from a remote interactive shell but rather it will be killed when
> the ssh session terminates. The command nohup can help with that. Here
> is what I did (which works OK):
Te
20 matches
Mail list logo
