vania-janet/multiturn-rag-retrieval-data huggingface dataset:
IBM Cloud® Databases for PostgreSQL Service Serves as the database for Delivery Pipeline job and step logs. 
 Object Storage Service Stores artifacts that are produced by Delivery Pipeline jobs and steps. Stores backups of Continuous Delivery data. 
 QRadar Service Collects security events such as successful or failed login authorization attempts for use by IBM specialists who maintain and support the service. 
 General Parallel File System (GPFS) Storage Provides secure, high-performance distributed file system storage of Git Repos and Issue Tracking repositories. GPFS runs on nodes within the same clusters that host the Git Repos and Issue Tracking components. 



For more information about the key components of the IBM Cloud Platform, see [What is the IBM Cloud Platform?](https://cloud.ibm.com/docs/overview?topic=overview-whatis-platform)

The following diagram shows the Continuous Delivery dependencies.

Zoom

![Continuous Delivery dependencies](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/CD_Dependencies_Arch.svg)

Figure 3. Continuous Delivery dependencies

Excluding data backups, customer-owned data that is provided to the Continuous Delivery service in a specific region is exchanged only with data and logging services in the same region. Data backups are stored in Cloud Object Storage cross-region buckets.



 Object storage location 

The following table shows the cross-region location for Object Storage in which backup data is stored for each Continuous Delivery service region.



Table 3. Object Storage location

 Continuous Delivery service location Object Storage backup service location 

 Dallas (us-south) US Cross Region (Dallas, Washington, San Jose) 
 Washington (us-east) US Cross Region (Dallas, Washington, San Jose) 
 London (eu-gb) EU Cross Region (Amsterdam, Frankfurt, Milan) 
 Frankfurt (eu-de) EU Cross Region (Amsterdam, Frankfurt, Milan) 
 Tokyo (jp-tok) AP Cross Region (Osaka, Sydney, Tokyo)
changes An array that lists the changes that were made to the specific document. Array 
 deleted Boolean indicating whether the corresponding document was deleted. If present, it always has the value true. Boolean 
 id Document identifier. String 
 last_seq Identifier of the last of the sequence identifiers. Currently, this identifier is the same as the sequence identifier of the last item in the results. String 
 results Array of changes that were made to the database. Array 
 seq Update sequence identifier. String 



See the following example (abbreviated) response to a _changes request:

{
"results": [
{
"seq": "1-g1A...sIg",
"id": "foo",
"changes":
{
"rev": "1-967...84d"
}
]
}
],
"last_seq": "1-g1A...sIg",
"pending": 0
}





 Important notes about _changes 



* The results that are returned by _changes are partially ordered. In other words, the order might not be preserved for multiple calls. You might decide to get a current list by using _changes and including the [last_seq value](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-get-changesget-changes). The resulting list provides the starting point for subsequent _changes lists that use the since query argument.
* Although shard copies of the same range contain the same data, their _changes history is often unique. This difference is a result of how writes were applied to the shard. For example, they might be applied in a different order. To be sure that all changes are reported for your specified sequence, it might be necessary to go further back into the shard's history to find a suitable starting point. The changes are then reported from that starting point. This "rolling back" might give the appearance of duplicate updates, or updates that are apparently before the specified since value.
What is the _all_docs endpoint? 

The GET and POST$SERVICE_URL/$DATABASE/_all_docs are used to fetch data from an IBM Cloudant database's primary index, that is, the index that keeps each document's _id in order. The _all_docs endpoint takes a number of optional parameters that configure the range of data that is requested and whether to return each document's body or not. With no parameters provided, _all_docs streams all of a database's documents, returning only the document _id and its current _rev token.



* Curl
* Java
* Node
* Python
* Go



curl -H "Authorization: Bearer $API_BEARER_TOKEN" -X GET "$SERVICE_URL/orders/_all_docs"

import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.AllDocsResult;
import com.ibm.cloud.cloudant.v1.model.PostAllDocsOptions;

Cloudant service = Cloudant.newInstance();

PostAllDocsOptions docsOptions =
new PostAllDocsOptions.Builder()
.db("orders")
.build();

AllDocsResult response =
service.postAllDocs(docsOptions).execute().getResult();

System.out.println(response);

const { CloudantV1 } = require('@ibm-cloud/cloudant');

const service = CloudantV1.newInstance({});

service.postAllDocs({
db: 'orders',
}).then(response => {
console.log(response.result);
});

from ibmcloudant.cloudant_v1 import CloudantV1

service = CloudantV1.new_instance()

response = service.post_all_docs(
db='orders',
).get_result()

print(response)
[11/7/19 5:08:22:613 UTC] 0000002f com.ibm.ws.logging.internal.impl.IncidentImpl I FFDC1015I: An FFDC Incident has been created: "org.jboss.weld.exceptions.DeploymentException: WELD-000049: Unable to invoke public void liquibase.integration.cdi.CDILiquibase.onStartup() on liquibase.integration.cdi.CDILiquibase@7f02a07 com.ibm.ws.container.service.state.internal.ApplicationStateManager 31" at ffdc_19.11.07_05.08.22.0.log
Show more

It is possible to manually unlock the plug-in. If you have Discovery 2.1.4 or earlier, enter the following command on the postgres database that the gateway-0 pod is looking at:

psql dadmin
UPDATE DATABASECHANGELOGLOCK SET LOCKED=FALSE, LOCKGRANTED=null, LOCKEDBY=null where ID=1;

If you have Discovery 2.2.0 or later, enter the following command on the postgres database that the gateway-0 pod is looking at:

oc exec -it wd-discovery-postgres-0 -- bash -c 'env PGPASSWORD="$PG_PASSWORD" psql "postgresql://$PG_USER@$STKEEPER_CLUSTER_NAME-proxy-service:$STKEEPER_PG_PORT/dadmin" -c "UPDATE DATABASECHANGELOGLOCK SET LOCKE
D=FALSE, LOCKGRANTED=null, LOCKEDBY=null where ID=1"'

If you can then restart the gateway pod, everything should resume normally.





 Environment variable settings for Smart Document Understanding 

There are two environment variables that need to be adjusted for Smart Document Understanding in IBM Watson® Discovery version 2.1.0. This was resolved in version 2.1.1, see [2.1.1 release, 24 Jan 2020](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-release-notes24jan2020).
For most IBM Cloud single-campus multizone regions, your data is backed up locally in [Single-campus multizone region Cloud Object Storage buckets](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints-zonee).

If a complete region failure occurs, the database servers in the region might not be accessible, but the backup data remains available. You can initiate a restore from these backups into an available region from the service management console. Consult your Cloud Databases backups page for more details.

It is your responsibility to [create a new service instance](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-provisioning) in which to restore when the IBM Cloud® Databases platform is restored. You are also responsible for testing the validity and restore time of your backups. For more information, see [Disaster recovery](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-responsibilities-cloud-databasesdisaster-recovery-responsibilities) in the Responsibilities for Cloud Databases page.



 Application-level high availability 

Applications that communicate over networks and cloud services are subject to transient connection failures. You want to design your applications to retry connections when errors are caused by a temporary loss in connectivity to your deployment or to IBM Cloud.

Because Cloud Databases is a managed service, regular updates and database maintenance occur as part of normal operations. Such maintenance can occasionally cause short intervals where your database is disabled.

Your applications must be designed to handle temporary interruptions to the database, implement error handling for failed database commands, and implement retry logic to recover from a temporary interruption.

Several minutes of database unavailability or connection interruptions are not expected. Open a [support ticket](https://cloud.ibm.com/unifiedsupport/cases/add) with details if you have time periods longer than a minute with no connectivity so we can investigate.

If you have deployments in more than one region, you must provision IBM Cloud® Monitoring and enable platform metrics in each region. For more information, see IBM Cloud Monitoringyour Cloud Databases deployment's IBM Cloud Monitoring page





 SLAs
Numerous documents provide in-depth help on planning and installing an HA environment for SAP services. The documents include information on failover, replication, scale-out, and disaster recovery (DR). References to specific documents are provided where appropriate.

All the operating systems and distributions that are supported by IBM Cloud for an SAP deployment (Windows Server, RHEL, and SLES) come with high-availability software and specific extensions. The supported OS and distributions are described in these documents:



* [New Failover Clustering Improvements in Windows Server 2012 and Its Benefits for SAP NetWeaver High Availability](https://blogs.sap.com/2013/10/16/new-failover-clustering-improvements-in-windows-server-2012-and-its-benefits-for-sap-netweaver-high-availability/) provides a description based on Microsoft Windows Server Failover Clustering (WFSC) on the Windows OS with SAP NetWeaver.
* Two references for guidance on deploying SAP NetWeaver in a Linux-based HA environment with Linux® Pacemaker are:



* SUSE SAP NetWeaver High Availability Cluster 7.40 Setup Guide
* Deploying Highly Available SAP NetWeaver-based Servers Using Red Hat Enterprise Linux HA add-on with Pacemaker



* [Building High Availability for SAP NetWeaver and SAP HANA on Linux](https://support.sap.com/content/dam/SAAP/SAP_Activate/AGS_70.pdf) is an SAP best-practice document and provides an in-depth technical description with a strong focus on SAP HANA.
* [SAP NetWeaver High Availability and Business Continuity in Virtual Environments with VMware and Hyper-V on Microsoft Windows](https://archive.sap.com/documents/docs/DOC-44415) covers the virtualization aspects if you’re planning to implement HA on virtualized servers.



For more high-availability products certified by SAP partners for high-availability scenarios, see [High Availability Partner Information](https://wiki.scn.sap.com/wiki/display/SI/High+Availability+Partner+Information).

For non-HANA SAP databases, more information on HA fail-over and DR configurations, is available in your database documentation.
: The IBM Cloud Object Storage endpoint to be associated with the IBM Cloud Object Storage bucket.

--bucket COS_BUCKET
: The name of the IBM Cloud Object Storage bucket to be associated with the target.

--target-crn COS_TARGET_CRN
: The CRN of the IBM Cloud Object Storage instance.

--api-key COS_API_KEY | @COS_API_KEY_FILE
: Your [API key](https://cloud.ibm.com/docs/account?topic=account-manapikey) value or a reference to the API Key file used to gain access. For example, ibmcloud login --apikey $KEYFILE

--service-to-service-enabled (TRUE | FALSE)
: Indicates if [service-to-service authorization](https://cloud.ibm.com/docs/atracker-cli-plugin?topic=atracker-cli-plugin-atracker-v2-clicos_s2s) has been enabled for the bucket. Specify TRUE if service-to-service authorization is enabled and FALSE if service-to-service authorization is not enable. By default, service-to-service authorization is FALSE.

--output FORMAT
: Currently supported format is JSON. If specified, output will be returned in JSON format. If JSON is not specified, output will be returned in a tabular format.

help | --help | -h
: List options available for the command.







 ibmcloud atracker target update (IBM Cloud Activity Tracker hosted event search) 

Use this command to update an IBM Cloud Activity Tracker hosted event search offering target to be used to configure a destination for activity events.

ibmcloud atracker target update --target TARGET [--name TARGET_NAME] ( --file @LOGDNA_ENDPOINT_DEFINITION_JSON_FILE ) | (--target-crn LOGDNA_TARGET_CRN --ingestion-key LOGDNA_INGESTION_KEY ) [--region REGION] [--output FORMAT]



 Command options 

--target TARGET
For more information about creating complex selector expressions, see [Creating selector expressions](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-selector-syntaxcreating-selector-expressions).





 Selector with two fields 

In the following example, the selector matches any document with a name field that contains Paul, and that also has a location field with the value "Boston".

See the following example of a more complex selector:

{
"selector": {
"name": "Paul",
"location": "Boston"
}
}





 Subfields 

Use a more complex selector to specify the values for a field of nested objects, or subfields. For example, you might use a standard JSON structure for specifying a field and a subfield.

See the following example of a field and subfield selector within a JSON object:

{
"selector": {
"imdb": {
"rating": 8
}
}
}

An abbreviated equivalent uses a dot notation to combine the field and subfield names into a single name.

See the following example of an equivalent field and subfield selector that uses dot notation:

{
"selector": {
"imdb.rating": 8
}
}
Although the configuration properties cos.object.deadline.seconds, cos.interval.seconds, and cos.object.records are listed as optional, you must set at least one of these properties to a nondefault value.



 cos-sink.json file properties 

Replace the placeholders in the cos-sink.json file with your own values.



Table 1. cos-sink.json file properties

 File properties Description 

 cos.api.key Required. API key used to connect to the Cloud Object Storage service instance. 
 cos.bucket.location Required. Location of the Cloud Object Storage service bucket. For example, for a [regional bucket](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints-region)eu-gb, or for a [global bucket](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints-geo)eu. 
 cos.bucket.name Required. Name of the Cloud Object Storage service bucket to write data into. 
 cos.bucket.resiliency Required. Resiliency of the Cloud Object Storage bucket. Must be one of: cross-region, regional, or single-site. 
 cos.service.crn Required. CRN for the Cloud Object Storage service instance. Ensure you enter the correct CRN: it is the resource instance ID ending with double colons, for example, crn:v1:staging:public:cloud-object-storage:global:a/8c226dc8c8bfb9bc3431515a16957954:b25fe12c-9cf5-4ee8-8285-2c7e6ae707f6::. 
 cos.endpoint.visibility Optional. Specify public to connect to the Cloud Object Storage service over the public internet. Specify private to connect from a connector that runs inside the IBM Cloud network, for example, from an IBM Cloud Kubernetes Service cluster. The default is public. 
 cos.object.deadline.seconds Optional.
--wait-timeout, --wto
: The length of time in seconds to wait for the IBM Cloud Object Storage event subscription to be deleted. This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 15.





 Example 

ibmcloud ce subscription cos delete --name mycosevent -f





 Example output 

Deleting COS source 'mycosevent'...
OK







 ibmcloud ce subscription cos get 

Display the details of an IBM Cloud Object Storage event subscription. Displayed attributes include Name, Destination, Bucket, Event Type, Prefix, Suffix, Ready, and Age. To see specific details, attach | grep <attribute>.

ibmcloud ce subscription cos get --name COS_SOURCE_NAME [--output OUTPUT] [--quiet]



 Command Options 

--name, -n
: The name of the IBM Cloud Object Storage event subscription. This value is required.

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

ibmcloud ce subscription cos get --name mycosevent





 Example output 

Getting COS source 'mycosevent'...
OK

Name: mycosevent
ID: abcdefgh-abcd-abcd-abcd-fb6be2347a14
Project Name: myproject
Project ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Age: 12s
Created: 2021-03-14T13:28:45-05:00

Destination: App:myapp
: The name of the IBM Cloud Object Storage bucket to be associated with the target.

--target-crn COS_TARGET_CRN
: The CRN of the IBM Cloud Object Storage instance.

--api-key COS_API_KEY | @COS_API_KEY_FILE
: Your [API key](https://cloud.ibm.com/docs/account?topic=account-manapikey) value or a reference to the API Key file used to gain access. For example, ibmcloud login --apikey $KEYFILE

--service-to-service-enabled
: Indicates if [service-to-service authorization](https://cloud.ibm.com/docs/atracker-cli-plugin?topic=atracker-cli-plugin-atracker-v2-clicos_s2s) has been enabled for the bucket. Specify TRUE if service-to-service authorization is enabled and FALSE if service-to-service authorization is not enable. By default, service_to_service_enabled is FALSE.

--output FORMAT
: Currently supported format is JSON. If specified, output will be returned in JSON format. If JSON is not specified, output will be returned in a tabular format.

help | --help | -h
: List options available for the command.







 ibmcloud atracker target create (IBM Cloud Activity Tracker hosted event search) 

Use this command to create an IBM Cloud Activity Tracker hosted event search offering target to be used to configure a destination for activity events.

ibmcloud atracker target create --name TARGET_NAME --type TARGET_TYPE ( [--file LOGDNA_ENDPOINT_DEFINITION_JSON_FILE] | ( [--target-crn LOGDNA_TARGET_CRN] [--ingestion-key LOGDNA_INGESTION_KEY] ) ) [--region REGION] [--output FORMAT]



 Command options 

--region REGION | -r REGION
: Name of the region, for example, us-south or eu-gb.
The response is a JSON document that contains the ID of the created document, the revision string, and "ok": true.

If you didn't provide an _id field, IBM Cloudant generates one automatically as a [UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier).

A failure to create the document results in a response that contains a description of the error.

See an example response after successfully creating a document:

{
"id": "exampleid",
"ok": true,
"rev": "2-056f5f44046ecafc08a2bc2b9c229e20"
}

If the write [quorum](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-create-documentquorum-writing-and-reading-data) can't be met during an attempt to create a document, a [202 response](https://cloud.ibm.com/apidocs/cloudantlist-of-http-codes) is returned.
If not specified, the region logged into, or targeted, will be used.--name TARGET_NAME: The name to be given to the target.
Do not include any personal identifying information (PII) in any resource names.
--type TARGET_TYPE: Set the TARGET_TYPE to cloud_object_storage for a COS target.--file @COS_ENDPOINT_DEFINITION_JSON_FILE: A file containing an endpoint definition in the following format:
{
"endpoint": "aaaaa",
"target_crn": "yyyyy",
"bucket": "zzzzzz",
"api_key": "xxxxxx"
}
--endpoint COS_ENDPOINT: The IBM Cloud Object Storage endpoint to be associated with the IBM Cloud Object Storage bucket.--bucket BUCKET: The name of the IBM Cloud Object Storage bucket to be associated with the target.--target-crn COS_TARGET_CRN: The CRN of the IBM Cloud Object Storage instance.--api-key COS_API_KEY | @COS_API_KEY_FILE: Your API key]API key 1] value or a reference to the API Key file used to gain access. For example, ibmcloud login --apikey $KEYFILE--service-to-service-enabled: Indicates if service-to-service authorization]service_-to_-service authorization] ! ! ! ! ! has been enabled for the bucket. Specify TRUE if service-to-service authorization is enabled and FALSE if service-to-service authorization is not enable. By default, service_to_service_enabled is FALSE.--output FORMAT: Currently supported format is JSON. If specified, output will be returned in JSON format.
The prefix parameter is the prefix of the IBM Cloud Object Storage objects. You can specify this flag when creating your trigger to filter trigger events by object name prefix. 
 suffix (Optional). The suffix parameter is the suffix of your IBM Cloud Object Storage objects. You can specify this flag when creating your trigger to filter trigger events by object name suffix. 
 event_types (Optional). The event_types is the type of bucket change that fires the trigger. You can specify write or delete or all. The default value is all. 







 Data structure of an IBM Cloud Object Storage trigger activation 

The content of the generated events has the following parameters:



Table 4. Generated events parameters

 Parameter Description 

 bucket The name of the IBM Cloud Object Storage bucket that was updated. 
 object_name The name of the object that was changed. 
 event_type The type of event that occurred. 
 endpoint The IBM Cloud Object Storage endpoint used to connect to the IBM Cloud Object Storage bucket. This is the endpoint value specified during trigger creation. 
 key The name of the changed object. 



The following sample is an example JSON response of a trigger activation. You can get details of an activation by running ibmcloud fn activation get <activation_id>.

{
"namespace": "<namespace_ID>",
"name": "cosTrigger",
"version": "0.0.1",
"subject": "ServiceId-65348247-951f-4f22-b2ef-7782597c3ab1",
"activationId": "78fg525e45964bcdae525e45966bcd6f",
"start": 1567608038827,
"end": 0,
"duration": 0,
"statusCode": 0,
"response": {
"status": "success",
"statusCode": 0,
"success": true,
"result": {
"bucket": "bucket_name",
For detailed information, see [Performing segmentation](https://cloud.ibm.com/docs/discovery?topic=discovery-configserviceperforming-segmentation).





 JSON 

You can perform pre-enrichment normalization of the ingested JSON by defining operation objects in the json_normalizations array.

"json_normalizations": [
{
"operation": "remove",
"source_field": "header"
},
{
"operation": "copy",
"source_field": "title",
"destination_field": "title_old"
},
{
"operation": "move",
"destination_field": "content",
"source_field": "body"
},
{
"operation": "merge",
"source_field": "synopsis",
"destination_field": "preamble"
},
{
"operation": "remove_nulls"
}
]
Show more



 Operations objects 



* "operation": string - required - the operation that is performed on the JSON, must be one of the following:



* remove - the specified source_field is removed from the JSON.
* copy - the specified source_field content is copied to a new instance of the destination_field.
* move - the specified source_field is renamed to the destination_field. If the destination_field already exists a new instance of the destination_field is created.
* merge - the contents of the source_field and the destination_field are merged into the destination_field.
* remove_nulls - fields with null content are removed.



* "source_field": string - optional - the field that the operation is performed on.
* "destination_field": string - optional - the destination field the the operation is output to.