[
https://issues.apache.org/jira/browse/COUCHDB-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015050#comment-13015050
]
Jan Lehnardt commented on COUCHDB-1117:
---------------------------------------
I think the long-term solution here is to drop group=true and rename it ti
group_level=exact. Of course, that would break BC and can't be considered
before 2.0.0.
In the meantime, how about detecting that both group=true and group_level=N are
set and returning an error, regardless of which order they are specified in?
> Querying view with group parameter after group_level parameter is ignoring
> group_level parameter
> ------------------------------------------------------------------------------------------------
>
> Key: COUCHDB-1117
> URL: https://issues.apache.org/jira/browse/COUCHDB-1117
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Affects Versions: 1.1
> Environment: {"couchdb":"Welcome","version":"1.1.0a771dd47-git"}
> Reporter: Sameer Babu KK
>
> Query with
> http://localhost:5984/t24-pmdata/_design/pm/_view/report?startkey=[3,%22temperature%22,2011,2,1]&endkey=[3,%22temperature%22,2011,2,29]&group_level=3&group=true
> returns different results than
> http://localhost:5984/t24-pmdata/_design/pm/_view/report?startkey=[3,%22temperature%22,2011,2,1]&endkey=[3,%22temperature%22,2011,2,29]&group=true&group_level=3
>
> or just
> http://localhost:5984/t24-pmdata/_design/pm/_view/report?startkey=[3,%22temperature%22,2011,2,1]&endkey=[3,%22temperature%22,2011,2,29]&group_level=3
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
