You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Paul Joseph Davis (JIRA)" <ji...@apache.org> on 2009/07/30 06:02:14 UTC

[jira] Resolved: (COUCHDB-442) Add a "view" or "format" function to process source doc on query

     [ https://issues.apache.org/jira/browse/COUCHDB-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Joseph Davis resolved COUCHDB-442.
---------------------------------------

    Resolution: Later

Right, we'd need to add ACL support to _list and _show to accomplish the original intent, but that was my reason for doubting the feature; we can just roll this functionality into the existing feature set.

Closing this because it probably won't happen. When some of the upcoming auth/access patches hit similar functionality will most likely get rolled into _list and _show. For interested listeners, keep an ear to the dev@ ground for updates.

> Add a "view" or "format" function to process source doc on query
> ----------------------------------------------------------------
>
>                 Key: COUCHDB-442
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-442
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: JavaScript View Server
>            Reporter: Curt Arnold
>
> It is common practice to do emit(key, null) in a map function and then query with ?include_docs=true to retrieve the documents that were responsible for the entries.  However, the full document may include information that is privileged or the full document may be substantially larger than the information needed to be transferred to the client.
> The proposed enhancement is to allow defining a "view" function in addition to the existing "map" and "reduce" on a view.  If specified, the view function would take the id, key, value and doc and return a JSON value that would be added as the "view" member to the row in the result set.
> One of the use cases on http://wiki.apache.org/couchdb/Authentication_and_Authorization is to be able to specify that a user can retrieve the values from a view, but not add include_docs since that may expose information that they are not authorized to view.  Without the "view" function, there would be pressure to start pushing things into the emitted value.
> Production of views would be likely controlled using a include_views=true in the query string.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Resolved: (COUCHDB-442) Add a "view" or "format" function to process source doc on query

Posted by Curt Arnold <ca...@apache.org>.
On Jul 30, 2009, at 1:55 PM, Paul Davis wrote:

...
>>
>>
>> Which upcoming patches?  Are these developments in progress or  
>> somewhere
>> down the road.   Have they been discussed on the mailing list  
>> (dates or
>> topics would be useful)?  Are there JIRA entries for them?
>>
>
> I was specifically thinking of the OAuth stuff that Jason Davies has
> been working on lately. There's also the cookie based auth. I'm not
> sure if anyone ever took up the mantle for ldap integration or not.
> But in general, there has been movement on authentication mechanisms
> lately.
>
>> It is good to avoid the case where a feature arrives fully baked in  
>> the SVN
>> without previous discussion.  It gives the community has no  
>> opportunity to
>> see if it meets their needs before it is cast in code.
>>
>
> It sure is. Jason has put his patches for OAuth up on JIRA [1]. I
> think Benoit's cookie auth has a ticket in there somewhere.
>

Had those on my radar with good intentions to review them this  
weekend.  Something about the previous message just triggered the  
thought that there might have been something else brewing.


>> I've been trying to organize info from the mailing list, JIRA  
>> entries and
>> code review into an overview of Authentication and Authorization  
>> thoughts on
>> the Wiki  It hasn't been easy getting up to speed and I'd to make  
>> things
>> easier for anyone else who is trying to catch up.
>>
>
> We greatly appreciate your help on focusing the picture on the
> auth/access work. If you're getting stumped with Google and the ML
> archives, your best bet is to hop on IRC and ask your questions. Its a
> friendly channel and there are starting to be enough regulars in all
> timezones that someone's always around.
>
> HTH,
> Paul Davis
>
> [1] https://issues.apache.org/jira/browse/COUCHDB-420

Thanks.

Re: [jira] Resolved: (COUCHDB-442) Add a "view" or "format" function to process source doc on query

Posted by Paul Davis <pa...@gmail.com>.
On Thu, Jul 30, 2009 at 9:11 AM, Curt Arnold<ca...@apache.org> wrote:
>
> On Jul 29, 2009, at 11:02 PM, Paul Joseph Davis (JIRA) wrote:
>
>>
>>    [
>> https://issues.apache.org/jira/browse/COUCHDB-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Paul Joseph Davis resolved COUCHDB-442.
>> ---------------------------------------
>>
>>   Resolution: Later
>>
>> Right, we'd need to add ACL support to _list and _show to accomplish the
>> original intent, but that was my reason for doubting the feature; we can
>> just roll this functionality into the existing feature set.
>>
>> Closing this because it probably won't happen. When some of the upcoming
>> auth/access patches hit similar functionality will most likely get rolled
>> into _list and _show. For interested listeners, keep an ear to the dev@
>> ground for updates.
>
>
> Which upcoming patches?  Are these developments in progress or somewhere
> down the road.   Have they been discussed on the mailing list (dates or
> topics would be useful)?  Are there JIRA entries for them?
>

I was specifically thinking of the OAuth stuff that Jason Davies has
been working on lately. There's also the cookie based auth. I'm not
sure if anyone ever took up the mantle for ldap integration or not.
But in general, there has been movement on authentication mechanisms
lately.

> It is good to avoid the case where a feature arrives fully baked in the SVN
> without previous discussion.  It gives the community has no opportunity to
> see if it meets their needs before it is cast in code.
>

It sure is. Jason has put his patches for OAuth up on JIRA [1]. I
think Benoit's cookie auth has a ticket in there somewhere.

> I've been trying to organize info from the mailing list, JIRA entries and
> code review into an overview of Authentication and Authorization thoughts on
> the Wiki  It hasn't been easy getting up to speed and I'd to make things
> easier for anyone else who is trying to catch up.
>

We greatly appreciate your help on focusing the picture on the
auth/access work. If you're getting stumped with Google and the ML
archives, your best bet is to hop on IRC and ask your questions. Its a
friendly channel and there are starting to be enough regulars in all
timezones that someone's always around.

HTH,
Paul Davis

[1] https://issues.apache.org/jira/browse/COUCHDB-420

Re: [jira] Resolved: (COUCHDB-442) Add a "view" or "format" function to process source doc on query

Posted by Jan Lehnardt <ja...@apache.org>.
On 30 Jul 2009, at 15:11, Curt Arnold wrote:

>
> On Jul 29, 2009, at 11:02 PM, Paul Joseph Davis (JIRA) wrote:
>
>>
>>    [ https://issues.apache.org/jira/browse/COUCHDB-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 
>>  ]
>>
>> Paul Joseph Davis resolved COUCHDB-442.
>> ---------------------------------------
>>
>>   Resolution: Later
>>
>> Right, we'd need to add ACL support to _list and _show to  
>> accomplish the original intent, but that was my reason for doubting  
>> the feature; we can just roll this functionality into the existing  
>> feature set.
>>
>> Closing this because it probably won't happen. When some of the  
>> upcoming auth/access patches hit similar functionality will most  
>> likely get rolled into _list and _show. For interested listeners,  
>> keep an ear to the dev@ ground for updates.
>
>
> Which upcoming patches?  Are these developments in progress or  
> somewhere down the road.   Have they been discussed on the mailing  
> list (dates or topics would be useful)?  Are there JIRA entries for  
> them?
>
> It is good to avoid the case where a feature arrives fully baked in  
> the SVN without previous discussion.  It gives the community has no  
> opportunity to see if it meets their needs before it is cast in code.
>
> I've been trying to organize info from the mailing list, JIRA  
> entries and code review into an overview of Authentication and  
> Authorization thoughts on the Wiki  It hasn't been easy getting up  
> to speed and I'd to make things easier for anyone else who is trying  
> to catch up.

https://issues.apache.org/jira/browse/COUCHDB-441 :)

Cheers
Jan
--

Re: [jira] Resolved: (COUCHDB-442) Add a "view" or "format" function to process source doc on query

Posted by Curt Arnold <ca...@apache.org>.
On Jul 29, 2009, at 11:02 PM, Paul Joseph Davis (JIRA) wrote:

>
>     [ https://issues.apache.org/jira/browse/COUCHDB-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 
>  ]
>
> Paul Joseph Davis resolved COUCHDB-442.
> ---------------------------------------
>
>    Resolution: Later
>
> Right, we'd need to add ACL support to _list and _show to accomplish  
> the original intent, but that was my reason for doubting the  
> feature; we can just roll this functionality into the existing  
> feature set.
>
> Closing this because it probably won't happen. When some of the  
> upcoming auth/access patches hit similar functionality will most  
> likely get rolled into _list and _show. For interested listeners,  
> keep an ear to the dev@ ground for updates.


Which upcoming patches?  Are these developments in progress or  
somewhere down the road.   Have they been discussed on the mailing  
list (dates or topics would be useful)?  Are there JIRA entries for  
them?

It is good to avoid the case where a feature arrives fully baked in  
the SVN without previous discussion.  It gives the community has no  
opportunity to see if it meets their needs before it is cast in code.

I've been trying to organize info from the mailing list, JIRA entries  
and code review into an overview of Authentication and Authorization  
thoughts on the Wiki  It hasn't been easy getting up to speed and I'd  
to make things easier for anyone else who is trying to catch up.