vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Example 1: Consolidate on single column

This example directs the system to examine the field Person.name of all output tuples and to use the ContainedWithin consolidation policy to resolve overlap.

consolidate on Person.name
using 'ContainedWithin'

Example 2: Consolidate on expression, involving multiple columns

This example directs the system to examine the result of applying the CombineSpans scalar function to fields Person.firstname and Person.lastname in each output tuple. It resolves overlap by using theContainedWithin consolidation policy.

consolidate on
CombineSpans(Person.firstname, Person.lastname)
using 'ContainedWithin'

Example 3: Consolidate by using LeftToRight policy and priority order

Suppose that the following Term tuples are extracted from the input text John Doe:

match: John,
priority: 1

and

match: John Doe,
priority: 2

Both spans have the same begin offset. When you consolidate by using the LeftToRight policy for ascending priority order, the tuple (match: John, priority: 1) is retained because it has the higher priority. When you consolidate by using the descending priority order, the tuple (match: John Doe, priority: 2) is retained, as in the following example:

create view ConsolidatePeopleWithPrioritiesAscending as
select P.match as match, P.weight as weight
from People P
consolidate on P.match
using 'LeftToRight'
with priority from P.weight
ascending;







 The group by clause 

The optional group by clause of a select statement directs the runtime component to group tuples that are produced from the same document by common values of a specified field.



 Syntax 

select <select list>
from <from list>
[where <where clause>]
...
[group by <group by list>]





 Description 



* <group by list>

Specifies a comma-delimited list of expressions that involves columns of the views in the from clause and scalar function calls. When you apply the group by clause, each group of tuples that shares common values for all group by expressions produces a single output tuple that is representative for the entire group.
create function udfSpanGreaterThan(span Span, size Integer)
return Boolean
external_name 'udfjars/udfs.jar:com.ibm.test.udfs.MiscScalarFunc!spanGreaterThan'
language java
deterministic;

-- identify occurrences of given names in the document
create dictionary FirstNamesDict from file 'firstNames.dict';

create view FirstName as
extract dictionary 'FirstNamesDict' on D.text as name
from Document D;

-- Use a UDF to merge the name that is longer than 7 characters with the text to its right in a
-- way that is appropriate to the application.
create view NameAndContext as
select udfCombineSpans(F.name, RightContext(F.name, 50)) as name
from FirstName F
where udfSpanGreaterThan(F.name, 7);
Show more

Example 2: Using Scalar UDFs implemented in Java with tables as input

The following example shows how to use a scalar function that uses tables as input. This example illustrates the usage of the MyScalarFunc table UDF function, whose Java™ implementation is included in [Implementing user-defined functions](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-annotation-query-language-referenceaql-user-def-imp). They are the same column types, but have different column names.

-- Declare a simple scalar function that turns two tables into a big string
create function MyScalarFunc(
firstArg table( spanVal Span ) as locator,
secondArg table( spanVal Span, strVal Text ) as locator
)
return String
external_name
'udfjars/udfs.jar:com.ibm.test.udfs.TableConsumingScalarFunc!eval'
language java
deterministic
called on null input;

-- Create two views to serve as inputs to the table function.
In this scenario, the command requires the npm command to be available.
* If the path contains the Python requirements.txt file, the command uses pip to generate the package dependencies. In this scenario, the bom-generatecommand requires the pip command to be available. Both Python version 2 and Python version 3 are supported.



If you are using Dockerfiles, make sure to log in to your container registry from where the base images are to be pulled.

If your Dockerfile requires ARGS, set an individual ARG as an environment variable before you run the command. For example, if the Dockerfile is using an IAM_USER ARG, export an environment variable that is named IAM_USER: export IAM_USER='value'. The CLI automatically passes these environment variables to the docker build command.

You can also specify the DOCKERBUILDFLAGS flag explicitly. To export DOCKERBUILDFLAGS with the ARGS Docker flag, type the following command:

export DOCKERBUILDFLAGS="--build-arg IAM_USER --build-arg API_KEY"





 BOM command options 

The following table lists the command options that you can use to generate a BOM file with the bom-generate command.



Table 2. Command options for generating a BOM file

 Command options Required or optional Description 

 --path Required The project directory path to scan. 
 -r, --report Required The file name in which to store the BOM report. 
 -a, --asset-type Optional The security checks to run (apps, image, os, all). By default, this option is set to all. The apps option is used to limit discovery to application packages. The image option is used to limit discovery to base images that are used in Dockerfiles. The os option is used to limit discovery to build stages in Dockerfiles only. You can specify multiple values by using a comma to delimit the values, such as -a os,image,apps. 
 -p, --prev-report Optional Use the previous BOM report to speed up the command.
measure","type":"measure"},"m7":{"operates":{"qubits":[7]},"purpose":"measure","type":"measure"},"m8":{"operates":{"qubits":[8]},"purpose":"measure","type":"measure"},"m9":{"operates":{"qubits":[9]},"purpose":"measure","type":"measure"},"u0":{"operates":{"qubits":[0,1]},"purpose":"cross-resonance","type":"control"},"u1":{"operates":{"qubits":[1,0]},"purpose":"cross-resonance","type":"control"},"u10":{"operates":{"qubits":[5,3]},"purpose":"cross-resonance","type":"control"},"u11":{"operates":{"qubits":[5,8]},"purpose":"cross-resonance","type":"control"},"u12":{"operates":{"qubits":[6,7]},"purpose":"cross-resonance","type":"control"},"u13":{"operates":{"qubits":[7,4]},"purpose":"cross-resonance","type":"control"},"u14":{"operates":{"qubits":[7,6]},"purpose":"cross-resonance","type":"control"},"u15":{"operates":{"qubits":[7,10]},"purpose
* By using the --rules option information is passed as JSON directly on the command.
* By using the --files option information is passed as a JSON file.





 Example that uses the --rules option 

The following example specifies rules directly on the --rules option. In this example, all metrics from us-east are routed to 11111111-1111-1111-1111-1111111111111. All metrics from appconnect, cloudant, and containers-kupernetes are routed to 22222222-2222-2222-2222-222222222222 and 33333333-3333-3333-3333-3333333333333.

[{"action": "send", "targets":{"id":"11111111-1111-1111-1111-1111111111111"}], "inclusion_filters":{"operand": "location","operator": "is","values": "us-east"]}]},{"targets":{"id":"22222222-2222-2222-2222-222222222222"},{"id":"33333333-3333-3333-3333-3333333333333"}], "inclusion_filters":{"operand": "service_name","operator": "in","values": "appconnect","cloudant","containers-kubernetes"]}]}]'





 Example that uses the --file option 

The following example specifies rules by passing a JSON file that is named rules_def.json on the --file option:

--file rules_def.json

The rules_def.json file contains:

[
{
"action":"send",
"targets":
{
"id":"11111111-1111-1111-1111-111111111111"
},
{
* [Additional IBM Cloud for Financial Services specifications](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-15additional-ibm-cloud-for-financial-services-specifications)
* [Implementation guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-15implementation-guidance)
* [IBM Cloud for Financial Services profile](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-15scc-fs-cloud-profile)
* [NIST supplemental guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-15nist-supplemental-guidance)



[SA-15 (9) - Use of Live Data](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-15.9sa-15.9)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-15.9control-requirements)
* [Additional IBM Cloud for Financial Services specifications](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-15.9additional-ibm-cloud-for-financial-services-specifications)
* [Implementation guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-15.9implementation-guidance)
* [NIST supplemental guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-15.9nist-supplemental-guidance)







 System and Communications Protection (SC)
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 
 sysdig-monitor.explore.edit Modify the Explore view. ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 
 sysdig-monitor.explore.read Use the Explore view. ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) !
* If the information you want to capture follows strict formatting rules, you can use the Regular expression enrichment to find it. Apply the enrichment, and then you can use the resulting field as the source for the facet.
* If the information you want to capture can occur in different formatting styles, the pattern facet is a better choice. For example, dates or currencies can be formatted in various ways. No single regex rule can capture all of the variations. With the pattern facet, you can provide multiple real-world examples that show the different ways in which the information can be specified.
Understanding your responsibilities when you use DevSecOps Application Lifecycle Management deployable architecture 

Learn about the management responsibilities and terms and conditions that you have when you use the DevSecOps Application Lifecycle Management deployable architecture.



*  For more information about the responsibilities for you and for IBM when you use a deployable architecture, see [Understanding your responsibilities when using deployable architectures](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-responsibilities-deployable-architectures).
*  For a high-level view of the service types in IBM Cloud® and the breakdown of responsibilities between the customer and IBM for each type, see [Shared responsibilities for using IBM Cloud products](https://cloud.ibm.com/docs/overview?topic=overview-shared-responsibilities).
*  For the overall terms of use, see [IBM Cloud® Terms and Notices](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-terms).
^{X} + \Omega_{d,23}(U_{49}^{(23,24)}(t)+U_{48}^{(23,21)}(t))\sigma_{23}^{X} \\ u0026 + \Omega_{d,24}(U_{50}^{(24,23)}(t)+U_{51}^{(24,25)}(t))\sigma_{24}^{X} + \Omega_{d,25}(U_{54}^{(25,26)}(t)+U_{53}^{(25,24)}(t)+U_{52}^{(25,22)}(t))\sigma_{25}^{X} \\ u0026 + \Omega_{d,26}(U_{55}^{(26,25)}(t))\sigma_{26}^{X} \\ \end{align}","h_str":["_SUMi,0,26,wq{i}/
When the optional alias is not specified, the view is output under the following names:



* In modular AQL, the view is output under the name <module-name>.<view-name> where <module-name> is the name of the module where the view is originally defined (which can be different from the module where the view is output).
* In AQL 1.4 or earlier, the view is output under the name <view-name> The output ... as <alias> statement is useful when you customize an extractor for different domains. The use of the <alias> name when you define an output view ensures that output names are identical across different implementations of the customization.



The <alias> name cannot be used in another select or export statement. You must enclose the <alias> with single quotation marks, and the <alias> name can contain periods.







 Usage notes 



* When an AQL extractor is run, it computes resultant tuples for each view that is defined as an output view. The tuples of any non-output view are also computed, but only when they are necessary to compute the resultant tuples of an output view.
* In modular AQL, the output view statement outputs the tuples of the view under the fully qualified view name that is qualified by its module name. Consider the following example where the statement output view Person; results in the output of the personModule.Person view:



module personModule;

create view Person as
extract dictionary 'FamousPeopleDict' on D.text as match
from Document D;

output view Person;

This behavior applies for any view output without an alias, regardless of whether the view is output in the module where it is defined, or a module where it is imported, even when it is imported by using an alias import. For example, in the output view MyPerson, this example results in the view being output under its original qualified name personModule.Person and not under its local alias MyPerson

module employeeModule;

import view Person from module personModule as MyPerson;

output view MyPerson;
Understanding your responsibilities when you use Power Virtual Server with VPC landing zone deployable architecture 

Learn about the management responsibilities and terms and conditions that you have when you use the Power Virtual Server with VPC landing zone deployable architecture.



*  For more information about the responsibilities for you and for IBM® when you use a deployable architecture, see [Understanding your responsibilities when you use deployable architectures](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-responsibilities-deployable-architectures).
*  For a high-level view of the service types in IBM Cloud® and the breakdown of responsibilities between the customer and IBM for each type, see [Shared responsibilities for using IBM Cloud products](https://cloud.ibm.com/docs/overview?topic=overview-shared-responsibilities).
*  For the overall terms of use, see [IBM Cloud® Terms and Notices](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-terms).



Review the following section for the specific responsibilities for you and for IBM when you use the Power Virtual Server with VPC landing zone deployable architecture.



  Security and regulation compliance 

Security and regulation compliance includes tasks such as security controls implementation and compliance certification.



Table 1. Security and compliance responsibilities for provisioned components

 Task                                                                           IBM responsibility                                                                                                                                                                                                                                                                                                       Your responsibility                                                                          

 Ensure that the operating system image does not contain any vulnerabilities.   IBM Cloud provided and verified RHEL and SLES operating system images are used. After deployment, operating system images are updated to the newest state in the defined minor release. Official RHEL and SLES software repositories are used for installation of additional software components (like SQUID proxy).     Customer is responsible to keep the operating system secure and compliant after deployment.
The URL to the license is [https://creativecommons.org/licenses/by-sa/1.0/legalcode](https://creativecommons.org/licenses/by-sa/1.0/legalcode)

NORMALIZE_TEST.GO [x/text](https://github.com/golang/text/tree/22f1617af38ed)





 Creative Commons Attribution Share Alike 2.0 license 

The Program includes some or all of the following that IBM obtained under the Creative Commons Attribute Share-Alike 2.0 License. The URL to the license is [https://creativecommons.org/licenses/by-sa/2.0/legalcode](https://creativecommons.org/licenses/by-sa/2.0/legalcode)

go-digest docs ([https://github.com/opencontainers/go-digest/tree/279bed98673dd5bef374d3b6e4b09e2af76183bf](https://github.com/opencontainers/go-digest/tree/279bed98673dd5bef374d3b6e4b09e2af76183bf)), mapstruct documentation ( [https://github.com/mapstruct/mapstruct/tree/1.2.0.Final](https://github.com/mapstruct/mapstruct/tree/1.2.0.Final)), NORMALIZE_TEST.GO [x/text](https://github.com/golang/text/tree/22f1617af38ed)





 Creative Commons Attribution Share Alike 2.5 Generic 

The Program includes some or all of the following works licensed under the Creative Commons. The URL to the license is [https://creativecommons.org/licenses/by-sa/2.5/legalcode](https://creativecommons.org/licenses/by-sa/2.5/legalcode)
--service-instance SERVICE_INSTANCE_GUID (optional)
: GUID of service instance of the policy definition. This option is exclusive with the --file option.

--region REGION (optional)
: Region of the policy definition. This option is exclusive with the --file option.

--resource-type RESOURCE_TYPE (optional)
: Resource type of the policy definition. This option is exclusive with the --file option.

--resource RESOURCE (optional)
: Resource of the policy definition. This option is exclusive with the --file option.

--resource-group-name RESOURCE_GROUP_NAME (optional)
: Name of the resource group. * means all resource groups. This option is exclusive with the --file, --resource and --resource-group-id options.

--resource-group-id RESOURCE_GROUP_ID (optional)
: ID of the resource group. * means all resource groups. This option is exclusive with the --file, --resource and --resource-group-name options.

--account-management (optional)
: Give access to all account management services.

--attributes name=value,name=value...
: Set resource attributes in the form of 'name=value,name=value....'

--output FORMAT
: Specify output format. Only 'JSON' is supported.

-q, --quiet
: Suppress verbose output.

--api-version
: Version of the access policy API.





 Examples 

Update user policy with the one in JSON file：

ibmcloud iam user-policy-update name@example.com 0bb730daa --file @policy.json

Update user policy to give name@example.comAdministrator role for all instances of sample-service service：

ibmcloud iam user-policy-update name@example.com user-policy-id --roles Administrator --service-name sample-service

Update user policy to give name@example.comEditor role and a custom role Responder for all instances of sample-service service：
('John', 'Peter', 'Andrew', 'Francis', 'Mary', 'Juliet');

create view PersonNameEnglish as
extract dictionary 'EnglishNames'
on D.text as name
from Document D;

output view PersonNameEnglish as 'PersonName';

The consumer of the example modules can access the output tuples through the alias name 'PersonName'. The consumer would not need to know the actual module from which the results are fetched.







 The extract statement 

The extract statement is used to extract basic features directly from text.



 Syntax 

extract <select list>,
<extraction specification>
from <from list>
[having <having clause>]
[consolidate on <column> using '<policy>']]
[limit <maximum number of output tuples for each document>];





 Description 



* <select list>

A comma-delimited list of output expressions. The results of these output expressions are returned as the output of the extract statement, along with the tuples that are generated by the evaluation of the extraction specification. The format for the <select list> is the same as the <select list> of a select statement.
* <extraction specification>

Applies the extraction specification over all tuples from the views that are defined in the <from list>. It renames the columns of tuples according to their corresponding aliases that are specified in the extract statement. You can use one of the following extraction specifications:



* Regular expressions
* Dictionaries
* Splits
* Blocks
* Part of speech
* Sequence patterns



* <from list>

A comma-delimited list that is the source of the tuples from which features are to be selected. The format of the <from list> is similar to the format of the <from list> of the select statement. However, if the extract statement does not have a pattern specification, then the <from list> can contain a single item.
* [having <having clause>]

Specifies a filtering predicate (in the <having clause>) that is applied to each extracted output tuple.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

UNIQUE

These are the packages covered under this license:

Floating point exception control (The Regents of the University of California)

---------------------------------------------------------------------
/ Copyright (c) 1996. 
 The Regents of the University of California. 
 All rights reserved. 

 Permission to use, copy, modify, and distribute this software for 
 any purpose without fee is hereby granted, provided that this en- 
 tire notice is included in all copies of any software which is or 
 includes a copy or modification of this software and in all 
 copies of the supporting documentation for such software. 

 This work was produced at the University of California, Lawrence 
 Livermore National Laboratory under contract no. W-7405-ENG-48 
 between the U.S. Department of Energy and The Regents of the 
 University of California for the operation of UC LLNL. 

 DISCLAIMER 

 This software was prepared as an account of work sponsored by an 
 agency of the United States Government. Neither the United States 
 Government nor the University of California nor any of their em- 
 ployees, makes any warranty, express or implied, or assumes any 
 liability or responsibility for the accuracy, completeness, or 
 usefulness of any information, apparatus, product, or process 
 disclosed, or represents that its use would not infringe 
 privately-owned rights. Reference herein to any specific commer- 
 cial products, process, or service by trade name, trademark, 
 manufacturer, or otherwise, does not necessarily constitute or 
 imply its endorsement, recommendation, or favoring by the United 
 States Government or the University of California.
The URL to the license is [https://creativecommons.org/licenses/by-sa/2.5/legalcode](https://creativecommons.org/licenses/by-sa/2.5/legalcode)

CANTONESE TEXT [golang.org/x/text](https://proxy.golang.org/golang.org/x/text/@v/v0.3.3-0.20200430171850-afb9336c4530.zip), MAP_TEST.GO [x/text]





 Creative Commons Attribution Share Alike 3.0 Generic 

The Program includes some or all of the following works licensed under the Creative Commons. The URL to the license is [https://creativecommons.org/licenses/by-sa/3.0/legalcode](https://creativecommons.org/licenses/by-sa/3.0/legalcode)