vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The Accept header specifies the list of potential data types that are returned by the server that would be accepted and understood by the client. The format is a list of one or more MIME types, which are separated by colons.

For the most requests, the accepted list must include JSON data (application/json).

For attachments, you can either specify the MIME type explicitly, or use / to specify that all file types are supported.

If the Accept header is not supplied, then the server assumes the / MIME type, which means that the client accepts all formats.

See the following example of sending a request without an explicit Accept header, or when you specify /:

GET /recipes HTTP/1.1
Host: username.cloudant.com
Accept: /

See the following example of a returned header when the client is assumed to accept all formats.

The returned content type is text/plain even though the information that is returned by the request is in JSON format.

Server: CouchDB/1.0.2 (Erlang OTP/R14B)
Date: Thu, 13 Jan 2011 13:39:34 GMT
Content-Type: text/plain;charset=utf-8
Content-Length: 7
Cache-Control: must-revalidate

The use of Accept in queries to IBM Cloudant is not required, but is highly recommended as it helps to ensure that the data returned can be processed by the client.

If you specify a data type that uses the Accept header, IBM Cloudant honors the specified type in the Content-type header field of responses. For example, if you explicitly request application/json in the Accept of a request, the returned HTTP headers use this value in the returned Content-type field.

See the following example request that explicitly specifies the Accept header:

GET /recipes HTTP/1.1
Host: username.cloudant.com
Accept: application/json

See the following example of the headers returned in response, including the application/json content type:

Server: CouchDB/1.0.2 (Erlang OTP/R14B)
Date: Thu, 13 Jan 2011 13:40:11 GMT
More information on JVM memory usage can be found at the developerWorks article [Thanks for the memory](http://www.ibm.com/developerworks/library/j-nativememory-linux/)

When you deploy an app, the memory usage of the entire process is monitored. If memory usage exceeds the memory limit that you specified when the app was deployed, the kernel stops the process. This action happens without warning and might be manifested in several ways.

If the Memory Limit is exceeded during app deployment, you receive a message that a failure occurred and you might see any the following.



* You might see that the app is flapping.
* You might see that the app attempted to start multiple times, always unsuccessfully.
* You might receive a message that indicates the app deployment failed.



If the Memory Limit is exceeded while the app is in service, the process stops and Cloud Foundry attempts to restart the app. The app might restart, but it is unavailable for some amount of time.





 Heap memory options 

You can customize the maximum amount of heap memory your app is allocated in various ways including by using the JVM_ARGS environment variable, changing the jvm.options file, or setting the JBP_CONFIG_IBMJDK environment variable which controls the heap_size_ratio. If you do not specify any settings, the buildpack uses the default settings.



 Heap memory defaults 

To prevent errors that result from exceeding memory limits, the Liberty for Java buildpack sets a default heap size ratio depending on the memory limit that you specify when you deploy your app.



* Apps with memory limits of less than 512M have a heap size ratio of 50%
* Apps that have memory limits greater than or equal to 512M have a heap size ratio of 75%



When you specify the heap memory using environment variables, you override the default heap size ratios.





 Specifying Heap Memory 

You can set the heap memory size by using environment variables or by changing the jvm.options file. When you use either the JVM_ARGS or JBP_CONFIG_IBMJDK environment variables, any changes will take effect when pushing your app to IBM Cloud.
* To adjust IOPS, the file share must be in a stable state.
* For a file share created with an [IOPS tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=uifs-tiers) to increase or decrease IOPS, select a different profile for the file share size. If the file share size exceeds that of the new IOPS tier profile, you can't change the profile.
* A [custom IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=uicustom) can expand to the maximum allowed by the custom band. You can't switch custom bands unless you increase file share size and then move to a higher band.
* A [dp2 profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&nterface=uidp2-profile) can expand to the maximum allowed by the dp2 band. You can't switch dp2 bands unless you increase file share size and then move to a higher band.
* Adjusting IOPS by moving between profiles is restricted by the file share size.
* When you use a custom or dp2 profile, IOPS can be adjusted multiple time until the maximum or minimum limit is reached.
* Maximum IOPS for a file share for all profiles is [96,000 IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=uifs-tiers). For 96,000 IOPS to be realized, a single file share must be accessed by multiple virtual server instances. A single file share in an instance is limited to 48,000 IOPS.







 Adjust IOPS in the UI 

Follow these steps to adjust IOPS by selecting a new IOPS tier or custom IOPS band:



1. Go to the list of file shares. In [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon !
* Adjust IOPS from a custom or dp2 profile to an IOPS tier profile. Again, you're restricted to which IOPS tier profile you can select by the file share size. When you move from a custom or dp2 profile to any tiered profile, billing is updated, and the IOPS is adjusted according to the profile.



To adjust a file share's IOPS, the file share must be in a stable state. Your user authorization is verified before IOPS is adjusted.

You can use the [UI](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-share-iopsfs-adjust-vpc-iops-ui-file), [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-share-iopsfs-adjust-vpc-iops-cli-file), or [API](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-share-iopsfs-adjust-vpc-iops-api-file) to adjust IOPS. You can adjust the file share's IOPS multiple times up to its maximum limit or reduce IOPS to its minimum limit.

You can monitor the progress of your file share's IOPS change from the UI or CLI. You can also use the [Activity Tracker](https://cloud.ibm.com/docs/vpc?topic=vpc-at-events) to verify that the IOPS were adjusted.





 Limitations 

The following limitations apply.



* To adjust IOPS, the file share must be in a stable state.
* For a file share created with an [IOPS tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=uifs-tiers) to increase or decrease IOPS, select a different profile for the file share size. If the file share size exceeds that of the new IOPS tier profile, you can't change the profile.
Memory limits and the Liberty buildpack 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

A memory limit must be specified when you deploy an app with the Liberty buildpack.



 Memory limits and the Liberty buildpack 

When you deploy an app with the Liberty buildpack, you are prompted for a "Memory Limit". The Liberty for Java buildpack sets a default heap memory size ratio to prevent your process from exceeding the memory limit. You can also specify the heap memory size or ratio by defining the JVM_ARGS or JBP_CONFIG_IBMJDK environmental variables. See [Heap memory options](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-memory_limitsheap_memory_options) to learn more.

To determine what Memory Limit to specify, it is important to understand that you are not specifying the size of the Java app heap. You are specifying the amount of memory available for the Diego container to use. This amount includes the memory that is used by the following components:



* by the warden container.
* to map kernel extensions and system libraries into the process.
* for the JVM executables, JVM working heap, JIT space, and compressed references.
* for classes (app server and app), thread stacks, and direct I/O buffers.
* by the Java app heap.



More information on JVM memory usage can be found at the developerWorks article [Thanks for the memory](http://www.ibm.com/developerworks/library/j-nativememory-linux/)

When you deploy an app, the memory usage of the entire process is monitored. If memory usage exceeds the memory limit that you specified when the app was deployed, the kernel stops the process. This action happens without warning and might be manifested in several ways.
* Adjust IOPS from a custom or dp2 profile to an IOPS tier profile. Again, you're restricted to which IOPS tier profile you can select by the file share size. When you move from a custom or dp2 profile to any tiered profile, billing is updated, and the IOPS is adjusted according to the profile.



To adjust a file share's IOPS, the file share must be in a stable state. Your user authorization is verified before IOPS is adjusted.

You can use the [UI](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-share-iops&interface=uifs-adjust-vpc-iops-ui-file), [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-share-iops&interface=uifs-adjust-vpc-iops-cli-file), or [API](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-share-iops&interface=uifs-adjust-vpc-iops-api-file) to adjust IOPS. You can adjust the file share's IOPS multiple times up to its maximum limit or reduce IOPS to its minimum limit.

You can monitor the progress of your file share's IOPS change from the UI or CLI. You can also use the [Activity Tracker](https://cloud.ibm.com/docs/vpc?topic=vpc-at-events) to verify that the IOPS were adjusted.





 Limitations 

The following limitations apply.



* To adjust IOPS, the file share must be in a stable state.
* For a file share created with an [IOPS tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=uifs-tiers) to increase or decrease IOPS, select a different profile for the file share size. If the file share size exceeds that of the new IOPS tier profile, you can't change the profile.
Prefer: return=minimal header
: Added the header Prefer: return=minimal to return only essential headers. This header reduces the size of the request, which gives a performance improvement to nonbrowser clients.

Disabled JavaScript constructors
: If a user calls the disabled JavaScript constructors, eval() or Function(), an error message similar to this one is returned, Call to eval() was blocked by CSP. You can fix the problem by replacing eval() calls with the calls from the [expr-eval library](https://github.com/silentmatt/expr-eval).





 4 December 2017 

Removed support for virtual hosts
: IBM Cloudant disabled the virtual host functionality on 4 December 2017. Support for insecure HTTP connections was replaced by HTTPS only. After you turn off HTTP support, the virtual hosts feature is no longer available since use of virtual hosts precludes secure HTTPS connections. Previous users of the virtual host feature need to make alternative arrangements to present a chosen hostname to your clients from your application and use HTTPS connections only.







 November 2017 



 7 November 2017 

Incompatibility between CouchDB version 1.6 and IBM Cloudant version 2.0.0
: An incompatibility exists between the most recent version of IBM Cloudant and CouchDB 1.6-based codebase. In the older version of IBM Cloudant, if you add a query parameter ("reduce=false") to the request body, the parameter in the request body is ignored. However, the parameter in the request URL is respected. In recent versions of IBM Cloudant, the query parameter ("reduce=false") in the request body isn't ignored.







 October 2017 



 17 October 2017 

Query (_find endpoint) improved
: IBM Cloudant Query now uses a new method to select an index. Learn more about [IBM Cloudant Query index selection](https://www.ibm.com/support/pages/improving-cloudant-query-index-selection).

Index validation
: The logic for determining whether a specific index is valid for a query that changed, addressing a bug that might lead to incorrect results.

Text indexes
For more information about strategies for handling complex actions with a webhook, watch the video in [Making a programmatic call from dialog](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-webhooks).



Analytics Analytics Engine



* Is IBM Cloud Object Storage included in IBM Analytics Engine?

No, IBM Cloud Object Storage isn't included. It is a separate offering. To learn more about IBM Cloud Object Storage, see the [product documentation](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cloud-object-storage) or the [documentation about its functionality](https://www.ibm.com/cloud/object-storage).
* How does IBM Cloud Object Storage work in the IBM Analytics Engine Hadoop environment?

Is it exactly equivalent to HDFS, only that it uses a different URL?

IBM Cloud Object Storage implements most of the Hadoop File System interface. For simple read and write operations, applications that use the Hadoop File System API will continue to work when HDFS is substituted by IBM Cloud Object Storage. Both are high performance storage options that are fully supported by Hadoop.
* What other components like IBM Cloud Object Storage should I consider while designing a solution using IBM Analytics Engine?

In addition to using IBM Cloud Object Storage for storing your data, consider using Databases for PostgreSQL, available on IBM Cloud, for persisting Hive metadata. Persisting Hive metadata in an external relational store like Databases for PostgreSQL allows you to reuse this data again after clusters were deleted or access to clusters was denied.
* How should I size my cluster?

Sizing a cluster is highly dependent on workloads. Here are some general guidelines:

For Spark workloads reading data from IBM Cloud Object Storage, the minimum RAM in a cluster should be at least half the size of the data you want to analyze in any given job. For the best results, the recommended sizing for Spark workloads reading data from the object store is to have the RAM twice the size of the data you want to analyze.
Troubleshooting ingestion 

Learn about solutions and workarounds to warnings or errors that you might encounter when you add data to a collection.

This information applies both to managed and installed instances of Discovery. For more troubleshooting tips for installed deployments only, see [Troubleshooting IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data deployments](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-troubleshoot).

Unable to process one or more documents
: This notification is displayed in the page header when a processing delay of any kind occurs in any project across the entire service instance. If the message is displayed while you are adding data to a collection, you can ignore it. If any problems occur that are related to the creation of your collection, a message is displayed in the Activity page for the collection. Check there for any pertinent messages.

This document exceeds the 1MB limit for non-HTML fields
: The html field in the document index stores structural information about the document. If you add a single document with complex tables, images, or other objects that need to be represented in HTML, you might hit the size limit for this field. To work around this issue, consider breaking the source file up into 2 or more smaller files, and then add the files to the same collection separately so that you can apply enrichments and search them together.



 Microsoft document troubleshooting tips 

Failed to prepare document for SDU processing
: Some DOC, PPT, and XLS files that use older features which are no longer supported by Microsoft Office can cause ingestion issues. If you encounter this issue, open the file in a more recent version of Microsoft Office and convert the file to the DOCX, PPTX, or XLSX format respectively, and then upload the DOCX, PPTX, or XLSX file.

Line breaks are inserted randomly
: When some files in Microsoft Office format are added to a collection, line breaks are inserted seemingly at random to the text that is stored in the html field in the collection's index. The unexpected line breaks can impact the efficiency of enrichments, such as custom rule recognition.
You can choose to completely opt out (as in the dashDB scenario) or opt out of only the server.xml file configuration updates (as in the cloudant scenario). The value that you specify for the services_autoconfig_excludes environment variable is a string as shown below.



* The string can contain opt-out specifications for one or more services.
* The opt-out specification for a specific service is service_type=option, where:



* The service_type is the label for the service as displayed in VCAP_SERVICES.
* The option is either all or config.



* If the String contains an opt-out specification for more than one service, the individual opt-out specifications must be separated by a single white-space character.



See the following example of services_autoconfig_excludes string grammar:

Opt_out_string :: <service_type_specification[<delimiter>service_type_specification]
<service_type_specification> :: <service_type>=<option>
<service_type> :: service type (service label as it appears in VCAP_SERVICES)
<option> :: all | config
<delimiter> :: one white space character

Important: The service type that you specify must match the services label as it appears in the VCAP_SERVICES environment variable. White space is not allowed. Important: No white space is allowed within a <service_type_specification>. The only allowed use of white space is to separate multiple <service_type_specification> instances.

Use the all option to opt out of all automatic configuration actions for a service, as in the dashDB scenario above. Use the config option to opt out of only the configuration update actions as in the cloudant scenario above.

Here are sample opt-out specifications in a manifest.yml file for the dashDB and cloudant scenarios.

env:
services_autoconfig_excludes: dashDB=all

env:
services_autoconfig_excludes: cloudant=config

env:
services_autoconfig_excludes: cloudant=config dashDB=all
* UI







 Running an evaluation for IBM Cloud 

With IBM Cloud® Security and Compliance Center, you can evaluate your resources on a recurring schedule or you can initiate a scan at any time.

To evaluate your resources, you create an attachment. An attachment is the association between the set of resources that you want to evaluate and a profile that contains the specific controls that you want to evaluate.

Zoom

![A diagram that shows the relationship between a control, profile, and scope.](https://cloud.ibm.com/docs-content/v1/content/a6478671e8f845a84102d9cf49bf28ee7f4f3227/security-compliance/images/term-flow.svg)

Figure 1. Understanding entities in Security and Compliance Center



 Before you begin 

Before you get started, be sure that you have the required level of access to create an attachment. To create an attachment, you need the Editor platform role or higher. For more information, see [Assigning access](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-access-management).

You must also connect a Cloud Object Storage bucket in which to store your results. To connect your bucket, you must have a service-to-service policy in place that enables communication between Security and Compliance Center and Cloud Object Storage.





 Scheduling a recurring scan 

To start scanning your resource, you create an attachment. To create an attachment, you can use the Security and Compliance Center UI to complete the following steps.



1. In the Security and Compliance Center UI, navigate to the Attachments page and click Create. A flat list of all of the attachments in your account is displayed.

Alternatively, you can create an attachment through the Profiles page. On the Attachments tab of the profile details page, click Create and then continue with step 2.
2. Provide a name and description for your attachment. Be sure to be as descriptive as possible so that it's easy for other members of your team to understand what is being evaluated. Then, click Next.
3.
To see and use the updated option, set the feature environment variable IBMCLOUD_IS_FEATURE_FILESHARE_CHANGE_TO_MOUNT_TARGETS to true.

export IBMCLOUD_IS_FEATURE_FILESHARE_CHANGE_TO_MOUNT_TARGETS=true





 Gathering information to create file storage from the CLI 

Before you run the ibmcloud is share-create command, you can view information about other file shares, mount targets, and file storage profiles.

Review the following information:



Table 1. Details for creating file shares.

 Details Listing options What it provides 

 File shares ibmcloud is shares List all shares in a region. 
 File share details ibmcloud is share SHARE_ID Review details of a share. 
 Mount targets ibmcloud is share-mount-targets SHARE_ID List all mount targets for a file share. 
 File share profiles ibmcloud is share-profiles List all file share profiles in a region. dp2 is recommended. 
 File share profile details ibmcloud is share-profile PROFILE_NAME List details of a file share profile. Profile names are tier-3iops, tier-5iops, tier-10iops, custom, and dp2. 







 Create a file share and mount target from the CLI 

Run the following command to create a file share and mount target. Indicate the zone in which to create the file share, [file share profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles), file share size, and optional name and user tags. Provide a mount target JSON or JSON file to create the mount target in this command.

ibmcloud is share-create
--zone ZONE_NAME
--profile PROFILE
--size SIZE
--access-control-mode value
--mount-targets value
[--name NAME]
[--initial-owner-gid INITIAL_OWNER_GID ]
[--initial-owner-uid INITIAL_OWNER_UID]
[--user-tags USER_TAGS]
[--mount-targets TARGETS_JSON | @TARGETS_JSON_FILE]