You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@couchdb.apache.org by "Robert Newson (JIRA)" <ji...@apache.org> on 2016/03/26 13:54:25 UTC

[jira] [Commented] (COUCHDB-2746) /db_updates behaviour changed

    [ https://issues.apache.org/jira/browse/COUCHDB-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212992#comment-15212992 ] 

Robert Newson commented on COUCHDB-2746:
----------------------------------------

/_db_updates behaviour is enhanced in 2.0 (it's persistent). Is there any reason for this to be a blocker?

> /db_updates behaviour changed
> -----------------------------
>
>                 Key: COUCHDB-2746
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2746
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>            Reporter: Robert Kowalski
>            Assignee: Alexander Shorin
>            Priority: Blocker
>
> It seems that the `db_updates` enpoint on the backdoor port and cluster port behave differently.
>  
> Ways to fix:
>  
> a) document as breaking change
> b) change global_changes default behaviour (which I would prefer to keep as much BC as possible to 1.x)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)