set_view_outdated errors from couchdb should not be logged with log level error

SUBJ. Here's what I'm seeing in ns_server's debug logs:

[couchdb:error,2012-10-16T8:39:21.575,ns_1@10.6.2.66:<0.15946.177>:couch_log:error:42]Uncaught error in HTTP request: {throw,{error,set_view_outdated}}

Stacktrace: [

{couch_view_merger,simple_set_view_query,3},
{couch_httpd,handle_request,6},
{mochiweb_http,headers,5},
{proc_lib,init_p_do_apply,3}]
[couchdb:error,2012-10-16T8:39:21.587,ns_1@10.6.2.66:<0.15700.177>:couch_log:error:42]Uncaught error in HTTP request: {throw,{error,set_view_outdated}}

Stacktrace: [{couch_view_merger,simple_set_view_query,3}

,

{couch_httpd,handle_request,6},
{mochiweb_http,headers,5},
{proc_lib,init_p_do_apply,3}]
[couchdb:error,2012-10-16T8:39:21.593,ns_1@10.6.2.66:<0.20790.169>:couch_log:error:42]Uncaught error in HTTP request: {throw,{error,set_view_outdated}}

Stacktrace: [{couch_view_merger,simple_set_view_query,3},
{couch_httpd,handle_request,6}

,

{mochiweb_http,headers,5},
{proc_lib,init_p_do_apply,3}]
[couchdb:error,2012-10-16T8:39:21.596,ns_1@10.6.2.66:<0.25760.177>:couch_log:error:42]Uncaught error in HTTP request: {throw,{error,set_view_outdated}}

Stacktrace: [{couch_view_merger,simple_set_view_query,3},
{couch_httpd,handle_request,6},
{mochiweb_http,headers,5}

,

{proc_lib,init_p_do_apply,3}]
[couchdb:error,2012-10-16T8:39:21.606,ns_1@10.6.2.66:<0.4477.177>:couch_log:error:42]Uncaught error in HTTP request: {throw,{error,set_view_outdated}}

Stacktrace: [{couch_view_merger,simple_set_view_query,3},
{couch_httpd,handle_request,6},
{mochiweb_http,headers,5},
{proc_lib,init_p_do_apply,3}

]
[couchdb:error,2012-10-16T8:39:21.607,ns_1@10.6.2.66:<0.16542.176>:couch_log:error:42]Uncaught error in HTTP request: {throw,{error,set_view_outdated}}

Stacktrace: [

{couch_view_merger,simple_set_view_query,3}

,

{couch_httpd,handle_request,6}

,

{mochiweb_http,headers,5}

,

{proc_lib,init_p_do_apply,3}

]
[couchdb:error,2012-10-16T8:39:21.607,ns_1@10.6.2.66:<0.1649.176>:couch_log:error:42]Uncaught error in HTTP request: {throw,{error,set_view_outdated}}

lots of messages like that. As far as I understand, this is somewhat expected during rebalance. Which makes it expected log message from data path. And not really error. IMHO, should be fixed.

I'd like this to be fixed for 2.0, but not sure if that matches other thinking