# Query: travel-sample # Flags: WordMatch RegExp # Including: ./docs-server # Excluding: *.html,*.json Manage pages: check if these pages need to be updated Check whether backup and restore can work on the scope and collection level. modules/manage/pages/manage-backup-and-restore/manage-backup-and-restore.adoc: 206: For the current example, the sample bucket `travel-sample` is assumed to have been installed (see xref:manage:manage-settings/install-sample-buckets.adoc[Sample Buckets]); and will be specified in this field. 228: The newly created repository, *hourlyBackupRepo*, is thus displayed with its associated plan, `hourlyBackupRepo`, with the affected bucket (`travel-sample`) and the next scheduled backup displayed. 229: Data Service and Index Service data for `travel-sample` will now be backed up to the specified location on the specified schedule. 298: Each bucket that has been backed up (in this case, the `travel-sample` bucket alone), appears on its assigned row in a table that specifies the number of items, mutations, and tombstones that have been included in the backup. 304: Then, enter the bucket name into the *Search Path* field: note that this requires explicit specification of both _scope_ and _collection_; unless default scope and collection have been used, in which case, explicit specification of the defaults is optional — for example, `travel-sample._default._default`. 544: For example, if data to be restored from `travel-sample` should be restored to `ts`, enter `travel-sample=ts`. 568: The data to be restored from `travel-sample` is specified to be restored to a bucket named `ts`, which has not previously been created: therefore, the *Auto-create Buckets* checkbox has been checked. 579: Its item-count indicates that it contains only a subset of the documents contained in `travel-sample`, in accordance with the filtering specified for the restore operation. modules/manage/pages/manage-indexes/manage-indexes.adoc: 161: For example, type the following query into the *Query Editor*: `SELECT icao FROM `travel-sample` WHERE name = "SeaPort Airlines";`. 162: This selects every `icao` key-value pair from the bucket `travel-sample`, where the host document also contains a `name` value that is `SeaPort Airlines`. modules/manage/pages/manage-security/manage-users-and-roles.adoc: 336: "bucket_name": "travel-sample", 345: "bucket_name": "travel-sample", modules/manage/pages/manage-statistics/manage-statistics.adoc: 39: The following examples assume that the `travel-sample` bucket has been installed. 84: The current option, *travel-sample*, is the only option available, since it is the only bucket currently loaded. 286: /opt/couchbase/bin/cbstats -b travel-sample -u Administrator -p password \ 325: /opt/couchbase/bin/cbstats -b travel-sample -u Administrator -p password \ 400: http://localhost:8091/pools/default/buckets/travel-sample/stats | jq modules/manage/pages/manage-ui/manage-ui.adoc: 107: After this procedure is followed for the `travel-sample` bucket, the *Dashboard* screen appears as follows: 274: After the `travel-sample` bucket has been added, by means of the procedure described in xref:manage:manage-settings/install-sample-buckets.adoc[Install Sample Buckets], the *Buckets* screen appears as follows: 474: If the `travel-sample` is installed, the screen appears as follows: 508: If the `travel-sample` bucket is installed, the *Query* screen appears as follows: 539: After this procedure is followed for the `travel-sample` bucket, the *Indexes* screen appears as follows: modules/manage/pages/manage-xdcr/filter-xdcr-replication.adoc: 32: * Cluster `10.143.192.101` contains a single bucket, which is the `travel-sample` bucket. 190: --xdcr-from-bucket travel-sample --xdcr-to-bucket US_airport \ 194: This expression specifies that all documents filtered by means of the specified `filter-expression` will be replicated from `travel-sample`, on the localhost `10.143.192.101`, to `US_airport` on the remote cluster `10.143.192.102`. 215: -d fromBucket=travel-sample \ 219: This expression specifies that all documents filtered by means of the specified `filter-expression` will be replicated from `travel-sample`, on the localhost `10.143.192.101`, to `US_airport` on the remote cluster `10.143.192.102`. modules/manage/pages/monitor/monitoring-n1ql-query.adoc: 289: "keyspace": "travel-sample", 325: cbq> SELECT * FROM `travel-sample` WHERE type = "airline" LIMIT 1; 337: "travel-sample": { 389: cbq> SELECT * FROM `travel-sample` WHERE type = "airline" LIMIT 1; 401: "travel-sample": { 457: "Target": "default:travel-sample", 461: "Target": "default:travel-sample", 502: "keyspace": "travel-sample", 531: "keyspace": "travel-sample", 568: "keyspace": "travel-sample", 596: "keyspace": "travel-sample", 630: "keyspace": "travel-sample", 650: "condition": "((`travel-sample`.`type`) = \"airline\")" 1124: "Target": "default:travel-sample" 1137: "keyspace": "travel-sample", 1143: "keyspace": "travel-sample", 1153: "condition": "((`travel-sample`.`foo`) = 42)" 1181: "text": "PREPARE p1 AS SELECT * FROM `travel-sample` WHERE foo = 42;" 1218: "Target": "default:travel-sample" 1231: "keyspace": "travel-sample", 1237: "keyspace": "travel-sample", 1247: "condition": "((`travel-sample`.`foo`) = 42)" 1278: "statement": "PREPARE p1 AS SELECT * FROM `travel-sample` WHERE foo = 42;", 1487: cbq> SELECT * FROM `travel-sample` ORDER BY name; 1496: cbq> SELECT * FROM `travel-sample` ORDER BY title; 1551: "statement": "SELECT * FROM `travel-sample` ORDER BY title;", 1590: "statement": "SELECT * FROM `travel-sample` ORDER BY name;", 1612: "Target": "default:travel-sample" 1643: "keyspace": "travel-sample", 1657: "keyspace": "travel-sample", 1689: "expr": "(`travel-sample`.`name`)" 1939: "bucket_name": "travel-sample",