vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Immutable Object Storage is available in certain regions only, see [Integrated Services](https://cloud.ibm.com/docs/services/cloud-object-storage/basics?topic=cloud-object-storage-service-availabilityservice-availability) for details. It also requires a Standard pricing plan. See [pricing](https://www.ibm.com/cloud/object-storage) for details.

It isn't possible to use Aspera high-speed transfer with buckets with a retention policy.



 Terminology and usage 



 Retention period 

The duration of time an object must be stored in the IBM Cloud Object Storage bucket.





 Retention policy 

A retention policy is enabled at the IBM Cloud Object Storage bucket level. Minimum, maximum and default retention period are defined by this policy and apply to all objects in the bucket.

Minimum retention period is the minimum duration of time an object must be kept unmodified in the bucket.

Maximum retention period is the maximum duration of time an object can be kept unmodified in the bucket.

If an object is stored in the bucket without specifying a custom retention period, the default retention period is used. The minimum retention period must be less than or equal to the default retention period, which in turn must be less than or equal to the maximum retention period.

A maximum retention period of 1000 years can be specified for the objects.

To create a retention policy on a bucket, you need Manager role. See [Bucket permissions](https://cloud.ibm.com/docs/services/cloud-object-storage/iam?topic=cloud-object-storage-iam-bucket-permissions) for more details.





 Legal hold 

Certain objects might need to be prevented from modification after a retention period expires. An example is an incomplete legal review, where records might need to be accessible for an extended duration beyond the retention period originally set. A legal hold flag can then be applied at the object level. Legal holds can be applied to objects during initial uploads or after an object is written. Note: A maximum of 100 legal holds can be applied per object.





 Indefinite retention
For the first phrase, Yon See, the service sends a positive match with a confidence score, similar to the previous examples. For the second phrase, Young Says He, the service can have one of two possible responses:



* It might send no response, indicating that the phrase does not match one of the grammar's rules.
* It might instead send a response with a low confidence score, indicating that the phrase is acoustically similar to one of the rules but is not a likely match.



Other factors and parameters can also effect grammar recognition:



* If the service encounters a pause that separates the phrases that are to be matched, the grammar fails to recognize the multi-phrase rule. You can use the end_of_phrase_silence_time parameter to increase the pause interval and avoid receiving multiple final results. For more information, see [End of phrase silence time](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-parsingsilence-time).
* If the split_transcript_at_phrase_end parameter is set to true, the service can split a transcript into multiple final results based on semantic features of the input. Such splits are unlikely to impact grammar recognition. But the use of a custom language model and a grammar can influence how the service interprets semantic features. For more information, see [Split transcript at phrase end](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-parsingsplit-transcript).







 Confidence scores and empty results 

For relatively simple grammars like those in the previous examples, the service can return a result with a low confidence score even when the response does not appear to match the grammar at all. This might seem surprising, but a response with a low confidence score can indicate the best match that the service could find for the given audio, even though the response is unlikely to match the grammar. If the response does not match the grammar, the confidence value of the results is typically low enough to indicate the unlikelihood that the grammar can generate the response.

Always consider the confidence score when evaluating whether a response satisfies a grammar.
To protect your privacy, do not use personal data, such as your name or location, as a description for your secret group.

The maximum length is 1024 characters. The minimum length is 0 characters. The value must match regular expression /(.?)/.

--labels ([]string)
: Labels that you can use to search secrets in your instance. Only 30 labels can be created.

Label can be between 2-30 characters, including spaces.

To protect your privacy, do not use personal data, such as your name or location, as a label for your secret.

The list items must match regular expression /(.?)/. The maximum length is 30 items. The minimum length is 0 items.

--custom-metadata (generic map)
: The secret metadata that a user can customize.

--expiration-date (strfmt.DateTime)
: The date when the secret material expires. The date format follows the RFC 3339 format.

--ttl (string)
: The time-to-live (TTL) or lease duration to assign to credentials that are generated.

For iam_credentials secrets, the TTL defines for how long each generated API key remains valid. The value can be either an integer that specifies the number of seconds, or the string representation of a duration, such as 120m or 24h.

The minimum duration is 1 minute. The maximum is 90 days.

The maximum length is 10 characters. The minimum length is 2 characters. The value must match regular expression /^[0-9]+[s,m,h,d]{0,1}$/.

--rotation ([RotationPolicy](https://cloud.ibm.com/docs/cli?topic=cli-secrets-manager-clicli-rotation-policy-example-schema))
: This field indicates whether Secrets Manager rotates your secrets automatically.





 Example
<prosody pitch="+12st">Increase pitch by 12 semitones from baseline</prosody>
<prosody pitch="x-low">Lower pitch by 12 semitones from baseline</prosody>





 The rate attribute 

The rate attribute indicates a change in the speaking rate for the text within the element. Accepted values are



* A number with no unit designation: The rate is changed to the specified number of words per minute. For example, a value of 50 indicates a speaking rate of 50 words per minute. The number is absolute; you cannot specify a relative increase or decrease in words per minute.
* A relative change in percent: A number that causes a relative shift from the default speaking rate. The number is preceded by + (an increase) or - (a decrease) and followed by a % (percent sign). An unsigned number that is followed by a % is interpreted as a positive increase. For example, +10% or 10%. The default speaking rate for a voice is equivalent to passing a value of 0%.
* A keyword: One of the following six keywords, which modify the speaking rate to the corresponding predefined values:



* default uses the service's default speaking rate.
* x-slow decreases the rate by 50 percent.
* slow decreases the rate by 25 percent.
* medium produces the same behavior as default.
* fast increases the rate by 25 percent.
* x-fast increases the rate by 50 percent.





Expressive neural voices support only percentage values for the rate attribute. They do not support words per minute or keywords.

The best way to determine what works for your application is to make adjustments based on percentages and experiment with different values. Try incremental changes of five or ten percent before making more significant modifications.

<prosody rate="50">Set speaking rate to 50 words per minute</prosody>
<prosody rate="-5%">Decrease speaking rate by 5 percent</prosody>
<prosody rate="+5%">Increase speaking rate by 5 percent</prosody>
For more information, see [End of phrase silence time](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-parsingsilence-time).



 Split transcript at phrase end results 

When the split transcript at phrase end feature is enabled, each final result in the transcript includes an additional end_of_utterance field that identifies why the service split the transcript at that point:



* full_stop - A full semantic stop, such as for the conclusion of a grammatical sentence. The insertion of splits is influenced by the base language model and biased by custom language models and grammars, as described previously.
* silence - A pause or silence that is at least as long as the pause interval. You can use the end_of_phrase_silence_time parameter to control the length of the pause interval.
* end_of_data - The end of the input audio stream.
* reset - The amount of audio that is currently being processed exceeds the two-minute maximum. The service splits the transcript to avoid excessive memory use.







 Split transcript at phrase end example 

The following example requests demonstrate the use of the split_transcript_at_phrase_end parameter. The audio speaks the phrase "I have an identification card. The number is one two three four five six." The speaker pauses for one second between the words "three" and "four."

The first example shows the results for a request that omits the parameter:

IBM Cloud

curl -X POST -u "apikey:{apikey}" --header "Content-Type: audio/wav" --data-binary @{path}audio-file.wav "{url}/v1/recognize"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" --header "Content-Type: audio/wav" --data-binary @{path}audio-file.wav "{url}/v1/recognize"

The service returns two final results, splitting the transcript only at the speaker's extended pause:

{
"result_index": 0,
"results": [
{
"alternatives":
The new retention period can be provided as part of the object overwrite request or the default retention time of the bucket will be given to the object.

The minimum and maximum supported values for the retention period settings MinimumRetention, DefaultRetention, and MaximumRetention are a minimum of 0 days and a maximum of 365243 days (1000 years).

def add_protection_configuration_to_bucket(bucket_name):
try:
new_protection_config = {
"Status": "Retention",
"MinimumRetention": {"Days": 10},
"DefaultRetention": {"Days": 100},
"MaximumRetention": {"Days": 1000}
}

cos.put_bucket_protection_configuration(Bucket=bucket_name, ProtectionConfiguration=new_protection_config)

print("Protection added to bucket {0}n".format(bucket_name))
except ClientError as be:
print("CLIENT ERROR: {0}n".format(be))
except Exception as e:
print("Unable to set bucket protection config: {0}".format(e))
Show more





 Check protection on a bucket 

def get_protection_configuration_on_bucket(bucket_name):
try:
response = cos.get_bucket_protection_configuration(Bucket=bucket_name)
protection_config = response.get("ProtectionConfiguration")

print("Bucket protection config for {0}n".format(bucket_name))
print(protection_config)
print("n")
except ClientError as be:
print("CLIENT ERROR: {0}n".format(be))
except Exception as e:
print("Unable to get bucket protection config: {0}".format(e))





 Upload a protected object 

Objects in protected buckets that are no longer under retention (retention period has expired and the object does not have any legal holds), when overwritten, will again come under retention.
print("New retention period on {0} is {1}n".format(object_name, additional_seconds))

function extendRetentionPeriodOnObject(bucketName, objectName, additionalSeconds) {
console.log(Extend the retention period on ${objectName} in bucket ${bucketName} by ${additionalSeconds} seconds.);
return cos.extendObjectRetention({
Bucket: bucketName,
Key: objectName,
AdditionalRetentionPeriod: additionalSeconds
}).promise()
.then((data) => {
console.log(New retention period on ${objectName} is ${data.RetentionPeriod});
})
.catch((e) => {
console.log(ERROR: ${e.code} - ${e.message}n);
});
}





 List legal holds on an object 

This implementation of the GET operation uses the legalHold query parameter to return the list of legal holds on an object and related retention state in an XML response body.

This operation returns:



* Object creation date
* Object retention period in seconds
* Calculated retention expiration date based on the period and creation date
* List of legal holds
* Legal hold identifier
* Timestamp when legal hold was applied



If there are no legal holds on the object, an empty LegalHoldSet is returned. If there is no retention period that is specified on the object, a 404 error is returned.

Syntax

GET https://{endpoint}/{bucket-name}/{object-name}?legalHold= path style
GET https://{bucket-name}.{endpoint}/{object-name}?legalHold= virtual host style

Example request

GET /BucketName/ObjectName?legalHold HTTP/1.1
Host: myBucket.mydsNet.corp.com
Date: Fri, 8 Dec 2018 17:50:00 GMT
Authorization: {authorization-string}
Content-Type: text/plain

Example response
* [Supported previous-generation language models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-modelsmodels-supported)
* [Speaker labels](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-speaker-labels)



Updates to multiple models for improved speech recognition
: The following models have been updated for improved speech recognition:



* French broadband model (fr-FR_BroadbandModel)
* German broadband (de-DE_BroadbandModel) and narrowband (de-DE_NarrowbandModel) models
* UK English broadband (en-GB_BroadbandModel) and narrowband (en-GB_NarrowbandModel) models
* US English short-form narrowband (en-US_ShortForm_NarrowbandModel) model



By default, the service automatically uses the updated models for all speech recognition requests. If you have custom language or custom acoustic models that are based on these models, you must upgrade your existing custom models to take advantage of the updates by using the following methods:



* POST /v1/customizations/{customization_id}/upgrade_model
* POST /v1/acoustic_customizations/{customization_id}/upgrade_model



For more information, see [Upgrading custom models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-custom-upgrade).

Hesitation marker for German changed
: The hesitation marker that is used for the updated German broadband and narrowband models has changed from [hesitation] to %HESITATION. For more information, see [Speech hesitations and hesitation markers](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-basic-responseresponse-hesitation).





 4 June 2020 

Defect fix: Improve latency for custom language models with many grammars
: Defect fix: The latency issue for custom language models that contain a large number of grammars has been resolved. When initially used for speech recognition, such custom models could take multiple seconds to load.
Type a new name for the database.
If the name contains special characters, enclose it in double quotation marks. The dot character (".") is not supported.
5. Click Rename.







 Updating retention time interval (time travel) for databases 



1. Go to Databases.
2. Select the database for which you want to update the retention time interval.
3. From the overflow menu, click Update interval.
4. Type a retention time interval.
You can select between 1 day and up to 99 days, or zero to alter a temporal database to nontemporal. For more information on retention time interval and time travel, see [Netezza Performance Server time travel](https://cloud.ibm.com/docs/netezza?topic=netezza-enablingdisabling_tt).
5. Click Save.







 Viewing privileges for databases 



1. Go to Databases.
2. Select the database which privileges you want to view.
3. From the overflow menu, click Show privileges.
A list of privileges is now displayed.







 Dropping databases 



1. Go to Databases.
2. Select the database that you want to drop.
3. From the overflow menu, click Drop.
4. Confirm your choice by clicking Drop.
* If an identifier is already in use on an object, the existing legal hold is not modified and the response indicates the identifier was already in use with a 409 error.
* If an object does not have retention period metadata, a 400 error is returned and adding or removing a legal hold is not allowed.



The presence of a retention period header is required, otherwise a 400 error is returned.

The user making adding or removing a legal hold must have Manager permissions for this bucket.

public static void addLegalHoldToObject(String bucketName, String objectName, String legalHoldId) {
System.out.printf("Adding legal hold %s to object %s in bucket %sn", legalHoldId, objectName, bucketName);

cos.addLegalHold(
bucketName,
objectName,
legalHoldId
);

System.out.printf("Legal hold %s added to object %s in bucket %s!n", legalHoldId, objectName, bucketName);
}

public static void deleteLegalHoldFromObject(String bucketName, String objectName, String legalHoldId) {
System.out.printf("Deleting legal hold %s from object %s in bucket %sn", legalHoldId, objectName, bucketName);

cos.deleteLegalHold(
bucketName,
objectName,
legalHoldId
);

System.out.printf("Legal hold %s deleted from object %s in bucket %s!n", legalHoldId, objectName, bucketName);
}
Show more





 Extend the retention period of a protected object 

The retention period of an object can only be extended. It cannot be decreased from the currently configured value.

The retention expansion value is set in one of three ways:



* additional time from the current value (Additional-Retention-Period or similar method)
* new extension period in seconds (Extend-Retention-From-Current-Time or similar method)
* new retention expiry date of the object (New-Retention-Expiration-Date or similar method)
Creating and altering objects for time travel 



 Overview 

To run time travel queries on Netezza Performance Server, create a time travel table, schema, or database (time travel objects) by setting DATA_VERSION_RETENTION_TIME (retention time interval) to a nonzero value. To set DATA_VERSION_RETENTION_TIME, use the CREATE or ALTER command for these object types or use the web console. You can select between 1 day and up to 99 days, or zero to alter a temporal object to nontemporal.

Before you set the retention time intervals for all tables in a schema or database, consider the cost of storage for temporal tables, which could be significant. See [Managing time travel space usage](https://cloud.ibm.com/docs/netezza?topic=netezza-managing_tt).

Also, you can [set a default DATA_VERSION_RETENTION_TIME for the system](https://cloud.ibm.com/docs/netezza?topic=netezza-dataretentioninterval_ttsettingretentioninterval_tt).

Temporal tables usually have current rows and historical rows. Current rows are not marked for deletion. Historical rows are marked for deletion (by the DELETE, UPDATE, MERGE, or TRUNCATE statements) and are visible to time travel queries up to the specified retention time interval past their delete timestamps.

A table with a DATA_VERSION_RETENTION_TIME value of zero is nontemporal. Only its current (not deleted) rows are visible to queries. Some historical rows might be preserved for incremental backup purposes, but the rows are not accessible to time travel queries.

If you alter DATA_VERSION_RETENTION_TIME of an existing temporal table to zero, the table becomes a nontemporal table. It no longer supports access to historical data with time travel queries.





 Limitations 

Changes to retention time intervals for tables, schemas, and databases are not replicated from primary to replica nodes. They are not historical (deleted) table rows either.
X-Clv-Request-Id: 3e8bdf1e-b611-4b83-a404-e7d3e58e60b0
Server: Cleversafe/3.14.9.53
X-Clv-S3-Version: 2.5
x-amz-request-id: 3e8bdf1e-b611-4b83-a404-e7d3e58e60b0

The server responds with 204 No Content.





 Add a retention policy on an existing bucket 

Immutable Object Storage is available in certain regions only, see [Integrated Services](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-service-availabilityservice-availability) for details. The service also requires a Standard pricing plan. See [pricing](https://www.ibm.com/cloud/object-storage) for details.

Find out more about Immutable Object Storage in the [documentation](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-immutable).

The minimum and maximum supported values for the retention period settings MinimumRetention, DefaultRetention, and MaximumRetention are a minimum of 0 days and a maximum of 365243 days (1000 years).

This operation does not make use of extra query parameters. The required Content-MD5 header needs to be the binary representation of a base64-encoded MD5 hash. The following snippet shows one way to achieve the content for that particular header.

Policies are enforced until the end of a retention period, and can not be altered until the retention period has expired. While IBM Cloud Object Storage makes use of the S3 API for most operations, the APIs used for configuring retention policies is not the same as the S3 API, although some terminology may be shared. Read this documentation carefully to prevent any users in your organization from creating objects that can not be deleted, even by IBM Cloud administrators.

Not all operations are supported in Satellite environments.
To protect your privacy, do not use personal data, such as your name or location, as a description for your secret group.

The maximum length is 1024 characters. The minimum length is 0 characters. The value must match regular expression /(.?)/.

--labels ([]string)
: Labels that you can use to search secrets in your instance. Only 30 labels can be created.

Label can be between 2-30 characters, including spaces.

To protect your privacy, do not use personal data, such as your name or location, as a label for your secret.

The list items must match regular expression /(.?)/. The maximum length is 30 items. The minimum length is 0 items.

--custom-metadata (generic map)
: The secret metadata that a user can customize.

--expiration-date (strfmt.DateTime)
: The date when the secret material expires. The date format follows the RFC 3339 format.

--ttl (string)
: The time-to-live (TTL) or lease duration to assign to credentials that are generated.

For iam_credentials secrets, the TTL defines for how long each generated API key remains valid. The value can be either an integer that specifies the number of seconds, or the string representation of a duration, such as 120m or 24h.

The minimum duration is 1 minute. The maximum is 90 days.

The maximum length is 10 characters. The minimum length is 2 characters. The value must match regular expression /^[0-9]+[s,m,h,d]{0,1}$/.

--rotation ([RotationPolicy](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-cli-plugin-secrets-manager-clicli-rotation-policy-example-schema))
: This field indicates whether Secrets Manager rotates your secrets automatically.





 Example
If there is not enough unreserved storage to satisfy the topic operation, it is rejected with a PolicyViolation error that explains the reason.

The reserved size calculation can change in the future if Kafka storage requirements are updated.





 Examples 

A nonobvious effect is that Kafka can reserve more storage than expected depending on your topic configurations. See the following examples.



1. A topic with retention.bytes of 1 GB, and with a log segment size of 512 MB:

With one partition, it would reserve about 1.5 GB of storage.
In this case, the reserved size is significantly larger than the retention size.
2. A topic with retention.bytes of 50 GB, and with a log segment size of 512 MB:

With one partition, it would reserve about 50.5 GB of storage.

In this case, the reserved size is very close to the retention size.
3. A topic with retention.bytes of 1 GB, and with a log segment size of 128 MB:

With one partition, it would reserve about 1.1 GB of storage.

In this case, the reserved size is very close to the retention size.