CouchDB API Server Miscellaneous Methods

Reply-To: dev@couchdb.apache.org Delivered-To: mailing list commits@couchdb.apache.org Received: (qmail 14302 invoked by uid 99); 6 Dec 2012 11:34:42 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2012 11:34:42 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id E4734819714; Thu, 6 Dec 2012 11:34:41 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: jan@apache.org To: commits@couchdb.apache.org X-Mailer: ASF-Git Admin Mailer Subject: [33/50] [abbrv] import Couchbase docs Message-Id: <20121206113441.E4734819714@tyr.zones.apache.org> Date: Thu, 6 Dec 2012 11:34:41 +0000 (UTC) http://git-wip-us.apache.org/repos/asf/couchdb/blob/fd643691/share/docs/couchdb-manual-1.1/metadoc-couchdb-api-misc.xml ---------------------------------------------------------------------- diff --git a/share/docs/couchdb-manual-1.1/metadoc-couchdb-api-misc.xml b/share/docs/couchdb-manual-1.1/metadoc-couchdb-api-misc.xml new file mode 100644 index 0000000..a9ae882 --- /dev/null +++ b/share/docs/couchdb-manual-1.1/metadoc-couchdb-api-misc.xml @@ -0,0 +1,1412 @@ + + +%every.entities; +]> + + + CouchDB API Server Miscellaneous Methods + + + The CouchDB Miscellaneous interface provides the basic interface to + a CouchDB server for obtaining CouchDB information and getting and + setting configuration information. + + + + A list of the available methods and URL paths are provided below: + + + + + + + +Miscellaneous API CallsMethodPathDescriptionGET/ + Get the welcome message and version information + GET/_active_tasks + Obtain a list of the tasks running in the server + GET/_all_dbs + Get a list of all the DBs + GET/_log + Return the server log file + POST/_replicate + Set or cancel replication + POST/_restart + Restart the server + GET/_stats + Return server statistics + GET/_utils + CouchDB administration interface (Futon) + GET/_uuids + Get generated UUIDs from the server + GET/favicon.ico + Get the site icon +

+ +

+ + <literal>GET /</literal> + + + + + + +URL API GET /MethodGET /Request + None + Response + Welcome message and version + Admin Privileges RequirednoReturn Codes200 + Request completed successfully. + + + + Accessing the root of a CouchDB instance returns meta information + about the instance. The response is a JSON structure containing + information about the server, including a welcome message and the + version of the server. + + + +{ + "couchdb" : "Welcome", + "version" : "1.0.1" +} + + +

+ +

+ + <literal>GET /_active_tasks</literal> + + + + + + +URL API GET /_active_tasksMethodGET /_active_tasksRequest + None + Response + List of running tasks, including the task type, name, status and + process ID + Admin Privileges RequirednoReturn Codes200 + Request completed successfully. + + + + You can obtain a list of active tasks by using the + /_active_tasks URL. The result is a JSON array + of the currently running tasks, with each task being described + with a single object. For example: + + + + +", + "status" : "Copied 0 of 18369 changes (0%)", + "task" : "recipes", + "type" : "Database Compaction" + } +] +]]> + + + + + The returned structure includes the following fields for each + task: + + + + + + + + + List of Active Tasks + FieldDescriptiontasks [array] + Active Task + pid + Process ID + status + Task status message + task + Task name + type + Operation Type +

+ + + For operation type, valid values include: + + + + + + + Database Compaction + + + + + + Replication + + + + + + View Group Compaction + + + + + + View Group Indexer + + + + + +

+ +

+ + <literal>GET /_all_dbs</literal> + + + + + + +URL API GET /_all_dbsMethodGET /_all_dbsRequest + None + Response + JSON list of DBs + Admin Privileges RequirednoReturn Codes200 + Request completed successfully. + + + + Returns a list of all the databases in the CouchDB instance. For + example: + + + +GET http://couchdb:5984/_all_dbs +Accept: application/json + + + + The return is a JSON array: + + + +[ + "_users", + "contacts", + "docs", + "invoices", + "locations" +] + + + +

+ +

+ + <literal>GET /_log</literal> + + + + + + +URL API GET /_logMethodGET /_logRequest + None + Response + Log content + Admin Privileges RequirednoQuery ArgumentsArgumentbytesDescription + Bytes to be returned + OptionalyesTypenumericDefault1000ArgumentoffsetDescription + Offset in bytes where the log tail should be started + OptionalyesTypenumericDefault0Return Codes200 + Request completed successfully. + + + + Gets the CouchDB log, equivalent to accessing the local log file + of the corresponding CouchDB instance. + + + + When you request the log, the response is returned as plain + (UTF-8) text, with an HTTP Content-type header + as text/plain. + + + + For example, the request: + + + +GET http://couchdb:5984/_log +Accept: */* + + + + The raw text is returned: + + + +] 192.168.0.2 - - 'PUT' /authdb 401 + +[Wed, 27 Oct 2010 11:02:19 GMT] [info] [<0.23428.2>] 192.168.0.116 - - 'GET' /recipes/FishStew 200 + +[Wed, 27 Oct 2010 11:02:19 GMT] [info] [<0.23428.2>] 192.168.0.116 - - 'GET' /_session 200 + +[Wed, 27 Oct 2010 11:02:19 GMT] [info] [<0.24199.2>] 192.168.0.116 - - 'GET' / 200 + +[Wed, 27 Oct 2010 13:03:38 GMT] [info] [<0.24207.2>] 192.168.0.116 - - 'GET' /_log?offset=5 200 +]]> + + + + If you want to pick out specific parts of the log information you + can use the bytes argument, which specifies the + number of bytes to be returned, and offset, + which specifies where the reading of the log should start, counted + back from the end. For example, if you use the following request: + + + +GET /_log?bytes=500&offset=2000 + + + + Reading of the log will start at 2000 bytes from the end of the + log, and 500 bytes will be shown. + + +

+ +

+ + <literal>POST /_replicate</literal> + + + + + + +URL API POST /_replicateMethodPOST /_replicateRequest + Replication specification + Response + Welcome message and version + Admin Privileges RequirednoReturn Codes200 + Replication request successfully completed + 202 + Continuous replication request has been accepted + 404 + Either the source or target DB is not found + 500 + JSON specification was invalid + + + + Request, configure, or stop, a replication operation. + + + + The specification of the replication request is controlled through + the JSON content of the request. The JSON should be an object with + the fields defining the source, target and other options. The + fields of the JSON request are shown in the table below: + + + + + + + + + Replication Settings + FieldDescriptioncancel (optional) + Cancels the replication + continuous (optional) + Configure the replication to be continuous + create_target (optional) + Creates the target database + doc_ids (optional) + Array of document IDs to be synchronized + proxy (optional) + Address of a proxy server through which replication should occur + source + Source database name or URL + target + Target database name or URL +

+ +

+ + Replication Operation + + + The aim of the replication is that at the end of the process, + all active documents on the source database are also in the + destination database and all documents that were deleted in the + source databases are also deleted (if they exist) on the + destination database. + + + + Replication can be described as either push or pull replication: + + + + + + + Pull replication is where the + source is the remote CouchDB instance, + and the destination is the local + database. + + + + Pull replication is the most useful solution to use if your + source database has a permanent IP address, and your + destination (local) database may have a dynamically assigned + IP address (for example, through DHCP). This is particularly + important if you are replicating to a mobile or other device + from a central server. + + + + + + Push replication is where the + source is a local database, and + destination is a remote database. + + + + + +

+ +

+ + Specifying the Source and Target Database + + + You must use the URL specification of the CouchDB database if + you want to perform replication in either of the following two + situations: + + + + + + + Replication with a remote database (i.e. another instance of + CouchDB on the same host, or a different host) + + + + + + Replication with a database that requires authentication + + + + + + + For example, to request replication between a database local to + the CouchDB instance to which you send the request, and a remote + database you might use the following request: + + + +POST http://couchdb:5984/_replicate +Content-Type: application/json +Accept: application/json + +{ + "source" : "recipes", + "target" : "http://coucdb-remote:5984/recipes", +} + + + + In all cases, the requested databases in the + source and target + specification must exist. If they do not, an error will be + returned within the JSON object: + + + +{ + "error" : "db_not_found" + "reason" : "could not open http://couchdb-remote:5984/ol1ka/", +} + + + + You can create the target database (providing your user + credentials allow it) by adding the + create_target field to the request object: + + + +POST http://couchdb:5984/_replicate +Content-Type: application/json +Accept: application/json + +{ + "create_target" : true + "source" : "recipes", + "target" : "http://couchdb-remote:5984/recipes", +} + + + + The create_target field is not destructive. + If the database already exists, the replication proceeds as + normal. + + +

+ +

+ + Single Replication + + + You can request replication of a database so that the two + databases can be synchronized. By default, the replication + process occurs one time and synchronizes the two databases + together. For example, you can request a single synchronization + between two databases by supplying the source + and target fields within the request JSON + content. + + + +POST http://couchdb:5984/_replicate +Content-Type: application/json +Accept: application/json + +{ + "source" : "recipes", + "target" : "recipes-snapshot", +} + + + + In the above example, the databases recipes + and recipes-snapshot will be synchronized. + These databases are local to the CouchDB instance where the + request was made. The response will be a JSON structure + containing the success (or failure) of the synchronization + process, and statistics about the process: + + + +{ + "ok" : true, + "history" : [ + { + "docs_read" : 1000, + "session_id" : "52c2370f5027043d286daca4de247db0", + "recorded_seq" : 1000, + "end_last_seq" : 1000, + "doc_write_failures" : 0, + "start_time" : "Thu, 28 Oct 2010 10:24:13 GMT", + "start_last_seq" : 0, + "end_time" : "Thu, 28 Oct 2010 10:24:14 GMT", + "missing_checked" : 0, + "docs_written" : 1000, + "missing_found" : 1000 + } + ], + "session_id" : "52c2370f5027043d286daca4de247db0", + "source_last_seq" : 1000 +} + + + + The structure defines the replication status, as described in + the table below: + + + + + + + + + Replication Status + FieldDescriptionhistory [array] + Replication History + doc_write_failures + Number of document write failures + docs_read + Number of documents read + docs_written + Number of documents written to target + end_last_seq + Last sequence number in changes stream + end_time + Date/Time replication operation completed + missing_checked + Number of missing documents checked + missing_found + Number of missing documents found + recorded_seq + Last recorded sequence number + session_id + Session ID for this replication operation + start_last_seq + First sequence number in changes stream + start_time + Date/Time replication operation started + ok + Replication status + session_id + Unique session ID + source_last_seq + Last sequence number read from source database +

+ +

+ + Continuous Replication + + + Synchronization of a database with the previously noted methods + happens only once, at the time the replicate request is made. To + have the target database permanently replicated from the source, + you must set the continuous field of the JSON + object within the request to true. + + + + With continuous replication changes in the source database are + replicated to the target database in perpetuity until you + specifically request that replication ceases. + + + +POST http://couchdb:5984/_replicate +Content-Type: application/json +Accept: application/json + +{ + "continuous" : true + "source" : "recipes", + "target" : "http://couchdb-remote:5984/recipes", +} + + + + Changes will be replicated between the two databases as long as + a network connection is available between the two instances. + + + + + Two keep two databases synchronized with each other, you need + to set replication in both directions; that is, you must + replicate from databasea to + databaseb, and separately from + databaseb to databasea. + + + +

+ +

+ + Canceling Continuous Replication + + + You can cancel continuous replication by adding the + cancel field to the JSON request object and + setting the value to true. Note that the structure of the + request must be identical to the original for the cancelation + request to be honoured. For example, if you requested continuous + replication, the cancellation request must also contain the + continuous field. + + + + For example, the replication request: + + + +POST http://couchdb:5984/_replicate +Content-Type: application/json +Accept: application/json + +{ + "source" : "recipes", + "target" : "http://couchdb-remote:5984/recipes", + "create_target" : true, + "continuous" : true +} + + + + Must be canceled using the request: + + + +POST http://couchdb:5984/_replicate +Content-Type: application/json +Accept: application/json + +{ + "cancel" : true, + "continuous" : true + "create_target" : true, + "source" : "recipes", + "target" : "http://couchdb-remote:5984/recipes", +} + + + + Requesting cancellation of a replication that does not exist + results in a 404 error. + + +

+ +

+ + <literal>POST /_restart</literal> + + + + + +URL API POST /_restartMethodPOST /_restartRequest + None + Response + JSON status message + Admin Privileges RequiredyesReturn Codes201 + Document created successfully. + + + + Restarts the CouchDB instance. You must be authenticated as a user + with administration privileges for this to work. + + + + For example: + + + +POST http://admin:password@couchdb:5984/_restart + + + + The return value (if the server has not already restarted) is a + JSON status object indicating that the request has been received: + + + +{ + "ok" : true, +} + + + + If the server has already restarted, the header may be returned, + but no actual data is contained in the response. + + +

+ +

+ + <literal>GET /_stats</literal> + + + + + +URL API GET /_statsMethodGET /_statsRequest + None + Response + Server statistics + Admin Privileges RequirednoReturn Codes200 + Request completed successfully. + + + + The _stats method returns a JSON object + containting the statistics for the running server. The object is + structured with top-level sections collating the statistics for a + range of entries, with each individual statistic being easily + identified, and the content of each statistic is self-describing. + For example, the request time statistics, within the + couchdb section are structured as follows: + + + +{ + "couchdb" : { +... + "request_time" : { + "stddev" : "27.509", + "min" : "0.333333333333333", + "max" : "152", + "current" : "400.976", + "mean" : "10.837", + "sum" : "400.976", + "description" : "length of a request inside CouchDB without MochiWeb" + }, +... + } +} + + + + The fields provide the current, minimum and maximum, and a + collection of statistical means and quantities. The quantity in + each case is not defined, but the descriptions below provide + + + + The statistics are divided into the following top-level sections: + + + + + + + couchdb + + + + Describes statistics specific to the internals of CouchDB. + + + + <literal>couchdb</literal> statistics + + + + + + + + Statistic ID + + + Description + + + Unit + + + + + + auth_cache_hits + + + Number of authentication cache hits + + + number + + + + auth_cache_misses + + + Number of authentication cache misses + + + number + + + + database_reads + + + Number of times a document was read from a database + + + number + + + + database_writes + + + Number of times a database was changed + + + number + + + + open_databases + + + Number of open databases + + + number + + + + open_os_files + + + Number of file descriptors CouchDB has open + + + number + + + + request_time + + + Length of a request inside CouchDB without MochiWeb + + + milliseconds + + + + +

+ + + + + httpd_request_methods + + + + <literal>httpd_request_methods</literal> statistics + + + + + + + + Statistic ID + + + Description + + + Unit + + + + + + COPY + + + Number of HTTP COPY requests + + + number + + + + DELETE + + + Number of HTTP DELETE requests + + + number + + + + GET + + + Number of HTTP GET requests + + + number + + + + HEAD + + + Number of HTTP HEAD requests + + + number + + + + POST + + + Number of HTTP POST requests + + + number + + + + PUT + + + Number of HTTP PUT requests + + + number + + + + +

+ + + + + httpd_status_codes + + + + <literal>httpd_status_codes</literal> statistics + + + + + + + + Statistic ID + + + Description + + + Unit + + + + + + 200 + + + Number of HTTP 200 OK responses + + + number + + + + 201 + + + Number of HTTP 201 Created responses + + + number + + + + 202 + + + Number of HTTP 202 Accepted responses + + + number + + + + 301 + + + Number of HTTP 301 Moved Permanently responses + + + number + + + + 304 + + + Number of HTTP 304 Not Modified responses + + + number + + + + 400 + + + Number of HTTP 400 Bad Request responses + + + number + + + + 401 + + + Number of HTTP 401 Unauthorized responses + + + number + + + + 403 + + + Number of HTTP 403 Forbidden responses + + + number + + + + 404 + + + Number of HTTP 404 Not Found responses + + + number + + + + 405 + + + Number of HTTP 405 Method Not Allowed responses + + + number + + + + 409 + + + Number of HTTP 409 Conflict responses + + + number + + + + 412 + + + Number of HTTP 412 Precondition Failed responses + + + number + + + + 500 + + + Number of HTTP 500 Internal Server Error responses + + + number + + + + +

+ + + + + httpd + + + + <literal>httpd</literal> statistics + + + + + + + + Statistic ID + + + Description + + + Unit + + + + + + bulk_requests + + + Number of bulk requests + + + number + + + + clients_requesting_changes + + + Number of clients for continuous _changes + + + number + + + + requests + + + Number of HTTP requests + + + number + + + + temporary_view_reads + + + Number of temporary view reads + + + number + + + + view_reads + + + Number of view reads + + + number + + + + +

+ + + + + + You can also access individual statistics by quoting the + statistics sections and statistic ID as part of the URL path. For + example, to get the request_time statistics, + you can use: + + + +GET /_stats/couchdb/request_time + + + + This returns an entire statistics object, as with the full + request, but containining only the request individual statistic. + Hence, the returned structure is as follows: + + + +{ + "couchdb" : { + "request_time" : { + "stddev" : 7454.305, + "min" : 1, + "max" : 34185, + "current" : 34697.803, + "mean" : 1652.276, + "sum" : 34697.803, + "description" : "length of a request inside CouchDB without MochiWeb" + } + } +} + + +

+ +

+ + <literal>GET /_utils</literal> + + + + + +URL API GET /_utilsMethodGET /_utilsRequest + None + Response + Administration interface + Admin Privileges Requiredno + + + Accesses the built-in Futon administration interface for CouchDB. + + +

+ +

+ + <literal>GET /_uuids</literal> + + + + + +URL API GET /_uuidsMethodGET /_uuidsRequest + None + Response + List of UUIDs + Admin Privileges RequirednoQuery ArgumentsArgumentcountDescription + Number of UUIDs to return + OptionalyesTypenumericReturn Codes200 + Request completed successfully. + + + + Requests one or more Universally Unique Identifiers (UUIDs) from + the CouchDB instance. The response is a JSON object providing a + list of UUIDs. For example: + + + +{ + "uuids" : [ + "7e4b5a14b22ec1cf8e58b9cdd0000da3" + ] +} + + + + You can use the count argument to specify the + number of UUIDs to be returned. For example: + + + + GET http://couchdb:5984/_uuids?count=5 + + + + Returns: + + + +{ + "uuids" : [ + "c9df0cdf4442f993fc5570225b405a80", + "c9df0cdf4442f993fc5570225b405bd2", + "c9df0cdf4442f993fc5570225b405e42", + "c9df0cdf4442f993fc5570225b4061a0", + "c9df0cdf4442f993fc5570225b406a20" + ] +} + + + + The UUID type is determined by the UUID type setting in the + CouchDB configuration. See + . + + + + For example, changing the UUID type to random: + + + +PUT http://couchdb:5984/_config/uuids/algorithm +Content-Type: application/json +Accept: */* + +"random" + + + + When obtaining a list of UUIDs: + + + +{ + "uuids" : [ + "031aad7b469956cf2826fcb2a9260492", + "6ec875e15e6b385120938df18ee8e496", + "cff9e881516483911aa2f0e98949092d", + "b89d37509d39dd712546f9510d4a9271", + "2e0dbf7f6c4ad716f21938a016e4e59f" + ] +} + + +

+ +

+ + <literal>GET /favicon.ico</literal> + + + + + +URL API GET /favicon.icoMethodGET /favicon.icoRequest + None + Response + Binary content for the favicon.ico site icon + Admin Privileges RequirednoReturn Codes200 + Request completed successfully. + 404 + The requested content could not be found. The returned content + will include further information, as a JSON object, if available. + + + + Returns the site icon. The return Content-type + header is image/x-icon, and the content stream + is the image data. + + +

+ + http://git-wip-us.apache.org/repos/asf/couchdb/blob/fd643691/share/docs/couchdb-manual-1.1/metadoc-couchdb-config-options.xml ---------------------------------------------------------------------- diff --git a/share/docs/couchdb-manual-1.1/metadoc-couchdb-config-options.xml b/share/docs/couchdb-manual-1.1/metadoc-couchdb-config-options.xml new file mode 100644 index 0000000..177ab41 --- /dev/null +++ b/share/docs/couchdb-manual-1.1/metadoc-couchdb-config-options.xml @@ -0,0 +1,413 @@ + + +%every.entities; +]> +

+ + CouchDB Configuration Options + + + + + + + + + +Configuration GroupsSectionDescriptionattachments + Attachment options + couchdb + CouchDB specific options + daemons + Daemons and background processes + httpd_db_handlers + Database Operation handlers + couch_httpd_auth + HTTPD Authentication options + httpd + HTTPD Server options + httpd_design_handlers + Handlers for design document operations + httpd_global_handlers + Handlers for global operations + log + Logging options + query_servers + Query Server options + query_server_config + Query server options + replicator + Replicator Options + ssl + SSL (Secure Sockets Layer) Options + stats + Statistics options + uuids + UUID generation options +

+ +

+ + <literal>attachments</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescriptioncompressible_types + compressible_types + compression_level + compression_level +

+ +

+ + <literal>couchdb</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescriptiondatabase_dir + database_dir + delayed_commits + delayed_commits + max_attachment_chunk_size + max_attachment_chunk_size + max_dbs_open + max_dbs_open + max_document_size + max_document_size + os_process_timeout + os_process_timeout + uri_file + uri_file + util_driver_dir + util_driver_dir + view_index_dir + view_index_dir +

+ +

+ + <literal>daemons</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescriptionhttpsd + Enabled HTTPS service + auth_cache + auth_cache + db_update_notifier + db_update_notifier + external_manager + external_manager + httpd + httpd + query_servers + query_servers + stats_aggregator + stats_aggregator + stats_collector + stats_collector + uuids + uuids + view_manager + view_manager +

+ +

+ + <literal>httpd_db_handlers</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescription_changes + _changes + _compact + _compact + _design + _design + _temp_view + _temp_view + _view_cleanup + _view_cleanup +

+ +

+ + <literal>couch_httpd_auth</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescriptionauth_cache_size + auth_cache_size + authentication_db + authentication_db + authentication_redirect + authentication_redirect + require_valid_user + require_valid_user + timeout + timeout +

+ +

+ + <literal>httpd</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescriptionnodelay + Enable TCP_NODELAY + allow_jsonp + allow_jsonp + authentication_handlers + authentication_handlers + bind_address + bind_address + default_handler + default_handler + max_connections + max_connections + port + port + secure_rewrites + secure_rewrites + vhost_global_handlers + vhost_global_handlers +

+ +

+ + <literal>httpd_design_handlers</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescription_info + _info + _list + _list + _rewrite + _rewrite + _show + _show + _update + _update + _view + _view +

+ +

+ + <literal>httpd_global_handlers</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescription/ + / + _active_tasks + _active_tasks + _all_dbs + _all_dbs + _config + _config + _log + _log + _oauth + _oauth + _replicate + _replicate + _restart + _restart + _session + _session + _stats + _stats + _utils + _utils + _uuids + _uuids + favicon.ico + favicon.ico +

+ +

+ + <literal>log</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescriptionfile + file + include_sasl + include_sasl + level + level +

+ +

+ + <literal>query_servers</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescriptionjavascript + javascript +

+ +

+ + <literal>query_server_config</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescriptionreduce_limit + reduce_limit +

+ +

+ + <literal>replicator</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescriptionmax_http_pipeline_size + max_http_pipeline_size + max_http_sessions + max_http_sessions +

+ +

+ + <literal>stats</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescriptionrate + rate + samples + samples +

+ +

+ + <literal>uuids</literal> Configuration Options + + + + + + + + + +Configuration GroupsOptionDescriptionalgorithm + algorithm +

+ +