vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Find more information on the [Security page](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-securitysecurity).





 7 September 2018 

The following changes were made in build 7205:

Refactor Mango Query selectors
: Refactor Mango Query selectors to reduce the amount of traffic sent between nodes in the cluster.

Document update errors
: Expose document update errors on concurrent document updates to client.

render_error errors
: Fix render_error errors where the req object that is passed to the JavaScript list function is set to noproc Atom.







 August 2018 



 1 August 2018 

The following changes were made in build 7138:

Erlang
: Upgrade to Erlang OTP 20.





 15 August 2018 

The following changes were made in build 7137:

Validation of configuration parameters
: Improve validation of configuration parameters supplied by administrator.

Compaction
: While compaction is running, delete compaction files when database is deleted.

Sandboxing feature
: Improve sandboxing features.

Authentication check
: Optimize authentication check.

Semantics
: Change semantics of status codes for delete database.

conflicts: true support
: Support conflicts: true for queries to the /{db}/_find endpoint.

update_seq field
: Preserve update_seq field across view compaction.







 July 2018 



 12 July 2018 

The following changes were made in build 7084:

stats reducer
: Refactor code for _stats reducer.

Views
: Fix active size calculations for views.

couch_key_tree algorithm
: Rewrite the couch_key_tree algorithm to reduce its computational complexity and avoid calling stemming when unnecessary.

Allocation strategy
: Change the allocation strategy for the message queue for each important process, so it's not stored on the heap of that process.

Internal audit facility
: Improvements to internal audit facility.

Constant fields
: Any constant fields that are in the selector, and are part of the index.
});

from ibmcloudant.cloudant_v1 import CloudantV1

service = CloudantV1.new_instance()

response = service.post_search(
db='movies',
ddoc='searches',
index='movies',
query='movie_name:Azazel',
highlight_fields=['"movie_name"]'],
highlight_pre_tag='" "',
highlight_post_tag='" "',
highlight_size=30,
highlight_number=2
).get_result()

print(response)

postSearchOptions := service.NewPostSearchOptions(
"movies",
"searches",
"movies",
"movie_name:Azazel",
)
postSearchOptions.SetHighlightFields([]string{"["movie_name"]"})
postSearchOptions.SetHighlightPreTag("" "")
postSearchOptions.SetHighlightPostTag("" "")
postSearchOptions.SetHighlightSize(30)
postSearchOptions.SetHighlightNumber(2)

searchResult, _, err := service.PostSearch(postSearchOptions)
if err != nil {
panic(err)
}

b, _ := json.MarshalIndent(searchResult, "", " ")
fmt.Println(string(b))

The previous Go example requires the following import block:

import (
"encoding/json"
"fmt"
"github.com/IBM/cloudant-go-sdk/cloudantv1"
)

See the following example of highlighted search results:

{
"highlights": {
"movie_name": [
" on the Azazel Orient Express",
" Azazel manuals, you"
]
}
}





 Search index metadata
In the app menu, select Restart App.







 Changing a plan through the CLI 

As an alternative to the console, you can change the Continuous Delivery service's pricing plan by using the IBM Cloud command-line interface (CLI).



1. Check whether the service is enabled with the resource controller.

ibmcloud catalog service continuous-delivery

If the service is enabled with the resource controller (RC), it lists RC Compatible true. Make note of the ID of the plan that you want to change to.

ID 59b735ee-5938-4ebd-a6b2-541aef2d1f68
Name continuous-delivery
Kind service
Provider IBM
Tags dev_ops, eu_access, gc_migrate, ibm_created, lite, rc_compatible
Active true
Description Support DevOps best practices by using Git, issue tracking, and CI/CD pipelines in the Cloud.
Bindable false
Original Name continuous-delivery
RC Compatible true
RC Provisionable true
IAM Compatible true
Children Name Kind ID
lite plan a35fb0e9-4fc2-400e-8161-49078e5af632
professional plan 9ca4dc64-bc7b-4aba-9c1c-8bbf30ff127e
2. Change the plan for your service instance by using the [ibmcloud resource service-instance-update command](https://cloud.ibm.com/docs/cli/reference/ibmcloud?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_update).

ibmcloud resource service-instance-update <service_instance_name>
--service-plan-id <plan_id>









 Delivery Pipeline usage 

Delivery pipelines under a Continuous Delivery service instance Lite plan have several limitations.



* The 500-step and job run limit includes both pipeline steps for Tekton pipelines and pipeline job runs for Classic pipelines. If your pipeline has many steps within a single run, such as with the DevSecOps pipelines, you might reach this limit quickly.
Users of existing instances need to migrate from the service before the end of service date. You can find guidance on migrating from IBM Cloudant on Transaction Engine to IBM Cloudant Standard here: [Migrating from TXE](https://blog.cloudant.com/2022/01/14/Migrating-from-Cloudant-TXE-to-Standard).



 What is Transaction Engine? 

IBM Cloudant has an architecture option, which is underpinned by a Transaction Engine. This architecture aims to provide the best of both nonrelational and relational data stores combining scale, fault tolerance, consistency, security, and speed at optimal cost. The Transaction Engine architecture is compared to the "Classic" architecture for clarity in the documentation. Instances that are provisioned with the Standard on Transaction Engine plan are deployed by using this architecture, while instances on the Lite and Standard plan are deployed on the "Classic" architecture.







 IBM Cloudant dbcopy feature removal 

As of 1 October 2023, IBM Cloudant's dbcopy feature (also known as "Chained MapReduce" or "view chaining") will cease to function. The dbcopy feature was [removed from our documentation in 2016](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-classic-release-notescloudant-feb16) and [since November 2022, new users cannot configure dbcopy](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-classic-release-notescloudant-nov22). Starting 1 October 2023, the dbcopy feature will be removed from the IBM Cloudant service entirely.



 What is dbcopy? 

IBM Cloudant allows materialized MapReduce views to be created on a database - a secondary index structure that contains user-defined keys and values. MapReduce views exist and are queried in the same path as the primary database.

With the "dbcopy" feature configured, the MapReduce data is instead written to a second database. The second database then contains the key/value pairs that would usually be found in the materialized view of a normal MapReduce view.
VSI on VPC landing zone - Standard variation 

The Standard variation of the VSI on VPC landing zone deployable architecture is based on the IBM Cloud for Financial Services reference architecture. The architecture creates a customizable and secure infrastructure, with virtual servers, to run your workloads with a Virtual Private Cloud (VPC) in multizone regions.



 Architecture diagram 

Zoom

![Architecture diagram for the Standard variation of VSI on VPC landing zone](https://cloud.ibm.com/docs-content/v1/content/bbc046343d620cb2210cb1c62a46d7601ae08e00/secure-infrastructure-vpc/includes/deployable-reference-architectures/terraform-ibm-landing-zone/includes/deployable-reference-architectures/terraform-ibm-landing-zone/vsi-vsi.drawio.svg)

Figure 1. Standard variation of VSI on VPC landing zone





 Design requirements 

Zoom

![Design requirements for VSI on VPC landing zone](https://cloud.ibm.com/docs-content/v1/content/bbc046343d620cb2210cb1c62a46d7601ae08e00/secure-infrastructure-vpc/includes/deployable-reference-architectures/terraform-ibm-landing-zone/includes/deployable-reference-architectures/terraform-ibm-landing-zone/heat-map-deploy-arch-slz-vsi.svg)

Figure 2. Scope of the design requirements





 Components 



 VPC architecture decisions 



Table 1. Architecture decisions

 Requirement Component Reasons for choice Alternative choice 

 <br><br> * Provide infrastructure and administration access<br> * Limit the number of infrastructure administration entry points to ensure security audit<br><br><br> Management VPC service Create a separate VPC service for management and maintenance of workload resources and access through a site-to-site VPN
from ibmcloudant.cloudant_v1 import CloudantV1

service = CloudantV1.new_instance()

response = service.post_search_analyze(
analyzer='keyword',
text='ablanks@renovations.com'
).get_result()

print(response)

postSearchAnalyzeOptions := service.NewPostSearchAnalyzeOptions(
"keyword",
"ablanks@renovations.com",
)

searchAnalyzeResult, _, err := service.PostSearchAnalyze(postSearchAnalyzeOptions)
if err != nil {
panic(err)
}

b, _ := json.MarshalIndent(searchAnalyzeResult, "", " ")
fmt.Println(string(b))

The previous Go example requires the following import block:

import (
"encoding/json"
"fmt"
"github.com/IBM/cloudant-go-sdk/cloudantv1"
)

See the following result that tests the keyword analyzer:

{
"tokens": [
"ablanks@renovations.com"
]
}

See the following example that uses HTTP to test the standard analyzer:

Host: $ACCOUNT.cloudant.com
POST /_search_analyze HTTP/1.1
Content-Type: application/json
{"analyzer":"standard", "text":"ablanks@renovations.com"}

See the following example that uses the command line to test the standard analyzer:

curl "https://$ACCOUNT.cloudant.com/_search_analyze" -H "Content-Type: application/json"
-d '{"analyzer":"standard", "text":"ablanks@renovations.com"}'

See the following result of testing the standard analyzer:

{
"tokens": [
"ablanks",
You must use a paid plan to use customization.

The Lite plan is intended for any user who wants to try out the service before committing to a purchase. For more information, see the Speech to Text service in the [IBM Cloud® Catalog](https://%7BDomainName%7D/catalog/speech-to-text). Services that are created with the Lite plan are deleted after 30 days of inactivity.
* What is the price for using the Speech to Text Plus plan?

The Plus plan provides access to all of the service's features:



* Use of all available models (same as the Lite plan).
* Unlimited creation and use of custom language and custom acoustic models at no extra charge.
* A maximum of one hundred concurrent transcription requests from all interfaces, WebSocket and HTTP, combined.



The plan uses a simple tiered pricing model to give high-volume users further discounts as they use the service more heavily. Pricing is based on the aggregate number of minutes of audio that you recognize per month:



* Users who recognize 1 to 999,999 minutes of audio in a given month pay $0.02 (USD) per minute of audio for that month.
* Users who recognize at least 1,000,000 minutes of audio in a given month pay $0.01 (USD) per minute of audio for that month.



The Plus plan is intended for small businesses. It is also a good choice for large enterprises that want to develop and test larger applications before considering moving to a Premium plan. For more information, see the Speech to Text service in the [IBM Cloud® Catalog](https://%7BDomainName%7D/catalog/speech-to-text).
* Can I continue to use the Speech to Text Standard plan?

The Standard plan is no longer available for purchase by new users. But existing users of the Standard plan can continue to use the plan indefinitely with no change in their pricing. Their API settings and custom models remain unaffected.

Existing users can also choose to upgrade to the new Plus plan by visiting the [IBM Cloud® Catalog](https://%7BDomainName%7D/catalog/speech-to-text).
If you created a Lite account before 25 October 2021, your account doesn't expire and you can work in IBM Cloud for free by accessing services with select Lite plans, which are displayed with a Lite tag ![Lite tag](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/Lite.svg) in the catalog. To gain access to all Free plans, you can go ahead and [upgrade to a Pay-As-You-Go account](https://cloud.ibm.com/docs/account?topic=account-accountfaqschangeacct) by adding your credit card information.

Starting 25 October 2021, all new accounts are created as Pay-As-You-Go based on an update to our account registration process. As part of this update, you're asked to provide credit card information for identity verification. You have full access to the catalog, including all Free and Lite plans, and you get a $200 credit that you can apply in your first 30 days. You pay only for billable services that you use, with no long-term contracts or commitments.

Lite accounts have access to a single resource group that's created for you with the name Default. All of your service's instances are automatically added to this resource group. You can update the name of this resource group at any time. See [Renaming a resource group](https://cloud.ibm.com/docs/account?topic=account-rgsrename_rgs) for the detailed steps.



 What's available in a lite account? 

Check out the following list of key features that are available in a Lite account:



* The account is free - no credit card required.
* The account never expires.
* You receive email notifications about your account status and quota limits.
* You can create one instance of any service in the [IBM Cloud catalog](https://cloud.ibm.com/catalog/?search=label:lite%20lite) that has a Lite plan.
Plan comparison 

IBM Cloud® Internet Services offers several plans to choose from: no-cost Trial, Standard Next, and Enterprise Tier variations.

The no-cost Trial plan is the same as the Standard Next plan, except that it expires after 30 days. Only one trial is available per account. After the Trial plan has expired, it is automatically subject to reclamation.

The numbers in these tables are quotas or resource limits for the associated feature. Features are pay-as-you-go, except for Trial and Standard Next plans.

The following table compares each offering to help you choose the one that's right for you. Enterprise Tier plans are available with different pricing models.



Table 1. CIS plan comparison

 Standard Next Enterprise Essentials Enterprise Advanced Enterprise Premier Enterprise Usage 

 Domain 1 1 2 2 Up to 1000, but recommend no more than 20 
 DNS 250 records 3500 records 3500 records 3500 records 3500 records
Allow a few minutes for the cached limit of 1 partition for the Lite plan to clear so that you can take advantage of the 100 partition limit for the Standard plan.

However, this option does not currently work in the IBM Cloud console for any other combination of plans. For example, if you try a different plan combination, you'll see an error message like the the following:

Could not find VCAP::CloudController::ServicePlan with guid: ibm.eventstreams.standard







 What are the differences between the Event Streams Standard and Event Streams Enterprise plans? 

To find out more information about the different Event Streams plans, see [Choosing your plan](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-plan_choose).





 How do I handle disaster recovery? 

Currently, it is the responsibility of the user to manage their own Event Streams disaster recovery. Event Streams data can be replicated between an Event Streams instance in one location (region) and another instance in a different location. However, the user is responsible for provisioning a remote Event Streams instance and managing the replication.

We suggest a tool like Kafka MirrorMaker to replicate data between clusters. For information about how to run MirrorMaker, see [Event Streams kafka-mirrormaker repository](https://github.com/ibm-messaging/event-streams-samples/tree/master/kafka-mirrormaker).

The user is also responsible for the backup of message payload data. Although this data is replicated across multiple Kafka brokers within a cluster, which protects against the majority of failures, this replication does not cover a location-wide failure.

Topic names are backed up by Event Streams, although it is recommended good practice for users to back up topic names and the configuration data for those topics.

If you have configured your Event Streams instance in a Multi-Zone Region, a regional disaster is very unlikely. However, we recommend that users do plan for such circumstances. If a user's instance is no longer available because of a disaster (and a remote DR instance is not already set up), the user should consider configuring a new instance in a new region and restoring their topics and data from backup if available.
This version of the CLI plug-in is deprecated; upgrade to the latest release.

Version 0.0.4 of the CLI was released on 04 March 2022.



* Updates Go version from 1.14 to 1.17.
* Uses IBM Cloudant Go SDK version: 0.0.43.
* Improves error messages for bad URL scenarios.
* Enables auto-completion.
* Introduces IBM Cloudant CLI-specific User-Agent header content.







 Version 0.0.3 

This version of the CLI plug-in is deprecated; upgrade to the latest release.

Version 0.0.3 of the CLI was released on 12 May 2021.

From now on, IBM Cloudant CLI plug-in is available for managing throughput capacity, Activity Tracker events, and retrieving data usage.
Cloud-based storage in IBM Cloudant ensures higher availability than when it was locked in an on-premises system. Since availability is essential, the apps are deployed across global data centers: for DR and for latency too.

They also accelerated their risk analysis and compliance. Their predictive and risk analytics functions, such as Monte Carlo calculations, are now constantly updated through iterative agile deployments. Container orchestration is handled by a managed Kubernetes so that operations costs are reduced too. Ultimately risk analysis for mortgages is more responsive to the fast-paced changes in the market.



* Heightened need for better financial risk management drives increases in regulatory oversight. The same needs drive the associated review in risk assessment processes and disclosure of more granular, integrated, and abundant regulatory reporting.
* High Performance Computing Grids are the key infrastructure components for financial modeling.



The problem of the company is scale and time to delivery.

Their current environment is 7+ years old, on-premises, and with limited compute, storage, and I/O capacity. Server refreshes are costly and take a long time to complete. Software and app updates follow an informal process and aren't repeatable. The actual HPC grid is hard to program against. The API is too complex for new Developers who join the team and requires non-documented knowledge. And major app upgrades take 6 - 9 months to complete.





 Solution 

Compute, storage, and I/O services that run in public cloud with secure access to on-premises enterprise assets as needed.



* Secure and scalable document storage that supports structured and unstructured document query
* Lift and shift existing enterprise assets and app while they enabled the integration to some on-premises systems that won't be migrated
* Shorten time-to-deploy solutions and implement standard DevOps and monitoring processes to address bugs that affected reporting accuracy



Technical solution:



* Red Hat OpenShift on IBM Cloud
* IBM Cloud Object Storage
* IBM Cloud Data Engine (Spark)
* IBM Cloudant
* Secure Gateway



Red Hat OpenShift on IBM Cloud provides scalable compute resources and the associated DevOps dashboards to create, scale, and tear down apps and services as needed.
Pricing 

Natural Language Understanding has two pricing plans: Lite and Standard.

This page contains pricing information in USD. To view pricing information in your local currency, see the [Natural Language Understanding](https://cloud.ibm.com/catalog/natural-language-understanding) page in the IBM Cloud® catalog.



 Lite 

The Lite plan is free for users who are looking to try out Natural Language Understanding or build a proof-of-concept.

Pricing



* Free 30,000 NLU items/month



Custom Model



* 1 free custom model







 Standard 

A "pay-as-you-go" plan that is recommended once you are ready to move your application from proof-of-concept to production.

Pricing (billed monthly)



* Tier 1: $0.003/NLU item for the first 1-250,000 NLU items
* Tier 2: $0.001/NLU item for 250,001 to 5,000,000 NLU items
* Tier 3: $0.0002/NLU item for additional NLU items past 5,000,000



Custom Entities and Relations Models ($/custom model/month)



* $800 for all tiers



Custom Classification Model ($/custom classification model/month)



* $25 for all tiers







 What is an NLU item? 

API usage is measured in NLU items. One NLU item is one text unit (up to 10,000 characters of text) that is analyzed for one feature, such as sentiment.

To keep track of the number of NLU items in your request, you can examine the usage object in the response. For example, analyzing 15,000 characters of text for sentiment, emotion, and keywords will return the following usage information.

"usage": {
"text_units": 2,
"text_characters": 15000,
"features": 3
}

There are 2 text units and 3 features in the request, so there are 2 × 3 = 6 NLU items.

Text units are counted seperately for each request. If one request analyzes 15,000 characters and another request analyzes 3,000 characters, that counts as 3 text units total.
* Can I continue to use the Speech to Text Standard plan?

The Standard plan is no longer available for purchase by new users. But existing users of the Standard plan can continue to use the plan indefinitely with no change in their pricing. Their API settings and custom models remain unaffected.

Existing users can also choose to upgrade to the new Plus plan by visiting the [IBM Cloud® Catalog](https://%7BDomainName%7D/catalog/speech-to-text). They will continue to have access to all of their settings and custom models after upgrading. And, if they find that the Plus plan does not meet their needs for any reason, they can always downgrade back to their Standard plan.
* What pricing plan do I need to use the service's customization interface?

You must have a paid plan (Plus, Standard, or Premium) to use language model or acoustic model customization. Users of the Lite plan cannot use customization. To use customization, users of the Lite plan must upgrade to a paid plan such as the Plus plan.
* How do I upgrade from the Lite plan to the Plus plan?

You can upgrade from the Lite plan to the Plus plan, for example, to gain access to customization. To upgrade from the Lite plan to the Plus plan, use the Upgrade button in the resource catalog page for your service instance:



* From the [resource list](https://cloud.ibm.com/resources), click on your Speech to Text instance to go to the Speech to Text dashboard page.
* From the Manage page, click Upgrade to move to the Plus plan.
* Follow the steps on the Plan page to complete your upgrade.



* What does "pricing per minute" mean?

For the Plus plan, pricing is based on the cumulative amount (number of minutes) of audio that you send to the service in any one month. The per-minute price of all audio that you recognize in a month is reduced once you reach the threshold of one million minutes of audio for that month. The price does not depend on how long the service takes to process the audio. (Per-minute pricing is different for the Standard plan.)