From dev-return-48864-archive-asf-public=cust-asf.ponee.io@couchdb.apache.org Wed Oct 23 10:40:26 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id E8DAE180608 for ; Wed, 23 Oct 2019 12:40:25 +0200 (CEST) Received: (qmail 68721 invoked by uid 500); 23 Oct 2019 10:40:25 -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 68710 invoked by uid 99); 23 Oct 2019 10:40:24 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.42) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Oct 2019 10:40:24 +0000 Received: from auth1-smtp.messagingengine.com (auth1-smtp.messagingengine.com [66.111.4.227]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 7F6AD5A44 for ; Wed, 23 Oct 2019 10:40:24 +0000 (UTC) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailauth.nyi.internal (Postfix) with ESMTP id 09D6420A0D for ; Wed, 23 Oct 2019 06:40:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 23 Oct 2019 06:40:24 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrkeelgdefudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephfgtgfgguffffhfvjgfkofesthhqmh dthhdtjeenucfhrhhomheptfhosggvrhhtucfurghmuhgvlhcupfgvfihsohhnuceorhhn vgifshhonhesrghprggthhgvrdhorhhgqeenucffohhmrghinheptghouhgthhgusgdroh hrghdpshhlrggtkhdrtghomhenucfkphepudehledrkedrudejtddrvddvnecurfgrrhgr mhepmhgrihhlfhhrohhmpehrnhgvfihsohhnodhmvghsmhhtphgruhhthhhpvghrshhonh grlhhithihqdelfeegvddtvdejvddqudduleegjedtjeejqdhrnhgvfihsohhnpeeprghp rggthhgvrdhorhhgsehfrghsthhmrghilhdrfhhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from [198.18.15.242] (16.aa.089f.ip4.static.sl-reverse.com [159.8.170.22]) by mail.messagingengine.com (Postfix) with ESMTPA id 9ED16D60062 for ; Wed, 23 Oct 2019 06:40:23 -0400 (EDT) From: Robert Samuel Newson Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3594.4.19\)) Subject: Re: Batch mode options for CouchDB 4.0 Date: Wed, 23 Oct 2019 11:40:22 +0100 References: To: CouchDB Developers In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3594.4.19) Hi, Just confirming my position on this. We should treat a request with = batch=3Dok as if the setting was not there. That is, make the same = durable commit as normal. We should therefore send a 201 Created = response code. We should continue to validate the batch setting (it can = be absent or it can be "ok" but every other value is a 400 Bad Request). > On 23 Oct 2019, at 11:16, Richard Ellis wrote: >=20 > Background: > = https://docs.couchdb.org/en/2.3.1/api/database/common.html#api-doc-batch-w= rites > https://couchdb.slack.com/archives/CKSBJJ2MT/p1571749837010500 >=20 >> ricellis 2:10 PM >> Anyone able to comment on whether batch=3Dok (batch mode writes) are = still=20 > going to be a thing in FDB based CouchDB? I didn't see it on the = proposed=20 > list of deprecations, but AIUI _ensure_full_commit is going to be a = no-op=20 > (even though the endpoint remains for replicator compatibility), so it=20= > seems at least the option to manually flush a batch seems to be going. >=20 >> jan 2:47 PM >> I don=E2=80=99t think we=E2=80=99ll keep that >=20 >> rnewson 3:53 PM >> we should decide though, on dev mlist. >> I'd vote for 'recognise and ignore', same as for 'sorted=3Dfalse' for=20= > _view. >=20 > Rounding out that discussion a couple of options were proposed in = slack=20 > for the handling of the batch=3Dok parameter in CouchDB 4/FDB: >=20 > 1. Continue to accept the batch parameter, but ignore it and on = success=20 > return the 201 status code associated with the write's FDB commit. = Note=20 > this a slight change from the currently documented batch mode = behaviour of=20 > "The CouchDB server will respond with an HTTP 202 Accepted response = code=20 > immediately.". >=20 > 2. No longer accept the batch parameter and return a 400 bad request = if it=20 > is used. >=20 > Opening the discussion here about these two or any other options = people=20 > would like to propose. >=20 > Rich > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with = number=20 > 741598.=20 > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 = 3AU >=20