Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 05187112C4 for ; Wed, 23 Jul 2014 18:57:43 +0000 (UTC) Received: (qmail 39625 invoked by uid 500); 23 Jul 2014 18:57:42 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 39543 invoked by uid 500); 23 Jul 2014 18:57:42 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 39414 invoked by uid 99); 23 Jul 2014 18:57:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jul 2014 18:57:42 +0000 Date: Wed, 23 Jul 2014 18:57:42 +0000 (UTC) From: "Alexander Shorin (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (COUCHDB-2277) Bad unuseable Rest-API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COUCHDB-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Shorin closed COUCHDB-2277. ------------------------------------- Resolution: Not a Problem {{key}}, {{startkey}} and {{endkey}] must have a valid JSON value. That's the requirement, because view index is built on JSON values - so you must provide the valid one to let CouchDB walk through index correctly. > Bad unuseable Rest-API > ---------------------- > > Key: COUCHDB-2277 > URL: https://issues.apache.org/jira/browse/COUCHDB-2277 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Reporter: Manfred Quasten > > 1. A key must be given with ?key="key" without " it will not work > http://localhost:5984/petstore/_design/qualityByArtist/_view/qualityByArtist?key=%22nicole%22 > Using google maps will work, with and without " > http://maps.googleapis.com/maps/api/geocode/jsonaddress=Magadan&sensor=false > 2: a) AcomposedKey must be given as json ?! that is nearly not testable in a browser and for me the only way is to use curl > b) I think giving a content in rest will normaly be use post and give it in body, this I've never seen before .... > http://localhost:5984/petstore/_design/pricePerUnit/_list/quantityFilter/pricePerUnit?key={%22quality%22:%22platinium%22,%20%22unit%22:%22date%22}&quantity=3 > 2c) when I use > key={"unit":"date"} , "quality" : "platinium"} use unit at first and quality as second" , nothing will be found. I think, why maps, it seams to work like an array , are maps fake ? It seam not that they will work in a correct way. Using java my workaround is using LinkedHashMaps and putting it in the right order into it and after this I serialize it to json an give it to springs resttemplate ... I will be rembered to petClinic, because pet will get ill from bad JavaEE, may be that this isn't good for pets too ... -- This message was sent by Atlassian JIRA (v6.2#6252)