vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Request 

To perform actions on a requested cross-account connection, set the following parameters:



Table 5. Query parameters for requesting a cross-account connection

 Query parameters Details 

 version <br>Required <br>string Requests the version of the API as of a date in the format YYYY-MM-DD. Any date up to the current date may be provided. Specify the current date to request the latest version. <br>Possible values: Value must match regular expression ^[0-9]{4}-[0-9]{2}-[0-9]{2}$ 
 Request Body <br>Required <br>TransitGatewayConnectionActions The action template 
 action <br>Required <br>string The action that is to be performed against the connection request <br>Allowable values: [approve,reject] <br>Example:approve 





 Example request 

This example illustrates approving a cross-account connection:

"
{base_url}/transit_gateways/{transit_gateway_id}/connections/{id}/actions?version={version}"
{
"action": "approve"
}







 Response 

The following response results show once you initiate the request:



Table 6. Status codes

 Status code 

 204 The connection approval/rejection was successful. 
 403 The caller is not authorized to perform the requested action, or the action was called by the gateway owning account. 
 404 A transit gateway or transit gateway connection with the specified identifier could not be found. 
 409 Attempted to approve a classic_access VPC connection. 





 Example response 

This example illustrates a Status 403 response in which the caller is not authorized to perform the requested action:

{
"errors": [
{
"code": "missing_field",
"message": "The location field is required.",
"more_info": "https://transitservice.cloud.ibm.com/",
"target": {
"name": "location",
"type": "field"
}
}
],
In order to determine your current usage, you may wish to query a bucket to see bytes_used and object_count. Use of this command returns metadata containing that information for the specified bucket.

curl https://config.cloud-object-storage.cloud.ibm.com/v1/b/{my-bucket} 
-H 'authorization: bearer <IAM_token>'

The appropriate response to the request should contain bytes_used and object_count.

{
"name": "{my-bucket}",
"crn": "crn:v1:bluemix:public:cloud-object-storage:global:a/3bf0d9003abfb5d29761c3e97696b71c:d6f04d83-6c4f-4a62-a165-696756d63903:bucket:my-new-bucket",
"service_instance_id": "d6f04d83-6c4f-4a62-a165-696756d63903",
"service_instance_crn": "crn:v1:bluemix:public:cloud-object-storage:global:a/3bf0d9003abfb5d29761c3e97696b71c:d6f04d83-6c4f-4a62-a165-696756d63903::",
"time_created": "2018-03-26T16:23:36.980Z",
"time_updated": "2018-10-17T19:29:10.117Z",
"object_count": 764265234,
"bytes_used": 28198745752445144
}





 Get resource information from an API 

The resource controller is the next-generation IBM Cloud Platform provisioning layer that manages the lifecycle of Object Storage resources in a customer account.
Connecting to Presto server 

Presto CLI provides a terminal-based interactive shell to run queries.

In IBM® watsonx.data, you can connect to the Presto server in multiple ways based on the platform and utilities you are using. See the following sections for more details:



* [Connecting to Presto engine using Presto CLI (Remote)](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-con-presto-servconn-to-prestoeng)
* [Connecting to Presto engine using Java/JDBC](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-con-presto-servconn-to-prestjava)
* [Connecting to Presto engine using Python scripts](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-con-presto-servconn-to-prestpython)





 Pre-requisites 



 Getting the Presto engine hostname and port details 



1. Log in to the watsonx.data service instance in IBM Cloud.
2. Go to Infrastructure Manager and click List view.
3. In the Engines tab, click the engine name for which you need the hostname and port details.
4. Under the Host label, click the Copy to clipboard icon to copy the host details.
5. Copy the host details to a notepad.







 Getting the IBM API key or IBM IAM token 

Use either IBM API key or IBM IAM token according to your requirement.

It is recommended to use IAM token for stress workload.



 Getting IBM API Key 



1. Log in to the [IBM Cloud console](http://test.cloud.ibm.com/).
2. In the navigation bar, click Manage and select Access (IAM).
3. Click API keys in the left navigation bar.
4. Click Create +.
5.
New custom entity model in Entity Extraction : The [Entity Extraction](https://cloud.ibm.com/docs/discovery?topic=discovery-configserviceentity-extraction) enrichment Discovery tooling now includes the option to incorporate a custom entity model created with IBM Watson™ Knowledge Studio.

Change to Japanese-language collections : The option to create a Japanese collection was removed from the Discovery tooling, however, the option to create a Japanese collection using the Discovery API remains.

New support for syndicated environments : Discovery Tooling now supports syndicated environments.





 10 November 2017 

New retrieval options for Passages : Added additional options for Passage retrieval to the Discovery tooling. When querying, you can now specify the fields you would like the passages to be returned from, the number of passages to return, and the maximum character count for each passage. See [Passages](https://cloud.ibm.com/docs/discovery?topic=discovery-query-parameterspassages) for limits, minimums, and maximums.





 8 November 2017 

Update to version string : The version string for all API calls changed to 2017-11-07 from 2017-10-16. : This version moves the score in each query result to a new object named result_metadata. If the collection queried was trained, and the query is a natural language query, result_metadata includes a confidence field that displays the confidence score for that result. For details, see [Confidence scores](https://cloud.ibm.com/docs/discovery?topic=discovery-improving-result-relevance-with-the-toolingconfidence). Fields that include whitespaces (for example: body.additional reading) are filtered out during ingestion. The notices description reads The field 'additional reading' is invalid: whitespace, '.', '' and ',' are invalid in a field name. The field result_metadata is filtered out during ingestion.





 16 October 2017 

Update to version string : The version string for all API calls changed to 2017-10-16 from 2017-09-01.
Deprecated Knowledge Graph Beta APIs and Knowledge Graph relationship query : As announced [3 September 2019](https://cloud.ibm.com/docs/discovery?topic=discovery-release-notes3sept19), the IBM Watson™ Discovery Knowledge Graph Beta APIs (Knowledge graph entity query /v1/environments/{environment_id}/collections/{collection_id}/query_entities and Knowledge Graph relationship query /v1/environments/{environment_id}/collections/{collection_id}/query_relations) are no longer accessible.

Deprecated Preview API : As announced [4 June 2019](https://cloud.ibm.com/docs/discovery?topic=discovery-release-notes4jun19), the Preview API is deprecated and is no longer available.





 3 September 2019 

Change to Knowledge Graph Beta APIs and Knowledge Graph relationship query : IBM Watson™ Discovery Knowledge Graph Beta APIs (Knowledge graph entity query /v1/environments/{environment_id}/collections/{collection_id}/query_entities and Knowledge Graph relationship query /v1/environments/{environment_id}/collections/{collection_id}/query_relations) are no longer be accessible, as of 30 September 2019. Data already in Discovery collections is not affected, nor are any other existing queries or operations affected. You can find the documentation for Knowledge Graph in the [Discovery archives](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-archiveskg) until 30 September 2019.





 29 August 2019 

Updated Web crawl connector status : The Web crawl connector moved from beta status to GA status. See [Web crawl](https://cloud.ibm.com/docs/discovery?topic=discovery-sourcesconnectwebcrawl) for more information about this connector.





 4 June 2019 

Change to Preview API : The Preview API is deprecated and is no longer available, effective 30 September 2019.





 30 April 2019
Users must keep track of block numbers and query the blocks directly (or within a range of block numbers), and parse the information. However, LevelDB is also faster than CouchDB, though it does not support database indexing (which helps performance).

This support for rich queries is why CouchDB is the default database unless a user selects the State database selection box during the process of adding a peer selects LevelDB on the subsequent tab.

Because the data is modeled differently in a Couch database than in a Level database, the peers in a channel must all use the same database type. If data written for a Level database is rejected by a Couch database (which can happen, as CouchDB keys have certain formatting restrictions as compared to LevelDB keys), a state fork would be created between the two ledgers. Therefore, take extreme care when joining a channel to know the database type supported by the channel. It might be necessary to create a new peer that uses the appropriate database type and join it to the channel. Note that the database type cannot be changed after a peer has been deployed.





 Deployment zone selection 

If your Kubernetes cluster is configured across multiple zones, when you deploy a peer you have the option of selecting which zone the peer is deployed to. Check the Advanced deployment option that is labeled Deployment zone selection to see the list of zones that is currently configured for your Kubernetes cluster.

If you are deploying a redundant node (that is, another peer when you already have one), it is a best practice to deploy this node into a different zone. You can determine the zone that the other node was deployed to by opening the tile of the node and looking under the Node location. Alternatively, you can use the APIs to deploy a peer or orderer to a specific zone. For more information on how to do this with the APIs, see [Creating a node within a specific zone](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-apisibp-v2-apis-zone).

If multizone-capable storage is configured for your Kubernetes cluster, when a zone failure occurs, the nodes can come up in another zone with their associated storage intact, ensuring high availability of the node.
From the options menu, click View key details to view the details of the key.







 Viewing key details with the key management service API 

To view detailed information about a specific root key or a standard key, you can make a GET call to the following endpoint.

https://api.<region>.hs-crypto.cloud.ibm.com:<port>/api/v2/keys/<key_ID_or_alias>/metadata



1. [Retrieve your authentication credentials to work with keys in the service](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-set-up-kms-api).
2. Retrieve the ID of the key that you would like to inspect.

The ID value is used to access detailed information about the key. You can find the ID for a key in your service instance by [retrieving a list of your keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-view-keys), or by accessing the IBM Cloud console.
3. Get details about the key by running the following cURL command.

curl -X GET 'https://api.<region>.hs-crypto.cloud.ibm.com:<port>/api/v2/keys/<key_ID_or_alias>/metadata' -H 'accept: application/vnd.ibm.kms.key+json' -H 'authorization: Bearer <IAM_token>' -H 'bluemix-instance: <instance_ID>' -H 'x-kms-key-ring: <key_ring_ID>' -H 'correlation-id: <correlation_ID>'

Replace the variables in the example request according to the following table.



Table 1. Describes the variables needed to view details about a key with the API

 Variable Description 

 region Required. The region abbreviation, such as us-south or eu-de, that represents the geographic area where your Hyper Protect Crypto Services instance resides.
JDBC driver 



 Driver download 

Download the latest version: [2.7.18](https://us.sql-query.cloud.ibm.com/download/jdbc/ibmcloudsql-jdbc-2.7.18.jar)

Here you find the previous version for reference: [2.7.16](https://us.sql-query.cloud.ibm.com/download/jdbc/ibmcloudsql-jdbc-2.7.16.jar)





 JDBC driver class and URL format 

The Java™ class name for the JDBC driver is com.ibm.cloud.sql.jdbc.Driver.

The JDBC URL needs to include the CRN of an IBM Cloud® Data Engine instance, and must match the following schema:

jdbc:ibmcloudsql:{instance-crn}[?{key1}={value1}&{key2}={value2}...]

The CRN can be obtained from the service dashboard in the IBM Cloud® console. The following example shows a JDBC URL:

jdbc:ibmcloudsql:crn:v1:bluemix:public:sql-query:eu-de:a/290ec9931c0737248f3dc2aa57187d14%3AAf86d20c4-7646-441e-ad4b-182c57008471::?targetcosurl=cos://us-geo/sample-result-bucket/results/

You can also easily obtain the JDBC URL from the Data Engine UI from the Connect tab.

Connection properties (except for the CRN) can be specified as part of the URL, separated by &, or through the Java connection properties object. The following properties are supported:



* password (required): IBM Cloud API key for running the queries. The property name must start with a lowercase letter.
* user (optional): A username is not required and is ignored if given. It must start with a lowercase letter.
For example, if you want to query usage data for the IBM Cloud® Kubernetes Service service you would run the following:

curl "https://api.us-south.logging.cloud.ibm.com/v1/usage/hosts/containers-kubernetes" -u <SERVICE_KEY>:

And the output would be similar to the following:

[
{
"name": "containers-kubernetes",
"current_total": 205699,
"percentage_of_total": 8.608651799894956
}
]





 List usage data for a specific host over the past 10 days 

The following will list the aggregated usage information for the host <HOST_NAME> over the past 10 days.

curl "https://api.us-south.logging.cloud.ibm.com/v1/usage/hosts/<HOST_NAME>?from=$(($(date +%s)-864000))&to=$(date +%s)" -u <SERVICE_KEY>:





 List usage data for highest usage host for a 1 month period 

The following will list the usage information for the highest usage host over a specific month. The time period is specified by including a <START_DATE> and END_DATE.

curl "https://api.us-south.logging.cloud.ibm.com/v1/usage/hosts/?from=<START-DATE>&to=<END_DATE>&limit=<LIMIT_NUMBER>" -u <SERVICE_KEY>:

For example, to return the host with the highest data usage in October 2021, that is from October 1, 2021 through November 1 2021, you would run:

curl "https://api.us-south.logging.cloud.ibm.com/v1/usage/hosts?from=1633046400&to=1635724800&limit=1" -u <SERVICE_KEY>:
[Manage Data](https://cloud.ibm.com/docs-content/v1/content/ded4adc3ea0bd2a81b113c579f2b1183926da211/discovery//images/icon_yourData.png) icon, then choose the appropriate language from the drop-down.

For information about querying a collection via the API, see [API Reference](https://cloud.ibm.com/apidocs/discoveryquery-your-collection). The collection_id of the English language version of Watson Discovery News is news-en. Formerly, the collection_id was news. If you use the former collection_id, it continues to work; however, you might want to switch to the new collection_id for new projects. The collection_id of the Korean collection is news-ko, the Spanish collection_id is news-es, the German collection_id is news-de, the French collection_id is news-fr, and the Japanese collection_id is news-ja.

IBM Watson™ Discovery News queries display the first 50 words of each article in the text JSON field.

The maximum number of results returned for a Watson Discovery News query is 50. Use additional queries and the offset parameter to return more than 50 results.

If using the Discovery Query Language, you can include a relative date range in your Discovery News queries, for example: crawl_date>=now-1month. Valid date interval values are second/secondsminute/minutes, hour/hours, day/days, week/weeks, month/months, and year/years. now is not affected by the time_zone parameter; the UTC time zone is the default.

This example queries for a keyword within a specific date range. The time zone information is not required:



* enriched_text.keywords.text:"olympics", publication_date<=2018-02-15T00:00:00Z, publication_date>=2018-02-01T00:00:00Z



News articles might be syndicated to several news outlets, and IBM Watson™ Discovery News picks up each of them, resulting in duplicate articles.
For more information, see [Service keys by using the API](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_keysservice_keys_api).
* Replace <GROUP_ID> with the groupId returned from [listing configured groups](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-groups-manage-apigroup-list-api).
* Replace <NAME> with the name you want to give to the group.
* Replace <SCOPE> with a query specified as a JSON array. See [Defining service groups](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-group_data_accessgroups_data_access_groups) for example access scope search queries.



curl --request PATCH --url https://api.eu-gb.logging.cloud.ibm.com/v1/config/groups/xxxxxxxxxxxx -H "content-type: application/json" -H "servicekey: <SERVICE_KEY>" -d '{"name": "My log group2","accessScopes": ["reasonCode:200"] }'

The response will be similar to the following:

{"name":"My log group2","groupId":"xxxxxxxxxxxx","accessScopes":["reasonCode:200"]}
curl -X POST -u apikey:{apikey_value} -F "file=@wikipedia-sample.html" -F "configuration=$(cat config.json)" "https://gateway.watsonplatform.net/v1/environments/{environment_id}/collections/{collection_id}/documents?version=2016-12-01"


: The PDF and Word converters create HTML as a middle step. The service can apply additional transforms and normalizations on the intermediary HTML before the final transformation to normalized JSON.





 16 February 2017 

New features for JSON fields and environments : You can now use CSS selectors to select JSON fields that you can then apply enrichments to. See [Using CSS selectors to extract fields](https://cloud.ibm.com/docs/discovery?topic=discovery-configserviceusing-css) for information. : You can now increase the size of an environment by passing a new size: X parameter to the [update-environment method](https://cloud.ibm.com/apidocs/discoveryupdate-an-environment), where X is an integer between 0 and 3. See the [create-environment method](https://cloud.ibm.com/apidocs/discoverycreate-an-environment) for information about environment sizes and attributes. If you want to update your pricing plan, see [Discovery pricing plans](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-pricing-plans). : You cannot reduce the size of an existing environment. If you want to reduce the size of your environment, contact IBM® support for assistance.

New query operator : The ::! operator is added as a unary not-equals operator. For example, you can now run query=field::!value (not equals). Previously the only exclusionary operator was :! for the not-contains operator (for example, query=field:!value).

Fixed defects : Applied security updates. : Improved status messages for search alerts.





 1 February 2017
"frequency": 22050
}
"status": "ok"
}





 List an archive-type resource example 

The following example returns information about the archive-type resource named audio2:

IBM Cloud

curl -X GET -u "apikey:{apikey}" "{url}/v1/acoustic_customizations/{customization_id}/audio/audio2"

IBM Cloud Pak for Data

curl -X GET --header "Authorization: Bearer {token}" "{url}/v1/acoustic_customizations/{customization_id}/audio/audio2"

The resource is a .zip file that contains more than nine minutes of audio. It too was successfully added to the model. As the example shows, querying information about an archive-type resource also provides information about the files that it contains.

{
"container": {
"duration": 556,
"name": "audio2",
"details": {
"type": "archive",
"compression": "zip"
},
"status": "ok"
},
"audio": [
{
"duration": 121,
"name": "audio-file1.wav",
"details": {
"codec": "pcm_s16le",
"type": "audio",
"frequency": 16000
},
"status": "ok"
},
{
"duration": 133,
"name": "audio-file2.wav",
"details": {
"codec": "pcm_s16le",
"type": "audio",
"frequency": 16000
},
"status": "ok"
},
. . .
]
}
Show more







 Deleting an audio resource from a custom acoustic model
The specific IDs of affected VPCs.
2. The IDs of the DNS Services private resource records (if any).
3. The IDs of zones that have affected private resource records (if any).
4. The DNS queries made. If possible, give the details on DNS queries related to the issue, including DNS message ID and timestamp for each.
5. Information about the source of the DNS query (for example, the ID of the VPC from which the query originated).
6. If it affects a custom resolver, then include the custom resolver ID.
7. If it affects a GLB health check, then include the GLB health check ID and the IDs of affected GLBs.
8. If it is an issue with a forwarding rule, then include the forwarding rule ID.
9. If it is an issue with a secondary zone, then include the secondary zone rule ID.
Depending on the regions and compliance requirements of each geography, the Cloud Object Storage buckets remain in the same country, which is sometimes the same physical site.

When you decide to use the Veeam self-service portal to create backup jobs, identify which VM instances from any virtual data center in the organization participate in the backup job. Those backups are stored in the organizations SOBR.

You can manage (restore or delete) backups in the Veeam self-service portal. All backups are deleted if a virtual organization is deleted.





 Limitations for Veeam Backup and Replication 



* For the Veeam application aware image processing and guest file system indexing options to work for Windows® VMs, the most recent VMware® Tools must be installed on the VMs. Linux® VMs do not support application awareness or guest file system indexing.
* If you are using application aware image processing for MS SQL or Oracle DB backups, the options application aware and Item restore are not supported. The restore operation needs to complete a full VM restore, which requires a downtime window for any consumers of the database.







 Related links 



* [Ordering VMware as a Service instances](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-ordering)
* [Viewing VMware as a Service instances](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-viewing)
* [Adding and deleting Veeam Backup and Replication](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-veeam-adding-deleting)
* [Veeam website](https://www.veeam.com/)
* [Veeam Help Center](https://www.veeam.com/documentation-guides-datasheets.html)