From dev-return-48824-archive-asf-public=cust-asf.ponee.io@couchdb.apache.org Wed Oct 2 20:05:46 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 1A61F18064F for ; Wed, 2 Oct 2019 22:05:46 +0200 (CEST) Received: (qmail 87244 invoked by uid 500); 2 Oct 2019 20:05:45 -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 87231 invoked by uid 99); 2 Oct 2019 20:05:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Oct 2019 20:05:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 79E7F1A4141 for ; Wed, 2 Oct 2019 20:05:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.773 X-Spam-Level: * X-Spam-Status: No, score=1.773 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-he-de.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id YbpJLHLW21Ym for ; Wed, 2 Oct 2019 20:05:41 +0000 (UTC) Received-SPF: Softfail (mailfrom) identity=mailfrom; client-ip=204.11.51.157; helo=smtp.justsomehost.net; envelope-from=wohali@apache.org; receiver= Received: from smtp.justsomehost.net (smtp.justsomehost.net [204.11.51.157]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id 969F57DDFB for ; Wed, 2 Oct 2019 20:05:40 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.justsomehost.net (Postfix) with ESMTP id 976045802A8 for ; Wed, 2 Oct 2019 16:05:32 -0400 (EDT) Received: from smtp.justsomehost.net ([127.0.0.1]) by localhost (smtp.justsomehost.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id xAgjCxabmiKf for ; Wed, 2 Oct 2019 16:05:30 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by smtp.justsomehost.net (Postfix) with ESMTP id 18E7E5802C5 for ; Wed, 2 Oct 2019 16:05:30 -0400 (EDT) X-Virus-Scanned: amavisd-new at smtp.justsomehost.net Received: from smtp.justsomehost.net ([127.0.0.1]) by localhost (smtp.justsomehost.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id lwascBUvhCdq for ; Wed, 2 Oct 2019 16:05:30 -0400 (EDT) Received: from [192.168.1.14] (toroon0560w-lp130-10-174-94-18-143.dsl.bell.ca [174.94.18.143]) by smtp.justsomehost.net (Postfix) with ESMTPSA id EE5975802A8 for ; Wed, 2 Oct 2019 16:05:29 -0400 (EDT) Subject: Re: Proposed deprecations / removals (was: Re: Getting started on CouchDB 3.0, and an introduction) To: dev@couchdb.apache.org References: <48b9b25e-9e78-e0af-bfa7-80284a18e9ae@apache.org> From: Joan Touzet Organization: Apache Software Foundation Message-ID: Date: Wed, 2 Oct 2019 16:05:41 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-CA Content-Transfer-Encoding: quoted-printable On 2019-10-02 15:10, Denitsa Burroughs wrote: > Hi Joan, Adam, et al, >=20 > Ilya and I got together to review the deprecations list to a) determine= if > there were any additional breaking changes required for 3.0 and b) ensu= re > we had a comprehensive list for documentation and release notes purpose= s. > We used this email thread and the tickets Adam created as a starting po= int. > Ilya identified a few other items that were missing from the lists. We'= ve > summarized the changes in https://github.com/apache/couchdb/issues/2218= Added to 3.0 in the project. > This ticket is specific to 3.0. Hopefully it would simplify the release= > notes process. Please take a look - we are missing some of the > reference/decision links and some of the deprecations are not complete = or > documented yet. (I will work with Ilya to update the table as we go sin= ce I > don't have edit permissions yet). >=20 > Proposed 1.x deprecations > was also mentioned and is currently in the 3.0 tasks column. Should we= > close this ticket? It appears quite old. Is there any information that > needs to be extracted and is required for 3.0? Closed out. This mailing list discussion is definitive; that ticket lived long past its useful lifetime. > Thanks, >=20 > Deni >=20 >=20 >=20 > On Mon, Sep 16, 2019 at 4:19 PM Adam Kocoloski wr= ote: >=20 >> I added https://github.com/apache/couchdb/issues/2191 to the 3.0 relea= se >> tasks but I don=E2=80=99t know exactly what the desired end state look= s like there. >> >> Adam >> >>> On Sep 14, 2019, at 3:11 PM, Joan Touzet wrote: >>> >>> Hi Deni, I think you mean Joan, not Jan. :D >>> >>> As I mentioned there isn't an issue yet, so we need to create one. I'= m >> away from my credentials until Tuesday and can address this then, if n= o one >> gets to it first. >>> >>> -Joan >>> >>> On 2019-09-11 2:43 p.m., Denitsa Burroughs wrote: >>>> Hi Jan - >>>> Do you happen to have the ticket/link for this? >>>>> I remembered one last deprecation we wanted in 3.0: security >> tightening, >>>>> which included the deprecation of admin party. >>>>> >>>> Thanks! >>>> Deni >>>> On Mon, Sep 9, 2019 at 2:14 PM Joan Touzet wrote= : >>>>> I remembered one last deprecation we wanted in 3.0: security >> tightening, >>>>> which included the deprecation of admin party. >>>>> >>>>> Jan can you find the ticket on this? I don't think it's the full #1= 504. >>>>> Just new defaults, and we'll need to think thru what happens when >>>>> starting up a node that has no [admins]. Do we create one and log i= ts >>>>> password to the logfile? What if logging is disabled / goes nowhere= ? Or >>>>> do we simply refuse to start until an admin is created? What about >>>>> crypting and salting the password ahead of time - do we introduce a= >>>>> small cli tool to generate passwords like apache/httpd does? Many >>>>> questions. >>>>> >>>>> -Joan >>>>> >>>>> >>>>> On 2019-09-04 5:37 p.m., Joan Touzet wrote: >>>>>> Hey Adam, >>>>>> >>>>>>> When it comes to deprecating and/or removing functionality, I fee= l >> like >>>>> I don=E2=80=99t know exactly where we stand today. We have occasion= ally >> described >>>>> some of the CouchApp functionality as already being deprecated, but= I=E2=80=99m >>>>> having trouble finding any official record of that in our >> documentation. >>>>>> Thanks for re-opening the deprecation discussion. I've reviewed [1= ] >> and >>>>>> provide the following summary tables (Markdown format). >>>>>> >>>>>> **NOTE**: This is /not/ the vote for deprecation, nor a formal >>>>>> announcement of such. This is a starting point for discussion. A v= ote >>>>>> still needs to happen for this to move forward. Anything already >>>>>> deprecated in 2.0 can be removed in 3.0 without a formal vote, but= >> it'd >>>>>> be nice if it got mentioned on the dev@ list before the PR lands o= n >>>>>> master, please. >>>>>> >>>>>> As I'm going to be travelling for most of the rest of September, I= 'd >>>>>> prefer if someone else (like Adam or Deni) can help drive this >>>>> discussion. >>>>>> >>>>>> Once there is consensus from the community on these lists, we shou= ld >>>>>> close #1534 and split it into 3 new tickets based on the tables be= low >>>>>> (excepting the features already removed in 2.x). >>>>>> >>>>>>> I guess let=E2=80=99s start with: does anyone believe we are in a= position to >>>>> be eliminating previously-deprecated functionality in 3.0? >>>>>> >>>>>> Yes, for the items in the 2nd table below, absolutely. >>>>>> >>>>>> -Joan "turning the tables" Touzet >>>>>> >>>>>> >>>>>> -------- >>>>>> >>>>>> >>>>>> # Recently removed features in 2.x >>>>>> >>>>>> **Feature/Endpoint** | **Links** >>>>>> ------------------------------------|------------ >>>>>> update_notifications | [10] >>>>>> ini-file based query servers | [11] >>>>>> ini-file based HTTP global handlers | [11] >>>>>> OS daemons | [11],[12] >>>>>> vhost redirects/global handlers | [11],[12] >>>>>> couch_httpd_proxy | [11],[12] >>>>>> >>>>>> *NOTE*: Some of these still have lingering bits in the documentati= on >>>>>> that need a final cleanup pass before 3.0 should be relea= sed. >>>>>> >>>>>> -------- >>>>>> >>>>>> # Already deprecated items, to be removed in 3.0 >>>>>> >>>>>> **Feature/Endpoint** | **Links** >>>>>> ------------------------------------|------------ >>>>>> some duplicate dbinfo size fields | [2],[3] >>>>>> delayed_commits | [4] >>>>>> port 5986 | [5],[6] >>>>>> `/{db}/_external/*` | [7],[8] >>>>>> view-based changes (code remnants) | [17],[18],[19],[20] >>>>>> >>>>>> -------- >>>>>> >>>>>> # Proposed deprecations for 3.0, not rebuilt/removed in 4.0 >>>>>> >>>>>> **Feature/Endpoint** | **Replaced by** | **Links** >>>>>> --------------------------|----------------------|----------- >>>>>> `/{db}/{ddoc}/_show/*` | App server/rev proxy | =E2=80=A0 >>>>>> `/{db}/{ddoc}/_list/*` | App server/rev proxy | =E2=80=A0 >>>>>> virtual hosts [24] | haproxy, multitenant | [25] >>>>>> `/{db}/{ddoc}/_rewrite/*` | App server/rev proxy | [26] >>>>>> >>>>>> =E2=80=A0: getRow() makes embedding a new, efficient JS engine imp= ossible >> since >>>>>> getRow() does not give up thread execution control; an entirely ne= w >>>>>> approach would need to be constructed, breaking backward compatibi= lity >>>>>> at the very least. (There are additional challenges.) >>>>>> >>>>>> -------- >>>>>> >>>>>> # Likely will remain unchanged through 4.0 >>>>>> >>>>>> **Feature/Endpoint** | **Improved by** >>>>>> ---------------------------------|---------------------- >>>>>> VDU (validatefun()) [13] | [14],[15] >>>>>> update handlers (updatefun) [16] | [14],[15] >>>>>> JS engine [21] | [22],[23] >>>>>> system DB special handling | [27] >>>>>> >>>>>> *NOTE*: The last table may grow as limitations imposed by FDB are >> better >>>>>> understood. >>>>>> >>>>>> -------- >>>>>> >>>>>> # References >>>>>> >>>>>> [1]: https://github.com/apache/couchdb/issues/1534 >>>>>> [2]: >>>>>> >>>>> >> https://docs.couchdb.org/en/stable/api/database/common.html?highlight=3D= disk-size#get--db >>>>>> [3]: https://github.com/apache/couchdb/pull/2163 >>>>>> [4]: >>>>>> >>>>> >> https://github.com/apache/couchdb/blob/103a0624f309ea0d796176a55eb5fae= a68f26047/test/javascript/tests/delayed_commits.js#L16 >>>>>> [5]: https://github.com/apache/couchdb/issues/1523 >>>>>> [6]: https://github.com/apache/couchdb/pull/2092 >>>>>> [7]: https://github.com/apache/couchdb/pull/1330 >>>>>> [8]: https://docs.couchdb.org/en/stable/whatsnew/2.2.html >>>>>> [10]: https://github.com/apache/couchdb/pull/1476 >>>>>> [11]: https://docs.couchdb.org/en/stable/whatsnew/2.3.html >>>>>> [12]: https://github.com/apache/couchdb/pull/1602 >>>>>> [13]: https://docs.couchdb.org/en/stable/ddocs/ddocs.html#vdufun >>>>>> [14]: https://github.com/apache/couchdb/issues/1554 >>>>>> [15]: https://github.com/apache/couchdb/pull/1898 >>>>>> [16]: >>>>> https://docs.couchdb.org/en/stable/ddocs/ddocs.html#update-function= s >>>>>> [17]: https://github.com/apache/couchdb/issues/592 >>>>>> [18]: https://github.com/apache/couchdb/issues/831 >>>>>> [19]: >>>>>> >>>>> >> https://lists.apache.org/thread.html/516793df0c1913c045441d0ff78339f30= 7e2aff517d9223da44edd9e@%3Cdev.couchdb.apache.org%3E >>>>>> [20]: >>>>>> >>>>> >> http://docs.couchdb.org/en/stable/api/database/changes.html?highlight=3D= selector#selector >>>>>> [21]: https://github.com/apache/couchdb/issues/1513 >>>>>> [22]: https://github.com/apache/couchdb/issues/1875 >>>>>> [23]: https://github.com/apache/couchdb/issues/1884 >>>>>> [24]: >> https://docs.couchdb.org/en/stable/config/http.html#virtual-hosts >>>>>> [25]: https://github.com/apache/couchdb/issues/1539 >>>>>> [26]: >>>>>> >>>>> >> https://docs.couchdb.org/en/stable/api/ddoc/rewrites.html#api-ddoc-rew= rite >>>>>> [27]: https://github.com/apache/couchdb/issues/1534 >>>>>> >>>>> >> >> >=20