Frequently Asked Questions

550 questions found.

Page 2 / 11

When a machine is added with the 'CONTROLLER' role, it is configured as a backup controller for the server. It's important to note that only two controllers (one primary, one backup) are supported in a CAS server environment....
Read full answer See technical action

Yes, the documentation explicitly states that the addNode action is disabled in a Kubernetes environment. This means you cannot dynamically add nodes to a CAS server that is deployed within a Kubernetes cluster using this action....
Read full answer See technical action

The `addNodeStatus` action is used to list details about machines that are currently in the process of being added to the CAS server....
Read full answer See technical action

The `addNodeStatus` action is part of the Session Methods Action Set....
Read full answer See technical action

The CASL syntax for the action is: `session.addNodeStatus ;`...
Read full answer See technical action

In Python, you can call the action using the following syntax: `results=s.session.addNodeStatus()`...
Read full answer See technical action

The R syntax for the `addNodeStatus` action is: `results ...
Read full answer See technical action

The Lua syntax for this action is: `results, info = s:session_addNodeStatus{}`...
Read full answer See technical action

The addPrototypes action is used to add PROTO definitions and store them in a CAS table....
Read full answer See technical action

The required parameters for the addPrototypes action are 'funcTable' to specify the output table and 'routineCode' to provide the PROTO definition's code....
Read full answer See technical action

You can specify the output table using the 'funcTable' parameter, which is a casouttable that defines the name, caslib, and other properties of the table....
Read full answer See technical action

The 'encode' parameter, which has aliases 'encrypt' and 'hide', specifies that the prototype definitions should be encoded in the saved function table....
Read full answer See technical action

Yes, you can specify an existing FCMP library to load using the 'library' parameter....
Read full answer See technical action

The 'bridgeFile' parameter specifies the path to the PROTO bridge file source module, which can contain code to install and handle signals if 'bridgeCatchSignals' is set to TRUE....
Read full answer See technical action

The addRegion action is used to add or replace custom regions for the S3 (Simple Storage Service) environment. This allows CAS (Cloud Analytic Services) to connect to a specified server on AWS....
Read full answer See technical action

The mandatory parameters are 'host' and 'name'. The 'host' parameter specifies the server that CAS connects to on AWS, and 'name' provides a unique name for the region being added or replaced....
Read full answer See technical action

You can manage SSL/TLS settings with several boolean parameters. 'sslrequired=TRUE' enforces that all communications use SSL. 'sslallowed=TRUE' permits SSL communication but is ignored if 'sslrequired' is also set to TRUE. Conversely, 'nossl=TRUE' disables SSL/TLS for the data transfer....
Read full answer See technical action

Yes, you can use the 'port' parameter for the HTTP port (without SSL) and the 'sslport' parameter for the HTTP port with SSL. If you do not specify a value, the default is used....
Read full answer See technical action

You can use the 'region' parameter to specify the region code of the region that you are adding or replacing, such as "us-east-1"....
Read full answer See technical action

The addRoutines action adds the FCMP routines and stores them in a table....
Read full answer See technical action

The 'appendTable' parameter specifies whether to append the new functions to the FCMP table. Its default value is FALSE....
Read full answer See technical action

The 'funcTable' parameter is required and specifies the table where the FCMP function is written. It is a common casouttable parameter....
Read full answer See technical action

The 'library' parameter specifies an existing FCMP library to load....
Read full answer See technical action

The 'package' parameter specifies the FCMP package name used for storing FCMP functions....
Read full answer See technical action

The 'routineCode' parameter is required and is used to specify the FCMP routine's code that is saved to the table. It has an alias of 'code'....
Read full answer See technical action

The 'saveTable' parameter specifies if the FCMP table should be saved. Its default value is FALSE....
Read full answer See technical action

The addTable action is used to add a table by sending it from the client to the server....
Read full answer See technical action

The addTable action cannot be run directly in the same way as other actions. Each client (CASL, Python, R, etc.) provides a specific function or method to transfer data to the server, which then runs the addTable action....
Read full answer See technical action

The 'append' parameter, when set to TRUE, adds rows from the client-side table to an existing table on the server. The default value is FALSE....
Read full answer See technical action

The 'caslib' parameter specifies the target caslib where the table will be created or appended on the server....
Read full answer See technical action

When the 'replace' parameter is set to TRUE, it overwrites an existing table with the same name in the target caslib. The default value is FALSE....
Read full answer See technical action

By setting the 'promote' parameter to TRUE, the table is added with a global scope, making it accessible to other sessions, provided they have the necessary permissions. The target caslib must also have a global scope....
Read full answer See technical action

The 'copies' parameter specifies the number of redundant copies of the table's rows to create for fault tolerance. A value of 0 means no redundancy, while the default is 1....
Read full answer See technical action

Yes, 'recLen' is a required parameter. It specifies the length, in bytes, for a single row of the table being added....
Read full answer See technical action

Variables are defined using the 'vars' parameter, which is a list of objects. Each object must specify the variable's 'name', 'rType' (raw type, OBSOLETE), 'length', and 'offset' (OBSOLETE). Optional attributes include 'label', 'format', and 'type' (e.g., 'VARCHAR', 'INT64')....
Read full answer See technical action

The addUserActionSetPath action adds a caslib to the user-defined action set search path....
Read full answer See technical action

It belongs to the Builtins action set, which provides actions for server management....
Read full answer See technical action

The required parameter is 'caslib', which specifies the caslib to be added to the search path....
Read full answer See technical action

The CASL syntax is `builtins.addUserActionSetPath / caslib="string";`, where "string" is the name of the caslib....
Read full answer See technical action

The 'aggregation.aggregate' action is used to perform aggregation on selected variables within a CAS table. It computes summary statistics for these variables, optionally grouping the results by other variables....
Read full answer See technical action

The 'table' parameter is required. It specifies the input CAS table that you want to process and perform aggregations on....
Read full answer See technical action

You can use the 'varSpecs' parameter. It is a list of specifications where each element defines an aggregation. For each specification, you can set the variable name with the 'name' subparameter and the aggregation method with the 'agg' subparameter (e.g., 'SUMMARY', 'N', 'MEAN', 'MAXIMUM')....
Read full answer See technical action

Yes, you can group results by using the 'groupBy' subparameter within the main 'table' parameter. You provide a list of variable names that the action will use to group the data before performing the aggregation....
Read full answer See technical action

To perform time-based aggregation, you must specify a timestamp variable using the 'id' parameter. Then, use the 'interval' parameter to define the time period for accumulation, such as 'MONTH', 'DAY', or 'HOUR'. Parameters like 'align' and 'offset' offer further control over the time intervals....
Read full answer See technical action

By default, the action uses a sliding window. A jumping (or tumbling) window can be enabled by setting the 'jumpingWindow' parameter to TRUE. A jumping window contains multiple intervals and the aggregation is reset when the time range elapses, whereas a sliding window always retains the same number...
Read full answer See technical action

The alJoin action is used to join a data table with an annotation table. It is part of the Active Learning action set....
Read full answer See technical action

The alJoin action requires three main parameters: 'table' which specifies the primary data table, 'annotatedTable' which specifies the table containing annotation data, and 'casOut' which defines the output table for the joined results....
Read full answer See technical action

You use the 'table' parameter for the main data table (aliased as 'left') and the 'annotatedTable' parameter for the annotation data (aliased as 'right' or 'annotation')....
Read full answer See technical action

The 'id' parameter (aliased as 'idVar') specifies the identifier column that is used to join the data table and the annotation table....
Read full answer See technical action

The 'joinType' parameter allows you to specify the join method. Supported types are: APPEND, FULL, INNER, LEFT, and RIGHT. The default join type is LEFT....
Read full answer See technical action
Copyright © WeAreCAS 2023-2025