[jira] [Commented] (COUCHDB-3199) Replicator VDU function doesn't acount for an already malformed document in replicator db

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on COUCHDB-3199:
--

Commit 7096273aac92afcffdb326ec963205583b4bc46f in couchdb's branch 
refs/heads/master from [~vatamane]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=7096273 ]

Bump replicator to fix restrictive VDU function issue

COUCHDB-3199


> Replicator VDU function doesn't acount for an already malformed document in 
> replicator db
> -
>
> Key: COUCHDB-3199
> URL: https://issues.apache.org/jira/browse/COUCHDB-3199
> Project: CouchDB
>  Issue Type: Bug
>Reporter: Nick Vatamaniuc
>
> In case when code is updated from an older version of couchdb which didn't 
> have (or had a less restrictive) VDU function. A malformed document could 
> have ended up in the _replicator database.
> Replicator will try to parse it and flag it as an error then try to update 
> the document. However the more restrictive VDU function will cause the 
> document update to crash the replicator manager.



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

[jira] [Commented] (COUCHDB-3199) Replicator VDU function doesn't acount for an already malformed document in replicator db

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on COUCHDB-3199:
-

Github user asfgit closed the pull request at:

https://github.com/apache/couchdb-couch-replicator/pull/50


> Replicator VDU function doesn't acount for an already malformed document in 
> replicator db
> -
>
> Key: COUCHDB-3199
> URL: https://issues.apache.org/jira/browse/COUCHDB-3199
> Project: CouchDB
>  Issue Type: Bug
>Reporter: Nick Vatamaniuc
>
> In case when code is updated from an older version of couchdb which didn't 
> have (or had a less restrictive) VDU function. A malformed document could 
> have ended up in the _replicator database.
> Replicator will try to parse it and flag it as an error then try to update 
> the document. However the more restrictive VDU function will cause the 
> document update to crash the replicator manager.



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

[jira] [Commented] (COUCHDB-3199) Replicator VDU function doesn't acount for an already malformed document in replicator db

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on COUCHDB-3199:
--

Commit 48996b108c458421c8a73097be152769bdc3fc48 in couchdb-couch-replicator's 
branch refs/heads/master from [~vatamane]
[ 
https://git-wip-us.apache.org/repos/asf?p=couchdb-couch-replicator.git;h=48996b1
 ]

Let "error" replication document updates bypass the VDU function.

This is necessary in the case where an software upgrade happens with
a more restrictive VDU function. Replicator db might end up having documents
which would not pass validation anymore, leading to a replicator manager
crash when it updates the document with an "error" state.

So in case of an "error" state allow malformed document so the user can
see the error.

COUCHDB-3199


> Replicator VDU function doesn't acount for an already malformed document in 
> replicator db
> -
>
> Key: COUCHDB-3199
> URL: https://issues.apache.org/jira/browse/COUCHDB-3199
> Project: CouchDB
>  Issue Type: Bug
>Reporter: Nick Vatamaniuc
>
> In case when code is updated from an older version of couchdb which didn't 
> have (or had a less restrictive) VDU function. A malformed document could 
> have ended up in the _replicator database.
> Replicator will try to parse it and flag it as an error then try to update 
> the document. However the more restrictive VDU function will cause the 
> document update to crash the replicator manager.



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

[GitHub] couchdb-couch-replicator pull request #50: Let "error" replication document ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/couchdb-couch-replicator/pull/50


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch-replicator issue #50: Let "error" replication document updates...

[rnewson]

Github user rnewson commented on the issue:

https://github.com/apache/couchdb-couch-replicator/pull/50
  
+1


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (COUCHDB-3199) Replicator VDU function doesn't acount for an already malformed document in replicator db

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on COUCHDB-3199:
-

GitHub user nickva opened a pull request:

https://github.com/apache/couchdb-couch-replicator/pull/50

Let "error" replication document updates bypass the VDU function.

This is necessary in the case where an software upgrade happens with
a more restrictive VDU function. Replicator db might end up having documents
which would not pass validation anymore, leading to a replicator manager
crash when it updates the document with an "error" state.

So in case of an "error" state allow malformed document so the user can
see the error.

COUCHDB-3199

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cloudant/couchdb-couch-replicator couchdb-3199

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/couchdb-couch-replicator/pull/50.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #50


commit 48996b108c458421c8a73097be152769bdc3fc48
Author: Nick Vatamaniuc 
Date:   2016-10-14T19:13:47Z

Let "error" replication document updates bypass the VDU function.

This is necessary in the case where an software upgrade happens with
a more restrictive VDU function. Replicator db might end up having documents
which would not pass validation anymore, leading to a replicator manager
crash when it updates the document with an "error" state.

So in case of an "error" state allow malformed document so the user can
see the error.

COUCHDB-3199




> Replicator VDU function doesn't acount for an already malformed document in 
> replicator db
> -
>
> Key: COUCHDB-3199
> URL: https://issues.apache.org/jira/browse/COUCHDB-3199
> Project: CouchDB
>  Issue Type: Bug
>Reporter: Nick Vatamaniuc
>
> In case when code is updated from an older version of couchdb which didn't 
> have (or had a less restrictive) VDU function. A malformed document could 
> have ended up in the _replicator database.
> Replicator will try to parse it and flag it as an error then try to update 
> the document. However the more restrictive VDU function will cause the 
> document update to crash the replicator manager.



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

[GitHub] couchdb-couch-replicator pull request #50: Let "error" replication document ...

[nickva]

GitHub user nickva opened a pull request:

https://github.com/apache/couchdb-couch-replicator/pull/50

Let "error" replication document updates bypass the VDU function.

This is necessary in the case where an software upgrade happens with
a more restrictive VDU function. Replicator db might end up having documents
which would not pass validation anymore, leading to a replicator manager
crash when it updates the document with an "error" state.

So in case of an "error" state allow malformed document so the user can
see the error.

COUCHDB-3199

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cloudant/couchdb-couch-replicator couchdb-3199

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/couchdb-couch-replicator/pull/50.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #50


commit 48996b108c458421c8a73097be152769bdc3fc48
Author: Nick Vatamaniuc 
Date:   2016-10-14T19:13:47Z

Let "error" replication document updates bypass the VDU function.

This is necessary in the case where an software upgrade happens with
a more restrictive VDU function. Replicator db might end up having documents
which would not pass validation anymore, leading to a replicator manager
crash when it updates the document with an "error" state.

So in case of an "error" state allow malformed document so the user can
see the error.

COUCHDB-3199




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (COUCHDB-3199) Replicator VDU function doesn't acount for an already malformed document in replicator db

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on COUCHDB-3199:
--

Commit 48996b108c458421c8a73097be152769bdc3fc48 in couchdb-couch-replicator's 
branch refs/heads/couchdb-3199 from [~vatamane]
[ 
https://git-wip-us.apache.org/repos/asf?p=couchdb-couch-replicator.git;h=48996b1
 ]

Let "error" replication document updates bypass the VDU function.

This is necessary in the case where an software upgrade happens with
a more restrictive VDU function. Replicator db might end up having documents
which would not pass validation anymore, leading to a replicator manager
crash when it updates the document with an "error" state.

So in case of an "error" state allow malformed document so the user can
see the error.

COUCHDB-3199


> Replicator VDU function doesn't acount for an already malformed document in 
> replicator db
> -
>
> Key: COUCHDB-3199
> URL: https://issues.apache.org/jira/browse/COUCHDB-3199
> Project: CouchDB
>  Issue Type: Bug
>Reporter: Nick Vatamaniuc
>
> In case when code is updated from an older version of couchdb which didn't 
> have (or had a less restrictive) VDU function. A malformed document could 
> have ended up in the _replicator database.
> Replicator will try to parse it and flag it as an error then try to update 
> the document. However the more restrictive VDU function will cause the 
> document update to crash the replicator manager.



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

[jira] [Created] (COUCHDB-3199) Replicator VDU function doesn't acount for an already malformed document in replicator db

[Nick Vatamaniuc (JIRA)]

Nick Vatamaniuc created COUCHDB-3199:


 Summary: Replicator VDU function doesn't acount for an already 
malformed document in replicator db
 Key: COUCHDB-3199
 URL: https://issues.apache.org/jira/browse/COUCHDB-3199
 Project: CouchDB
  Issue Type: Bug
Reporter: Nick Vatamaniuc


In case when code is updated from an older version of couchdb which didn't have 
(or had a less restrictive) VDU function. A malformed document could have ended 
up in the _replicator database.

Replicator will try to parse it and flag it as an error then try to update the 
document. However the more restrictive VDU function will cause the document 
update to crash the replicator manager.





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

[GitHub] couchdb-couch-epi pull request #20: Update README.md

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/couchdb-couch-epi/pull/20


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch-epi issue #20: Update README.md

[iilyak]

Github user iilyak commented on the issue:

https://github.com/apache/couchdb-couch-epi/pull/20
  
+1


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (COUCHDB-3198) Improve _bulk_get error handling

[Robert Newson (JIRA)]

Robert Newson created COUCHDB-3198:
--

 Summary: Improve _bulk_get error handling
 Key: COUCHDB-3198
 URL: https://issues.apache.org/jira/browse/COUCHDB-3198
 Project: CouchDB
  Issue Type: Bug
Reporter: Robert Newson


By passing request bodies like;

{"docs":12}
{"docs":[12]}

it's possible to get a 500 error from couchdb. Worse, we send that 500 error as 
a chunk of an already started 200 response, which clients handle poorly.

As I looked into this, we also allow;

{"docs":[{}]}

and then complain that the object has no "id" attribute in the 200 response 
body.




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

[jira] [Created] (COUCHDB-3197) dbupdate feature in additional to dbcopy

[Thaina Yu (JIRA)]

Thaina Yu created COUCHDB-3197:
--

 Summary: dbupdate feature in additional to dbcopy
 Key: COUCHDB-3197
 URL: https://issues.apache.org/jira/browse/COUCHDB-3197
 Project: CouchDB
  Issue Type: Wish
  Components: JavaScript View Server
Reporter: Thaina Yu


DBCopy can only copy result of mapreduce into database as a new document

But couchdb has feature design/update

So I think it would be useful if we could write update function. And set that 
function name to dbupdate after reduce in place of dbcopy

So whenever mapreduce was trigger. Instead of copy result to target database, 
it would pass that reduce document to target update function. We then could use 
reduce document to update another document



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

[GitHub] couchdb-fauxton pull request #786: a few doc-list fixes

[robertkowalski]

Github user robertkowalski closed the pull request at:

https://github.com/apache/couchdb-fauxton/pull/786


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-fauxton pull request #785: react-select: disable cache

[robertkowalski]

Github user robertkowalski closed the pull request at:

https://github.com/apache/couchdb-fauxton/pull/785


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-fauxton issue #785: react-select: disable cache

[robertkowalski]

Github user robertkowalski commented on the issue:

https://github.com/apache/couchdb-fauxton/pull/785
  
merged as 5a8a3fb


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---