vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Changing the inactivity timeout setting 

When a user interacts with your assistant, the chat session ends after a specific period of time passes in which the user does not interact with the assistant. You can specify the amount of time to wait before a chat session is reset by changing the inactivity timeout setting.

When a chat session is reset, the dialog loses any contextual information that it saved during the previous exchange with the user. For example, if the dialog asks for the user's name and then calls the user by that name throughout the rest of the conversation, then after the chat session ends and a new one begins, the dialog will start by asking for the user's name again.



  Session limits 



Session inactivity timeout details

 Chat session default inactivity period  Chat session maximum inactivity period 

 1 hour                                  168 hours (7 days)                     







  Changing the setting 



1.  Click the menu for your assistant ![open and close list of options](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/kabob-beta.png), and then choose Settings.
2.  Change the time specified in the Timeout limit field.
3.  Close the settings page. Your change is saved automatically.
The table’s retention lower bound and retention start time are equal to or just before the commit time of this altering transaction.

Unlike when you create a table, existing visible rows in the table are treated as if they were inserted by this altering transaction. The existing visible rows receive virtual insert timestamps that are equal to the retention start time. With these timestamps, the rows are potentially visible to time travel queries.





 Altering temporal schemas to nontemporal with the web console 

To alter a temporal schema to nontemporal, set retention time interval to 0.



1. Log in to the web console as described in [Getting started with the web console](https://cloud.ibm.com/docs/netezza?topic=netezza-getstarted-console).
2. Alter your table as described in [Updating retention time interval for schemas](https://cloud.ibm.com/docs/netezza?topic=netezza-create-schemasupdating_rt_sch).







 Altering nontemporal schemas to temporal with the web console 

To alter a nontemporal schema to temporal, set retention time interval to a nonzero value.



1. Log in to the web console as described in [Getting started with the web console](https://cloud.ibm.com/docs/netezza?topic=netezza-getstarted-console).
2. Alter your table as described in [Updating retention time interval for schemas](https://cloud.ibm.com/docs/netezza?topic=netezza-create-schemasupdating_rt_sch).







 Altering temporal databases to nontemporal with the web console 

To alter a temporal database to nontemporal, set retention time interval to 0.



1. Log in to the web console as described in [Getting started with the web console](https://cloud.ibm.com/docs/netezza?topic=netezza-getstarted-console).
2.
"start_time": 3.03,
"confidence": 0.98,
"end_time": 3.84
}
],
"colorado":
{
"normalized_text": "Colorado",
"start_time": 4.58,
"confidence": 0.98,
"end_time": 5.16
}
]
},
"alternatives":
{
"timestamps":

"a",
0.15,
0.3
],

"line",
0.3,
0.64
],
. . .

"Colorado",
4.58,
5.16
],

"on",
5.16,
5.32
],

"Sunday",
5.32,
6.04
]
],
"confidence": 0.99,
"transcript": "a line of severe thunderstorms with several
possible tornadoes is approaching Colorado on Sunday "
}
],
"final": true
}
]
}
Show more





Contribute in GitHub

Open doc issue

Edit topic





On this page[Making a basic HTTP speech recognition request](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-httpHTTP-basic)[Basic request example](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-httpHTTP-basic-example)[Making a multipart HTTP speech recognition request](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-httpHTTP-multi)


Feedback

Focus sentinel

 Give us your feedback 

Tell us about your experience0/1500



Don't include any sensitive or personal information.

How satisfied are you with your experience?

How satisfied are you with your experience?

1
(https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/streaming-topic-2.png)
8. Select a Message retention and click Create Topic.

Message retention defines how long messages are retained before they are deleted. If your messages are not read by a consumer within this time, they will be missed.







 Step 2. Create credentials to authenticate the logging instance with Event Streams 

You need the following information to connect the IBM Log Analysis instance to the Event Streams instance:



* Endpoint URLs to call the APIs
* Credentials for authentication



Complete the following steps to create service credentials that the IBM Log Analysis instance needs to communicate with the Event Streams instance:



1. In the IBM Cloud, click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/icons/icon_hamburger.svg) > Resource list.
2. Look for the Event Streams instance that you plan to use, and select it.
3. In the Event Streams console, click Service credentials.
4. Select New credential.
5. Enter a name and select the writer role.

![Create a credential.](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/streaming-credentials.png)
6. Click Add.



To restrict access to 1 topic, complete the following steps:



1. From the menu bar, click Manage > Access (IAM), and select Service IDS.

!
Managing the default retention time interval for the system and viewing retention time intervals 

Before you set retention time interval 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/docs/netezza?topic=netezza-managing_tt).



 Setting the retention time interval for the system 

To set the default DATA_VERSION_RETENTION_TIME to a specific value for the system, run the SET SYSTEM DEFAULT command.

Before you set DATA_VERSION_RETENTION_TIME 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).

SET SYSTEM DEFAULT DATA_VERSION_RETENTION_TIME TO <NUMBER OF DAYS>

Example:

SET SYSTEM DEFAULT DATA_VERSION_RETENTION_TIME TO 30

The value of the property at the system level determines the default value inherited by a subsequent CREATE DATABASE statement that does not explicitly specify this property.

To set DATA_VERSION_RETENTION_TIME for a specific object, you can run the ALTER or CREATE command.





 Viewing the retention time interval with the command-line 



 Viewing the default retention time interval for the system with the command-line 

To view DATA_VERSION_RETENTION_TIME for the system, run the SHOW SYSTEM DEFAULT command.

SHOW SYSTEM DEFAULT DATA_VERSION_RETENTION_TIME

If you did not set the retention time previously, the default is 0.





 Viewing the retention time interval for tables, schemas, and databases with the command-line 

To view DATA_VERSION_RETENTION_TIME for a specific object, run one of these commands. The commands display DATA_VERSION_RETENTION_TIME only if it is a nonzero value.

d <table_name>

SHOW SCHEMA <schema_name>

l+ <all databases, with detail>

Retention time interval and retention lower bound for an object are available in the dataverretntime and dataverretnlowerbound columns of the following system views:



* _v_table
For more information about all available next-generation models, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng).





 21 September 2022 

New Activity Tracker event for GDPR deletion of user information
: The service now returns an Activity Tracker event when you use the DELETE /v1/user_data method to delete all information about a user. The event is named speech-to-text.gdpr-user-data.delete. For more information, see [Activity Tracker events](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-at-events).

Defect fix: Update some next-generation models to improve low-latency response time
: Defect fix: The following next-generation models were updated to improve their response time when the low_latency parameter is used:



* en-IN_Telephony
* hi-IN_Telephony
* it-IT_Multimedia
* nl-NL_Telephony



Previously, these models did not return recognition results as quickly as expected when the low_latency parameter was used. You do not need to upgrade custom models that are based on these models. For more information about all available next-generation models, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng).





 19 August 2022 

Important: Deprecation date for most previous-generation models is now 3 March 2023
: Superseded: This deprecation notice is superseded by the [15 February 2023 service update](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-release-notesspeech-to-text-15february2023). The end of service date for all previous-generation models is now 31 July 2023.

On 15 March 2022, the previous-generation models for all languages other than Arabic and Japanese were deprecated.
Updating retention time interval (time travel) for tables 



1. Go to Databases.
2. Select the database and schema in which the table that you want to update is.
3. Select the table.
4. From the overflow menu, click Update interval.
5. 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).
6. Click Save.







 Dropping tables 



1. Go to Databases.
2. Select the database and schema in which the table that you want to update is.
3. Select the table.
4. From the overflow menu, click Drop.
5. Confirm your choice by clicking Drop.







 Viewing space usage (time travel) 



1. Go to Databases.
2. Select the database and schema in which the temporal table that you want to analyze is located.
3. Select the table.
4. Go to the Time travel tab.
5. Analyze the data.
You can view the information in a list or as a chart.
* For more information about the next-generation models and their capabilities, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng).
* For more information about language support for next-generation models and about which next-generation models support low latency, see [Supported next-generation language models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ngmodels-ng-supported).
* For more information about feature support for next-generation models, see [Supported features for next-generation models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ngmodels-ng-features) and [Unsupported features for next-generation models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ngmodels-ng-unsupported).
* For more information about the low_latency parameter, see [Low latency](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-interimlow-latency).
* For more information about the interaction between the low_latency and interim_results parameters for next-generation models, see [Requesting interim results and low latency](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-interiminterim-low-latency).







 17 March 2021 

Defect fix: Fix limitation for asynchronous HTTP interface
: Defect fix: The limitation that was reported with the asynchronous HTTP interface in the Dallas (us-south) location on 16 December 2020 has been addressed. Previously, a small percentage of jobs were entering infinite loops that prevented their execution. Asynchronous HTTP requests in the Dallas data center no longer experience this limitation.





 2 December 2020 

Arabic model renamed to ar-MS_BroadbandModel
[Menu icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/icons/icon_hamburger.svg) > Resource list.
3. Look for the Event Streams instance that you plan to use, and select it.
4. Select Topics.
5. Click Create a topic.

![Create a topic.](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/streaming-topic.png)
6. Enter a topic name and click Next.

![Create a topic part 2.](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/streaming-topic-1.png)
7. Enter the number of partitions and click Next.

One or more partitions make up a topic. A partition is an ordered list of messages. Partitions are distributed across the brokers in order to increase the scalability of your topic. You can also use them to distribute messages across the members of a consumer group.

![Create a topic part 3.](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/streaming-topic-2.png)
8. Select a Message retention and click Create Topic.

Message retention defines how long messages are retained before they are deleted. If your messages are not read by a consumer within this time, they will be missed.







 Step 2.
Host: myBucket.mydsNet.corp.com
Date: Fri, 8 Dec 2018 17:50:00GMT
Authorization: authorization string
Content-Type: text/plain
Additional-Retention-Period: 31470552

Example response

HTTP/1.1 200 OK
Date: Fri, 8 Dec 2018 17:50:00GMT
Connection: close



* Java
* Python
* Node



public static void extendRetentionPeriodOnObject(String bucketName, String objectName, Long additionalSeconds) {
System.out.printf("Extend the retention period on %s in bucket %s by %s seconds.n", objectName, bucketName, additionalSeconds);

ExtendObjectRetentionRequest req = new ExtendObjectRetentionRequest(
bucketName,
objectName)
.withAdditionalRetentionPeriod(additionalSeconds);

cos.extendObjectRetention(req);

System.out.printf("New retention period on %s is %sn", objectName, additionalSeconds);
}

def extend_retention_period_on_object(bucket_name, object_name, additional_seconds):
print("Extend the retention period on {0} in bucket {1} by {2} seconds.n".format(object_name, bucket_name, additional_seconds))

cos.extend_object_retention(
Bucket=bucket_ame,
Key=object_name,
AdditionalRetentionPeriod=additional_seconds
)

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,
Updates to English next-generation telephony models
: The English next-generation telephony models have been updated for improved speech recognition:



* en-AU_Telephony
* en-GB_Telephony
* en-IN_Telephony
* en-US_Telephony



All of these models continue to support low latency. You do not need to upgrade custom models that are based on these models. For more information about all available next-generation models, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng).

Italian next-generation multimedia model now supports low latency
: The Italian next-generation multimedia model, it-IT_Multimedia, now supports low latency. For more information about next-generation models and low latency, see



* [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng)
* [Customization support for next-generation models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-custom-supportcustom-language-support-ng)
* [Low latency](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-interimlow-latency)



Important: Maximum hours of audio data being reduced for custom acoustic models
: Important: The maximum amount of audio data that you can add to a custom acoustic model is being reduced from 200 hours to 50 hours. This change is being phased into different locations from August to September 2022. For information about the schedule for the limit reduction and what it means for existing custom acoustic models that contain more than 50 hours of audio, see [Maximum hours of audio](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-audioResourcesaudioMaximum).





 3 August 2022 

Defect fix: Update speech hesitations and hesitation markers documentation
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)



The current retention period stored in the object metadata is either increased by the given additional time or replaced with the new value, depending on the parameter that is set in the extendRetention request. In all cases, the extend retention parameter is checked against the current retention period and the extended parameter is only accepted if the updated retention period is greater than the current retention period.

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. 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.

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 a protected object 

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
To view DATA_VERSION_RETENTION_TIME for a specific object, run one of these commands. The commands display DATA_VERSION_RETENTION_TIME only if it is a nonzero value.

d <table_name>

SHOW SCHEMA <schema_name>

l+ <all databases, with detail>

Retention time interval and retention lower bound for an object are available in the dataverretntime and dataverretnlowerbound columns of the following system views:



* _v_table
* _v_schema
* _v_database









 Viewing the retention time interval with the web console 



 Viewing the default retention time interval for the system with the web console 



1. Log in to the web console as described in [Getting started with the web console](https://cloud.ibm.com/docs/netezza?topic=netezza-getstarted-console).
2. Go to Databases. The retention time interval for the system is displayed in the Retention time interval section at the top of the page.







 Viewing the retention time interval for tables, schemas, and databases with the web console 



1. Log in to the web console as described in [Getting started with the web console](https://cloud.ibm.com/docs/netezza?topic=netezza-getstarted-console).
2. View the retention time interval:



* For a table:





1. Go to Databases.
2. Select the database and schema in which the table that you want to view the retention interval is located.
3. Ensure that you are in the DB Objects > Tables tab.
4. Identify the table for which you want to view the retention interval.

The retention interval is displayed in the Retention time interval (days) column.





* For a schema:





1. Go to Databases.
2. Select the database in which the schema that you want to view the retention interval is located.
3. Identify the schema for which you want to view the retention interval.

The retention interval is displayed in the Retention time interval (days) column.
[Menu icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/icons/icon_hamburger.svg) > Resource list.
3. Look for the Event Streams instance that you plan to use, and select it.
4. In the Event Streams instance console, click Manage > Launch Dashboard.
5. Click Create a topic.

![Create a topic.](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/streaming-topic.png)
6. Enter a topic name and click Next.

![Create a topic part 2.](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/streaming-topic-1.png)
7. Enter the number of partitions and click Next.

One or more partitions make up a topic. A partition is an ordered list of messages. Partitions are distributed across the brokers in order to increase the scalability of your topic. You can also use them to distribute messages across the members of a consumer group.

![Create a topic part 3.](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/streaming-topic-2.png)
8. Select a Message retention and click Create Topic.

Message retention defines how long messages are retained before they are deleted.
The object version can be be deleted after this date is passed (assuming there are no legal holds on the object version).

The retention period for new objects can be inherited from the default value set on the bucket, or it can be explicitly defined when writing the object by specifying a Retain Until Date.

When you use bucket default settings, you don’t specify a Retain Until Date. Instead, you specify a duration, in either days or years, for which every object version placed in the bucket should be protected. When you place an object in the bucket, a Retain Until Date is calculated for the object version by adding the specified duration to the time of the object write.

If your request to place an object version in a bucket contains an explicit retention mode and Retain Until Date, those settings override any bucket default settings for that object version.

Like all other Object Lock settings, the Retain Until Date applies to individual object versions. Different versions of a single object can have different retention modes and periods.

Imagine an object that is 60 days into a 90-day retention period, and you overwrite that object with the same name and a two year retention period. The operation will succeed and a new version of the object with a two year retention period is created. Meanwhile, after 30 more days the original version is eligible for deletion.





 Extending a retention period 

To extend the retention period of an object, simply send a request to set a new, longer, retention period. The old value will be overwritten with the new, assuming the requestor has the cloud-object-storage.object.put_object_lock_retention and cloud-object-storage.object.put_object_lock_retention_version actions.





 Legal Hold 

A legal hold is like a retention period in that it prevents an object version from being overwritten or deleted. However, legal holds are more flexible and don't have a defined temporal component. Instead they simply remain in effect until removed. Legal holds can be freely placed and removed by any user who has the cloud-object-storage.object.put_object_lock_legal_hold and cloud-object-storage.object.put_object_lock_legal_hold_version actions.

Legal holds have the additional benefit of acting as method for applying indefinite retention on an object.