[GitHub] [couchdb] wohali closed issue #1534: proposed 1.x deprecations
wohali closed issue #1534: proposed 1.x deprecations URL: https://github.com/apache/couchdb/issues/1534 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb] wohali commented on issue #1534: proposed 1.x deprecations
wohali commented on issue #1534: proposed 1.x deprecations URL: https://github.com/apache/couchdb/issues/1534#issuecomment-537656882 Closing this ticket in favour of the following: * #2218 What's being removed in 3.0 * Beyond that, see https://lists.apache.org/thread.html/cf990063d5b686901f2b6ead0bd6eb3b687f99c7746d5345283a403e@%3Cdev.couchdb.apache.org%3E This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb] wohali opened a new issue #2219: function_clause in chttpd_db:update_doc/4
wohali opened a new issue #2219: function_clause in chttpd_db:update_doc/4 URL: https://github.com/apache/couchdb/issues/2219 # Description Single node CouchDB under light load experiences this error occasionally: ``` [error] 2019-09-20T17:42:46.575000Z couchdb@localhost <0.889.287> c6691696a0 req_err(181230657) unknown_error : function_clause [<<"chttpd_db:update_doc/4 L1196">>,<<"chttpd_db:send_updated_doc/6 L1160">>,<<"chttpd:handle_req_after_auth/2 L320">>,<<"chttpd:process_request/1 L303">>,<<"chttpd:handle_request_int/1 L243">>,<<"mochiweb_http:headers/6 L128">>,<<"proc_lib:init_p_do_apply/3 L247">>] ``` ## Steps to Reproduce Unknown. ## Expected Behaviour `function_clause` is always a bug. ## Your Environment * CouchDB Version used: 2.3.1 * Browser name and version: n/a * Operating System and version: Windows Server 2008 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb] iilyak opened a new issue #2218: Deprecation list for 3.0 (release notes compilation)
iilyak opened a new issue #2218: Deprecation list for 3.0 (release notes
compilation)
URL: https://github.com/apache/couchdb/issues/2218
This ticket would be used to collect all related links
| * | **Feature/Endpoint** | **Decision** | **Code change** | **Docs** |
**Release Notes** |
|::||---|--|--|--|
| [] | update_notifications| | [10]
|[30]||
| [] | ini-file based query servers | | [12] |
[??]| [11],[vv] |
| [] | ini-file based HTTP global handlers | | [12] | [??]
| [11],[vv] |
| [] | OS daemons | | [12]
|[30] | [11],[vv] |
| [] | vhost redirects/global handlers | | [12]|
[rr] | [11],[vv] |
| [] | couch_httpd_proxy | | [12]|
[rr] | [11],[vv] |
| [] | _view based changes feed. | [13],[24] | |
||
| [] | Support for ?queries parameter| [] |
[14],[15],[17],[21] | [16],[20] ||
| [] | remove `delayed_commits` setting | [28],[??] | [18] | [19]
||
| [] | remove fsync_options setting | [] | [18]|
[19]||
| [] | Retire the node-local interface (port 5986)| [23],[??] | [22]
|||
| [] | Remove `/{db}/_external/*` functionality | [25],[??] | [27]
|[26] ||
| [] | some duplicate dbinfo size fields | [2],[??] | [3]
|[] ||
| [] | `/{db}/{ddoc}/_show/*` | [??] | [] |
[dd] ||
| [] | `/{db}/{ddoc}/_list/*` | [??] | []
|[dd] ||
| [] | virtual hosts | [??] | []
|[dd] ||
| [] | `/{db}/{ddoc}/_rewrite/*` | [??] | [] |
[dd] ||
| [] | remove admin party | [29],[??] |
| [vv] ||
# Legend
- [vv]: need to be done
- [??]: Need to find reference
- [dd]: Just document as deprecated
- [rr]: Remove documentation for feature
[2]:
https://docs.couchdb.org/en/stable/api/database/common.html?highlight=disk-size#get--db
[3]: https://github.com/apache/couchdb/pull/2163
[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://lists.apache.org/thread.html/516793df0c1913c045441d0ff78339f307e2aff517d9223da44edd9e@%3Cdev.couchdb.apache.org%3E
[14]: https://github.com/apache/couchdb/issues/820
[15]: https://github.com/apache/couchdb/pull/1032
[16]: https://github.com/apache/couchdb-documentation/pull/437
[17]: https://github.com/apache/couchdb/pull/2173
[18]: https://github.com/apache/couchdb/pull/2208
[19]: https://github.com/apache/couchdb-documentation/pull/445
[20]: https://github.com/apache/couchdb-documentation/pull/437
[21]: https://github.com/apache/couchdb/issues/2168
[22]: https://github.com/apache/couchdb/pull/2092
[23]: https://github.com/apache/couchdb/issues/1523
[24]: https://github.com/apache/couchdb/issues/2167
[25]: https://github.com/apache/couchdb/issues/2166
[26]: https://docs.couchdb.org/en/stable/whatsnew/2.2.html
[27]: https://github.com/apache/couchdb/pull/1330
[28]: https://github.com/apache/couchdb/issues/2165
[29]: https://github.com/apache/couchdb/issues/2191
[30]: https://github.com/apache/couchdb-documentation/pull/276
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [couchdb-docker] wohali commented on issue #85: Provide and publish arm64 images
wohali commented on issue #85: Provide and publish arm64 images URL: https://github.com/apache/couchdb-docker/issues/85#issuecomment-537608544 @lag-linaro fyi I've just been forwarded on to AWS by ARM, something may materialise, but no promises have been made about not having to pay yet. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb-docker] lag-linaro commented on issue #85: Provide and publish arm64 images
lag-linaro commented on issue #85: Provide and publish arm64 images URL: https://github.com/apache/couchdb-docker/issues/85#issuecomment-537607927 Leave it with me, I'll see what I can do. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb-docker] kocolosk commented on issue #68: Provide and publish ppc64le images
kocolosk commented on issue #68: Provide and publish ppc64le images URL: https://github.com/apache/couchdb-docker/issues/68#issuecomment-537607301 Sure we can cover that. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb-docker] wohali commented on issue #68: Provide and publish ppc64le images
wohali commented on issue #68: Provide and publish ppc64le images URL: https://github.com/apache/couchdb-docker/issues/68#issuecomment-537605735 @sarveshtamba Yes, we need 2x ppc64le machines against which to test. The hadoop machine is hands-off for us, and we can't rely on just the one other machine. I can push out packages for 2.3.1 but until we have those 2x machines I can't agree to a 3.0.0 package or image release. @kocolosk will the VM credits IBM is providing be able to cover 2x ppc64le Jenkins nodes? If so then there's no need for @sarveshtamba to look any further. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb-docker] wohali commented on issue #85: Provide and publish arm64 images
wohali commented on issue #85: Provide and publish arm64 images URL: https://github.com/apache/couchdb-docker/issues/85#issuecomment-537605403 @lag-linaro Sorry for the frustration here, neither Works On Arm nor ARM themselves have been able to provide the 2x aarch64 nodes we need to integrate this into our CI workflow yet. This is incredibly frustrating. I can get aarch64 and ppc64le out for 2.3.1, but those machines need to appear before we can push a 3.0.0 release as there have been major changes on master since 2.3.1. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb-fauxton] wohali commented on issue #1227: Add Search support
wohali commented on issue #1227: Add Search support URL: https://github.com/apache/couchdb-fauxton/pull/1227#issuecomment-537584912 One idea, if you would rather use the Apache docker image (I'd prefer it frankly) would be to clone the `apache/couchdb-docker` repo, then build the `dev` Docker image from it, and then use that to run your tests. Would add about 5-10 mins to your build time, which shouldn't be horrible. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb] wohali commented on issue #2169: Remove support for ?stale query parameter in favor of `stable` and `update_after` combo
wohali commented on issue #2169: Remove support for ?stale query parameter in favor of `stable` and `update_after` combo URL: https://github.com/apache/couchdb/issues/2169#issuecomment-537584204 I don't really care either way, but this was something that whomever put in the new behaviour (@banjiewen perhaps?) wanted to deprecate. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb-documentation] nono opened a new pull request #448: Add a warning for $lt and $gt with strings
nono opened a new pull request #448: Add a warning for $lt and $gt with strings URL: https://github.com/apache/couchdb-documentation/pull/448 Comparison of strings with mango selectors `$gt` and `$lt` and be surprising. Let's add a warning about that. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb] rnewson commented on issue #2217: Update fauxton to version 1.1.20
rnewson commented on issue #2217: Update fauxton to version 1.1.20 URL: https://github.com/apache/couchdb/pull/2217#issuecomment-537540480 @willholley I added the 'add search support' PR to the Couchdb 3.0 roadmap (https://github.com/apache/couchdb/projects/1) so we don't forget. This PR is solely for the item to move us up to 1.1.20, which adds some fauxton goodness for partitioned dbs. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb] rnewson commented on issue #2217: Update fauxton to version 1.1.20
rnewson commented on issue #2217: Update fauxton to version 1.1.20 URL: https://github.com/apache/couchdb/pull/2217#issuecomment-537539896 @willholley that would presumably make a fauxton 1.1.21 or so? happy to bump it again if apache/couchdb-fauxton#1227 lands in time. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb] willholley commented on issue #2217: Update fauxton to version 1.1.20
willholley commented on issue #2217: Update fauxton to version 1.1.20 URL: https://github.com/apache/couchdb/pull/2217#issuecomment-537538145 prior to release it would be good to get https://github.com/apache/couchdb-fauxton/pull/1227 in. This is currently blocked on getting the test suite to pass against CouchDB master. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb] sploders101 commented on issue #1514: Query Server Protocol v2
sploders101 commented on issue #1514: Query Server Protocol v2 URL: https://github.com/apache/couchdb/issues/1514#issuecomment-537535667 @kocolosk That's good to know, thanks! @davisp Thank you for the clarification! I was just submitting an issue I'm having with the current query server protocol and found this (seeing that it was open and had activity). Wohali's comment is what concerned me, talking about getting rid of the query server entirely, but it seems I misunderstood. Using a well-defined protocol for query servers should be more than fine. If you are doing something network-based though, unix sockets may be worth looking into. I'm not sure how they are done in erlang, but the C/C++ api is almost identical to that of TCP. I believe the only difference is in construction, due to the fact that it uses a file path instead of a network address. I'm excited to see where this goes! Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb] rnewson commented on issue #2169: Remove support for ?stale query parameter in favor of `stable` and `update_after` combo
rnewson commented on issue #2169: Remove support for ?stale query parameter in favor of `stable` and `update_after` combo URL: https://github.com/apache/couchdb/issues/2169#issuecomment-537534962 Given that the behaviours themselves continues to be supported (albeit independently), I don't think we should remove these options; they are both reasonable combinations of the new `stable` and `update` options. +1 for a WONTFIX from me also. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb] rnewson opened a new pull request #2217: Update fauxton to version 1.1.20
rnewson opened a new pull request #2217: Update fauxton to version 1.1.20 URL: https://github.com/apache/couchdb/pull/2217 # Overview Update Fauxton to version 1.1.20 ## Testing recommendations N/A ## Related Issues or Pull Requests https://github.com/apache/couchdb/issues/2177 ## Checklist - [ ] Code is written and works correctly - [ ] Changes are covered by tests - [ ] Any new configurable parameters are documented in `rel/overlay/etc/default.ini` - [ ] A PR for documentation changes has been made in https://github.com/apache/couchdb-documentation The checklist does not apply in this case. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb-docker] lag-linaro commented on issue #85: Provide and publish arm64 images
lag-linaro commented on issue #85: Provide and publish arm64 images URL: https://github.com/apache/couchdb-docker/issues/85#issuecomment-537488820 Just over 2 weeks has gone. Any luck? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb-docker] ljkenny removed a comment on issue #85: Provide and publish arm64 images
ljkenny removed a comment on issue #85: Provide and publish arm64 images URL: https://github.com/apache/couchdb-docker/issues/85#issuecomment-537488454 Just over 2 weeks has gone. Any luck? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb-docker] ljkenny commented on issue #85: Provide and publish arm64 images
ljkenny commented on issue #85: Provide and publish arm64 images URL: https://github.com/apache/couchdb-docker/issues/85#issuecomment-537488454 Just over 2 weeks has gone. Any luck? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb-pkg] Lesterpig closed issue #54: Latest snap update destroyed all databases
Lesterpig closed issue #54: Latest snap update destroyed all databases URL: https://github.com/apache/couchdb-pkg/issues/54 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb-pkg] Lesterpig commented on issue #54: Latest snap update destroyed all databases
Lesterpig commented on issue #54: Latest snap update destroyed all databases URL: https://github.com/apache/couchdb-pkg/issues/54#issuecomment-537473664 It seems I was one of the only few that experienced this issue. Time to close I think, thanks for your help :) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [couchdb-nano] glynnbird commented on issue #184: Error: Invalid operator: $regex
glynnbird commented on issue #184: Error: Invalid operator: $regex
URL: https://github.com/apache/couchdb-nano/issues/184#issuecomment-537370120
First of all the regex operator is very slow and an index can't be used to
speed it up. It will inevitable cause CouchDB to do a full database scan
(looking through each document body in turn) to get your answer. If you are
looking for "all documents containing 'cat'" then you need to index each word
in the string in question, which is what `type: 'text'` indexes are for.
Unfortunately they are not baked into CouchDB today (stay tuned for CouchDB 3.0
which should have free-text search baked in).
Without the Lucene-based free-text search index, you're a bit stuck. You
could roll your own index with a MapReduce index like so?:
```js
function(doc) {
// break "str" into words
var words = doc.str.split(/\W/);
for(var i in words) {
if (words[i]) {
// create an index with the lower-cased word as the key
emit(words[i].toLowerCase(), null)
}
}
}
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
