[jira] [Commented] (COUCHDB-1792) Query to a view fails with {os_process_error,{exit_status,1}}
[
https://issues.apache.org/jira/browse/COUCHDB-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849984#comment-13849984
]
Randall Leeds commented on COUCHDB-1792:
It says it in the help: "specify that the runtime should allow at most SIZE
bytes of memory to be allocated". Maybe we should note the default? It's 64MB.
> Query to a view fails with {os_process_error,{exit_status,1}}
> -
>
> Key: COUCHDB-1792
> URL: https://issues.apache.org/jira/browse/COUCHDB-1792
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core, View Server Support
>Reporter: Arpit
>Assignee: Dave Cottlehuber
> Fix For: 1.3.1, 1.4.0
>
> Attachments: 0001-couchjs-make-stack-size-option-effective.patch
>
>
> I have a heavy JSON document around 5MB in size. I installed couchdb 1.3,
> spidermonkey 1.8.5 from source on a unix box. Upon querying a view having
> this heavy document I get the following error intermittently (once in a 2
> queries)
> The same operations never fails on my windows box but does fail sometimes on
> this unix installation which built from source.
> Stacktrace:
> [Fri, 10 May 2013 22:35:52 GMT] [error] [<0.187.0>] OS Process Error
> <0.189.0> :: {os_process_error,{exit_status,1}}
> [Fri, 10 May 2013 22:35:52 GMT] [error] [emulator] Error in process <0.187.0>
> with exit value:
> {{nocatch,{os_process_error,{exit_status,1}}},[{couch_os_process,prompt,2
> },{couch_query_servers,map_doc_raw,2},{couch_mrview_updater,'-map_docs/2-fun-0-',3},{lists,foldl,3},{couch_mrview_updater,map_docs,2}]}
> [Fri, 10 May 2013 22:35:52 GMT] [debug] [<0.108.0>] Minor error in HTTP
> request: {os_process_error,{exit_status,1}}
> [Fri, 10 May 2013 22:35:52 GMT] [debug] [<0.108.0>] Stacktrace:
> [{couch_mrview_util,get_view,4},
> {couch_mrview,query_view,6},
> {couch_httpd,etag_maybe,2},
> {couch_mrview_http,design_doc_view,5},
> {couch_httpd_db,do_db_req,2},
> {couch_httpd,handle_request_int,5},
> {mochiweb_http,headers,5},
> {proc_lib,init_p_do_apply,3}]
> [Fri, 10 May 2013 22:35:52 GMT] [info] [<0.108.0>] 10.36.3.4 - - GET
> /config-store-test/_design/queries/_view/docsByName?key=%22Arpit10%22&include_docs=true
> 500
> [Fri, 10 May 2013 22:35:52 GMT] [error] [<0.108.0>] httpd 500 error response:
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
couchdb pull request: Ship single full document default config file.
Github user kxepal closed the pull request at: https://github.com/apache/couchdb/pull/120
couchdb pull request: Ship single full document default config file.
GitHub user kxepal opened a pull request: https://github.com/apache/couchdb/pull/120 Ship single full document default config file. The default.ini becomes really solid default config file with full set of options with short documentation and default values. The big warning alerts you, that any changes made in default.ini might be overwritten and suggests you to use local.ini for any modifications instead. The local.ini is removed and doesn't ships with new CouchDB installations. This also resolves issue when after CouchDB upgrade package manager asks users to merge their local.ini with shipped one. However, when CouchDB starts it checks for local.ini existence and will create it if missed to keep there all config options modifications. COUCHDB-1744 You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/couchdb 1744-single-config-file Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb/pull/120.patch commit 1c344a9669f6b3b6bafeac82ddc29a52d3eccf18 Author: Alexander Shorin Date: 2013-07-06T23:54:45Z Ship single full document default config file. The default.ini becomes really solid default config file with full set of options with short documentation and default values. The big warning alerts you, that any changes made in default.ini might be overwritten and suggests you to use local.ini for any modifications instead. The local.ini is removed and doesn't ships with new CouchDB installations. This also resolves issue when after CouchDB upgrade package manager asks users to merge their local.ini with shipped one. However, when CouchDB starts it checks for local.ini existence and will create it if missed to keep there all config options modifications. COUCHDB-1744
[jira] [Commented] (COUCHDB-1986) 04-replication-large-atts.t times out
[ https://issues.apache.org/jira/browse/COUCHDB-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849663#comment-13849663 ] ASF subversion and git services commented on COUCHDB-1986: -- Commit 74e0f08f72f8c002674159a4f765991f101abddc in branch refs/heads/1744-single-config-file from [~benoitc] [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=74e0f08 ] don't crash if ibrowse is already started fix #COUCHDB-1986 > 04-replication-large-atts.t times out > - > > Key: COUCHDB-1986 > URL: https://issues.apache.org/jira/browse/COUCHDB-1986 > Project: CouchDB > Issue Type: Bug > Components: Replication >Affects Versions: 1.5.0 >Reporter: Jan Lehnardt > > 04-replication-large-atts.t gets stuck around 558, sometimes a little earlier > or later, but it times out eventually, regardless of the timeout. I tried > doubling and such. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (COUCHDB-1744) Make the config file optional
[ https://issues.apache.org/jira/browse/COUCHDB-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849664#comment-13849664 ] ASF subversion and git services commented on COUCHDB-1744: -- Commit 1c344a9669f6b3b6bafeac82ddc29a52d3eccf18 in branch refs/heads/1744-single-config-file from [~kxepal] [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=1c344a9 ] Ship single full document default config file. The default.ini becomes really solid default config file with full set of options with short documentation and default values. The big warning alerts you, that any changes made in default.ini might be overwritten and suggests you to use local.ini for any modifications instead. The local.ini is removed and doesn't ships with new CouchDB installations. This also resolves issue when after CouchDB upgrade package manager asks users to merge their local.ini with shipped one. However, when CouchDB starts it checks for local.ini existence and will create it if missed to keep there all config options modifications. COUCHDB-1744 > Make the config file optional > - > > Key: COUCHDB-1744 > URL: https://issues.apache.org/jira/browse/COUCHDB-1744 > Project: CouchDB > Issue Type: Improvement >Reporter: Dave Cottlehuber > Labels: gsoc, mentor > > 1) move defaults into the code > 2) instead of local/default, ship a fully complete config with all of its > lines commented out > This will make everybody's life simpler. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
Re: [docs] Analytics on docs.couchdb.org
Hi all,
this is done. Alex pasted the GA id to the RTD admin panel. Could you
confirm, that there are incoming tracking requests in GA for the ID
UA-658988-6?
http://snag.gy/XKxxX.jpg
Cheers
Andy
On 12 December 2013 00:04, Andy Wenk wrote:
> On 11 December 2013 22:27, Jan Lehnardt wrote:
>
>>
>> On 11 Dec 2013, at 21:46 , Andy Wenk wrote:
>>
>> > On 4 December 2013 16:41, Noah Slater wrote:
>> > Okay, we have this:
>> >
>> > https://support.google.com/analytics/answer/1032400?hl=en
>> >
>> > > For more information on implementing multiple instances of the
>> tracking code with the analytics.js library, consult the Analytics
>> Developer Guide.
>> >
>> > If someone wants to look at this and prepare the code needed to add a
>> > second tracking code, I can provide the tracking ID. (I have access to
>> > the main CouchDB GA account.)
>> >
>> > I had a look at this. As far as I understood, we just need to add
>> >
>> > ga('create', 'UA-12345-6', 'auto', {'name': 'docs-couchdb'});
>> > ga('docs-couchdb.send', 'pageview');
>> >
>> > (where UA-12345-6 has to be replaced with the CouchDB tracking ID)
>> >
>> > to a feasible place - at the end it could be the searchbox template
>> proposed by Benjamin. Noah, if you send me the ID I will check this and add
>> it ...
>>
>> UA-658988-6
>>
>> Thanks!
>> Jan
>> --
>>
>
> I have added the code in the branch ga-couchdbdocs. Please review. Be
> aware, that the tracking will not be fired unless you run the docs in a
> server ... like a local nginx ...
>
> Feel free to change and or merge into master :)
>
> Cheers
>
> Andy
> --
> Andy Wenk
> Hamburg - Germany
> RockIt!
>
> http://www.couchdb-buch.de
> http://www.pg-praxisbuch.de
>
> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
>
--
Andy Wenk
Hamburg - Germany
RockIt!
http://www.couchdb-buch.de
http://www.pg-praxisbuch.de
GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
https://people.apache.org/keys/committer/andywenk.asc
[jira] [Commented] (COUCHDB-523) View API POST keys to retrieve multiple docs by key could also allow for multiple 'range' queries, i.e. an array of { startkey: .., endkey: ... } params in the POST
[
https://issues.apache.org/jira/browse/COUCHDB-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849643#comment-13849643
]
Joan Touzet commented on COUCHDB-523:
-
Hi Amza, thanks for your offer of help.
This is a fairly difficult bug, not one I'd recommend for a new Erlanger. I'm
currently working on COUCHDB-1334 and will be moving to this bug immediately
after that.
Please be patient :)
> View API POST keys to retrieve multiple docs by key could also allow for
> multiple 'range' queries, i.e. an array of { startkey: .., endkey: ... }
> params in the POST
>
>
> Key: COUCHDB-523
> URL: https://issues.apache.org/jira/browse/COUCHDB-523
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
>Reporter: Nathan Stott
>Assignee: Joan Touzet
>Priority: Minor
> Attachments: couch_httpd_view.erl, multi_start_end_key.diff,
> ranged_key_post.diff
>
>
> It would be useful if I could do a single POST to a view to retrieve multiple
> ranges specified by startkey, endkey.
> The format could be as follows:
> { "ranges": [ { "startkey": "a", "endkey": "c" }, { "startkey":"g",
> "endkey":"z" } ] }
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (COUCHDB-1986) 04-replication-large-atts.t times out
[ https://issues.apache.org/jira/browse/COUCHDB-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849272#comment-13849272 ] Jan Lehnardt commented on COUCHDB-1986: --- Some more testing today, bumping the test timeout waiting for replication to finish from 30 to 60 makes this pass again. Looking at the request log can see that PUTing docs to the remote db takes disproportionally long (1 minute + a few seconds each): [Mon, 16 Dec 2013 12:23:27 GMT] [info] [<0.321.0>] 127.0.0.1 - - PUT /couch_test_rep_db_b/_local/8831f8738bd5d17e00da7 1581b23 201 [Mon, 16 Dec 2013 12:24:30 GMT] [info] [<0.322.0>] 127.0.0.1 - - PUT /couch_test_rep_db_b/doc5?new_edits=false 201 [Mon, 16 Dec 2013 12:25:38 GMT] [info] [<0.322.0>] 127.0.0.1 - - PUT /couch_test_rep_db_b/doc4?new_edits=false 201 [Mon, 16 Dec 2013 12:26:51 GMT] [info] [<0.322.0>] 127.0.0.1 - - PUT /couch_test_rep_db_b/doc3?new_edits=false 201 [Mon, 16 Dec 2013 12:27:58 GMT] [info] [<0.322.0>] 127.0.0.1 - - PUT /couch_test_rep_db_b/doc2?new_edits=false 201 [Mon, 16 Dec 2013 12:29:06 GMT] [info] [<0.322.0>] 127.0.0.1 - - PUT /couch_test_rep_db_b/doc11?new_edits=false 201 [Mon, 16 Dec 2013 12:30:13 GMT] [info] [<0.322.0>] 127.0.0.1 - - PUT /couch_test_rep_db_b/doc10?new_edits=false 201 [Mon, 16 Dec 2013 12:31:20 GMT] [info] [<0.322.0>] 127.0.0.1 - - PUT /couch_test_rep_db_b/doc1?new_edits=false 201 [Mon, 16 Dec 2013 12:31:20 GMT] [info] [<0.322.0>] 127.0.0.1 - - POST /couch_test_rep_db_b/_ensure_full_commit 201 After the last one all other requests come in at expected speeds. I’m not too familiar with this part of the replicator code, so I couldn’t quickly find why either the requests take that long, or why the replicator waits a minute until it continues. Another thing I tried was seeing whether the new R16B scheduling behaviour introduced this, but running the test with > ERL_FLAGS="+sws legacy" ./test/etap/run -v > src/couch_replicator/test/04-replication-large-atts.t and the original timeout still times out. > 04-replication-large-atts.t times out > - > > Key: COUCHDB-1986 > URL: https://issues.apache.org/jira/browse/COUCHDB-1986 > Project: CouchDB > Issue Type: Bug > Components: Replication >Affects Versions: 1.5.0 >Reporter: Jan Lehnardt > > 04-replication-large-atts.t gets stuck around 558, sometimes a little earlier > or later, but it times out eventually, regardless of the timeout. I tried > doubling and such. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
Re: git commit: updated refs/heads/ga-couchdbdocs to 850eafb
Alex can you help me with the question below?
Thanks and Cheers
Andy
On 12 December 2013 11:52, Andy Wenk wrote:
> I already thought about if there is a way in RTD to provide a GA tracker
> ID but could not finde anything in the sources. Can you point me to the
> "project's
> admin panel on
> RTD". I don't know about that ...
>
> On 12 December 2013 00:28, Alexander Shorin wrote:
>
>> I think it's better to add tracking number in project's admin panel on
>> RTD . There is special field about:
>>
>> Analytics code: Google Analytics Tracking ID (ex. UA-22345342-1). This
>> may slow down your page loads.
>> --
>> ,,,^..^,,,
>>
>>
>> On Thu, Dec 12, 2013 at 3:24 AM, Alexander Shorin
>> wrote:
>> > Do we ship GA tracker with CouchDB releases?(:
>> > --
>> > ,,,^..^,,,
>> >
>> >
>> > On Thu, Dec 12, 2013 at 3:01 AM, wrote:
>> >> Updated Branches:
>> >> refs/heads/ga-couchdbdocs [created] 850eafbdd
>> >>
>> >>
>> >> added google analytics code to docs
>> >>
>> >>
>> >> Project: http://git-wip-us.apache.org/repos/asf/couchdb/repo
>> >> Commit: http://git-wip-us.apache.org/repos/asf/couchdb/commit/850eafbd
>> >> Tree: http://git-wip-us.apache.org/repos/asf/couchdb/tree/850eafbd
>> >> Diff: http://git-wip-us.apache.org/repos/asf/couchdb/diff/850eafbd
>> >>
>> >> Branch: refs/heads/ga-couchdbdocs
>> >> Commit: 850eafbddc0b7c5600dc6f642c33e313f2b57279
>> >> Parents: 9c641f1
>> >> Author: Andy Wenk
>> >> Authored: Thu Dec 12 00:01:02 2013 +0100
>> >> Committer: Andy Wenk
>> >> Committed: Thu Dec 12 00:01:02 2013 +0100
>> >>
>> >> --
>> >> share/doc/static/ga-couchdbdocs.js | 6 ++
>> >> share/doc/templates/searchbox.html | 1 +
>> >> 2 files changed, 7 insertions(+)
>> >> --
>> >>
>> >>
>> >>
>> http://git-wip-us.apache.org/repos/asf/couchdb/blob/850eafbd/share/doc/static/ga-couchdbdocs.js
>> >> --
>> >> diff --git a/share/doc/static/ga-couchdbdocs.js
>> b/share/doc/static/ga-couchdbdocs.js
>> >> new file mode 100644
>> >> index 000..6276f60
>> >> --- /dev/null
>> >> +++ b/share/doc/static/ga-couchdbdocs.js
>> >> @@ -0,0 +1,6 @@
>> >>
>> +(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
>> >> +(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new
>> Date();a=s.createElement(o),
>> >>
>> +m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
>> >> +})(window,document,'script','//www.google-analytics.com/analytics.js
>> ','ga');
>> >> +ga('create', 'UA-658988-6', 'auto', {'name': 'couchdbdocs'});
>> >> +ga('couchdbdocs.send', 'pageview');
>> >> \ No newline at end of file
>> >>
>> >>
>> http://git-wip-us.apache.org/repos/asf/couchdb/blob/850eafbd/share/doc/templates/searchbox.html
>> >> --
>> >> diff --git a/share/doc/templates/searchbox.html
>> b/share/doc/templates/searchbox.html
>> >> index fa12a7f..7926b15 100644
>> >> --- a/share/doc/templates/searchbox.html
>> >> +++ b/share/doc/templates/searchbox.html
>> >> @@ -29,3 +29,4 @@ specific language governing permissions and
>> limitations under the License.
>> >>
>> >>
>> >> $('#searchbox').show(0);
>> >> +
>> >>
>>
>
>
>
> --
> Andy Wenk
> Hamburg - Germany
> RockIt!
>
> http://www.couchdb-buch.de
> http://www.pg-praxisbuch.de
>
> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
>
--
Andy Wenk
Hamburg - Germany
RockIt!
http://www.couchdb-buch.de
http://www.pg-praxisbuch.de
GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
https://people.apache.org/keys/committer/andywenk.asc
Re: Writing a Plugin : know couchdb core
Hi Alexander and Jan, Thank you both of us for your answers. I understand that the best way to learn is to dig into the code, I will use this You gave me some good resources to complete the knowledge. Especially the erlang one; in fact, I'm not so afraid by how the erlang code is presented, but I might end up to use it in a too basic way and not use its whole power, so having an erlang doc will be also very useful. Good idea also to look at another auth plugin, and I suppose that if you mentioned the XO_Auth to me, it means that it is well built (would be a pity to copy a bad project !) Yes, I'll keep the list posted about how it goes, most probably after the Holidays. As I mentioned in one of my first emails, if you already have some drafts for the planned developer guide, I might help to enhance it once I learned some more stuff ! Cheers, Franck On 14/12/2013 10:41, Alexander Shorin wrote: Hey Franck! On Sat, Dec 14, 2013 at 1:02 PM, Franck Eyraud wrote: It seems that plugin discussions don't create passionate debates... It's a pity because it is really a good feature, and since from what I understood taht the couchdb core might be reduced in the future, plugins will be always used more. There is nothing to discuss - it's very useful plugin and great idea to implement! Don't think that nobody cares because there was no responses from devs: most of them on CouchHack now and focused on code, fork merges and CouchDB (: Maybe creating a plugin is not a in itself problem. I watched the interesting talk[1] from Jason Smith which is a very good start. And it made me realize that writing a plugin is in fact equivalent to writing a bit of code in couchdb core. So what I need is to learn what a couchdb developer knows : couchdb architecture and API. Is there any resource online where I can learn this stuff ? A quick start guide to develop in couchdb (especially for people who never used erlang before) ? Or is the only way to dig inside couchdb git tree and try to understand ? Before doing this, I want to be sure I won't loose too much time. So please people who entered the couchdb project later, how did you reach your level ? Actually, there are plans to have such in our docs for developers guide section, but currently there is no any "official" information about. But we're working on to fix this (: However, you may found some useful blog posts over Internet and projects that are already hacked into CouchDB. For instance, you would love to see similar project that implements custom authentication with 3d party service: https://github.com/ocastalabs/CouchDB-XO_Auth About how to start...locate interesting module, take a look on his commit history, find out interesting functions, write some tests about to check and ensure in his behaviour or read existed ones. After that, create your own test case - it will be all "red", but thats ok. Trying to make it "green" will be your goal during developing or hacking. Don't make it too detailed from start, but you'll be happy to extend and improve it while adding new functions and featured. Not the best plan, but something to start from (; But anyway, don't fear erlang, don't fear write stuff and see it broken: in most cases it's easy to fix things quickly after 5 minutes googling or reading erlang docs or lyse[1]. Happy hacking! [1]: http://learnyousomeerlang.com/ -- ,,,^..^,,,
[jira] [Commented] (COUCHDB-523) View API POST keys to retrieve multiple docs by key could also allow for multiple 'range' queries, i.e. an array of { startkey: .., endkey: ... } params in the POST
[
https://issues.apache.org/jira/browse/COUCHDB-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849103#comment-13849103
]
Amza OUSSEY commented on COUCHDB-523:
-
Hello,
any patch for current version?
I started learning erlang yesterday for that purpose.
> View API POST keys to retrieve multiple docs by key could also allow for
> multiple 'range' queries, i.e. an array of { startkey: .., endkey: ... }
> params in the POST
>
>
> Key: COUCHDB-523
> URL: https://issues.apache.org/jira/browse/COUCHDB-523
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
>Reporter: Nathan Stott
>Assignee: Joan Touzet
>Priority: Minor
> Attachments: couch_httpd_view.erl, multi_start_end_key.diff,
> ranged_key_post.diff
>
>
> It would be useful if I could do a single POST to a view to retrieve multiple
> ranges specified by startkey, endkey.
> The format could be as follows:
> { "ranges": [ { "startkey": "a", "endkey": "c" }, { "startkey":"g",
> "endkey":"z" } ] }
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
