couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1446) Config settings input validation
Date Tue, 20 Mar 2012 07:05:57 GMT

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

Paul Joseph Davis commented on COUCHDB-1446:
--------------------------------------------

I understand your concern, but (at least at this hour after a few beers) I'm not seeing much
of a distinction. A "validate all the inputs" doesn't seem far off the (IMO simpler) reorganization
to Erlang term format.

IMO, the immediate solution to this patch is fixing the bug the user encounter at the source
where the config value is used and the fancier validation split off as its own thing.
                
> Config settings input validation
> --------------------------------
>
>                 Key: COUCHDB-1446
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1446
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 1.2
>            Reporter: Jason Smith
>            Assignee: Jason Smith
>            Priority: Minor
>              Labels: config
>
> Today I received a bug report from a user who thought CouchDB might be relaxing and evaluate
an arithmetic expression in the config. (That makes sense, since it seems to evaluate erlang
terms elsewhere.)
> https://getsatisfaction.com/iriscouch/topics/my_couchdb_is_broken_after_putting_a_badarg_for_a_configuration_value
> It would be nice for CouchDB to validate config input, particularly when bad values permanently
take it offline. (In this case, it returns 500 for all subsequent requests.)
> IMO, a good bang-for-buck is to have three basic value types:
> 1. String
> 2. Erlang tuple
> 3. Integer
> And each setting knows what type it must be.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message