couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Chesneau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1894) Add experimental NodeJS query server
Date Wed, 25 Sep 2013 13:26:09 GMT

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

Benoit Chesneau commented on COUCHDB-1894:
------------------------------------------

releasing new features is fine. But I would be really cautious on that one, the last thing
we want is to break a machine because we used too much ram, cpu or whatever. Which can happen
very rapidly on a loaded machine with a lot of view indexations or filtered replications.

In this case I don't think it's really difficult to go for the model I describe from the current
patch anyway this is "just" a matter of having the dispatching done at another level. All
what I say is that it may worth to take the time to see if this patch could be improved that
way. 

We can iterate in different branches or not. Like I see it there could be 2 works done simultaneously
on that patch:

- check/improve the sandboxing
- try to improve the multiprocessing model

At some point we can just decide to ship the current version ("current" as the working version
at the time we are looking at it) and continue to iterate on top of it. But I don't see the
point of having 2 tickets for the same feature. nothing stop us to keep open a ticket across
release until we know the state in the shipped release.
                
> Add experimental NodeJS query server
> ------------------------------------
>
>                 Key: COUCHDB-1894
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1894
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: JavaScript View Server
>            Reporter: Jan Lehnardt
>
> Let’s clean up and merge Jason Smith’s Node.js query server into ASF land and ship
it as opt-in and experimental.
> I’ve prepared a branch that does the following:
>  - remove fancy extra features like app server handlers and the visual debugger support
for now
>  - make it a drop-in replacement for couchjs
>  - bundle the code in src/couchjs-node
>  - add a new query server language “nodejs” that people can use
>  - include sandbox.js from https://github.com/KlausTrainer/sandbox.js (not hooked up
yet)
> The query server is not installed by default and users can install them in two ways:
> 1. from source:
>     $ cd src/couchjs-node
>     $ npm link
> 2. from NPM:
>     $ npm install couchjs # add @1.x.x for once the module mirrors CouchDB version numbers
for forward compat)
> And then they can uncomment and update the [query_server] line in local.ini.
> * * *
> Open work items on the view server:
>  - make it work with CLI tests
>  - fix remaining test cases in web test runner
>  - hook up sandbox.js from https://github.com/KlausTrainer/sandbox.js

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message