Yay, welcome!
On Wed, Jan 1, 2014 at 8:24 PM, Dave Cottlehuber d...@jsonified.com wrote:
Dear community,
There's nothing like starting off the New Year with a New Committer!!
I am pleased to announce that the CouchDB Project Management Committee
has elected Nick North as a CouchDB
I put a design doc behind a desk record / virtual host, that should do the
trick. The user that is used by the app is read only
Robert Newson rnew...@apache.org wrote:
there’s no notion of read-protection in CouchDB.
There’s no document level read protection, but you can certainly grant
or
On Thu, Jan 2, 2014 at 12:27 AM, Robert Newson rnew...@apache.org wrote:
there’s no notion of read-protection in CouchDB.
There’s no document level read protection, but you can certainly grant or
deny read access to users on a per database basis. That’s by design due to
the ease that
Hi,
I have the following strange problem: I want to rewrite an URL to trigger a
_list function which should display data supplied by a view. The does both
map and reduce, but for this list funtion I don't need the reduce step, so I
supplied the query argument reduce=false. This is the rewrite I
The 1st thing I see right off the bat is that that is not valid json... The
keys need to be in quotes because they are strings... Second.. They query
arg needs to be a string too... I believe...I haven't used them in a
while...either way that's not valid json.
On Jan 2, 2014 6:54 AM, Oliver
It is relevant, the OP could use multiple databases to expose the subset of
documents to the appropriate subset of users.
Mentioning Couchbase is not relevant. :)
B.
On 2 Jan 2014, at 00:40, Jens Alfke j...@couchbase.com wrote:
On Jan 1, 2014, at 3:27 PM, Robert Newson rnew...@apache.org
It doesn’t achieve the same effect, though, the virtual host + url rewriter is
not an access control mechanism. You’re still granting database-wide read
permissions to the user.
B.
On 2 Jan 2014, at 09:09, Florian Westreicher Bakk.techn. st...@meredrica.org
wrote:
I put a design doc
Correct me if I'm wrong here... If every doc had some meta info with it...
And every URL rewrite went to a show or list function...couldn't you use
the sec object passed on the request object to get what you want?... Or
pass in some application level user credentials... Granted that doesn't
sound
Happy 2014 @ the list,
there is no document level (or even worse attribute level) access control
mechanism implemented in couched at this time, please correct me if I am wrong.
Any type of document level access control introduces problems with either
information leaking aggregate/reduce
On Thu, Jan 2, 2014 at 2:29 PM, Keno Kuhlmann keno.kuhlm...@gmx.de wrote:
Happy 2014 @ the list,
there is no document level (or even worse attribute level) access control
mechanism implemented in couched at this time, please correct me if I am
wrong. Any type of document level access control
Great, it works now. I didn't know that false is just a string and not it's
own type like in Python
SOLVED
Am Donnerstag, 2. Januar 2014, 03:58:26 schrieb Stanley Iriele:
The 1st thing I see right off the bat is that that is not valid json... The
keys need to be in quotes because they are
Well..thanks for that I didn't realize that. The solution I was suggesting
would have been places behind a reverse proxy of course
On Jan 2, 2014 1:12 PM, Jan Lehnardt j...@apache.org wrote:
On 01 Jan 2014, at 23:32 , Stanley Iriele siriele...@gmail.com wrote:
Can't you just use vhosts and
I was referring to Apache / nginx vhost. But I did not know this issue , good
to know for the future.
Jan Lehnardt j...@apache.org wrote:
On 01 Jan 2014, at 23:32 , Stanley Iriele siriele...@gmail.com wrote:
Can't you just use vhosts and rewrites to take care of that?...
Also...you
could use
List function are bad for performance since they are evaluated every time they
run. I wanted to avoid them and use views (disk storage is cheap, CPU is not)
Stanley Iriele siriele...@gmail.com wrote:
Correct me if I'm wrong here... If every doc had some meta info with
it...
And every URL
On Jan 2, 2014, at 4:20 AM, Robert Newson rnew...@apache.org wrote:
It is relevant, the OP could use multiple databases to expose the subset of
documents to the appropriate subset of users.
True. But FWIW, we found in 2012 that this setup is a hassle to configure (i.e.
provisioning user
On 02 Jan 2014, at 20:49 , Jens Alfke j...@couchbase.com wrote:
On Jan 2, 2014, at 4:20 AM, Robert Newson rnew...@apache.org wrote:
It is relevant, the OP could use multiple databases to expose the subset of
documents to the appropriate subset of users.
True. But FWIW, we found in
Welcome aboard, Nick! :)
Best
Jan
--
On 01 Jan 2014, at 20:24 , Dave Cottlehuber d...@jsonified.com wrote:
Dear community,
There's nothing like starting off the New Year with a New Committer!!
I am pleased to announce that the CouchDB Project Management Committee
has elected Nick North
On Jan 2, 2014, at 11:56 AM, Jan Lehnardt j...@apache.org wrote:
Out of curiosity, what scaling limit have you found? Is this documented
somewhere?
By “we found” I should have said “we extrapolated”. We have customers that will
need hundreds of thousands of user accounts, and attaching that
On 02 Jan 2014, at 21:08 , Jens Alfke j...@couchbase.com wrote:
On Jan 2, 2014, at 11:56 AM, Jan Lehnardt j...@apache.org wrote:
Out of curiosity, what scaling limit have you found? Is this documented
somewhere?
By “we found” I should have said “we extrapolated”. We have customers
Welcome Nick!
-Russell
On Thu, Jan 2, 2014 at 11:57 AM, Jan Lehnardt j...@apache.org wrote:
Welcome aboard, Nick! :)
Best
Jan
--
On 01 Jan 2014, at 20:24 , Dave Cottlehuber d...@jsonified.com wrote:
Dear community,
There's nothing like starting off the New Year with a New
Hello all!
Long lived HTTP connections like the continuous feed from CouchDB are
not exactly in wide use. I had an issue using them together with vert.x
[1] because there is no API to close the stream from the vert.x side.
So I wrote couchpipe - a simple Java server that consumes a changes
On Jan 2, 2014, at 12:17 PM, Jan Lehnardt
j...@apache.orgmailto:j...@apache.org wrote:
We added /_db_updates in 1.4.0 that allows building the above with the
difference that a replication only runs for active users, thus delaying most of
the work until it is needed *and* avoiding having to
22 matches
Mail list logo
