CData Cloud offers access to Redis across several standard services and protocols, in a cloud-hosted solution. Any application that can connect to a MySQL or SQL Server database can connect to Redis through CData Cloud.
CData Cloud allows you to standardize and configure connections to Redis as though it were any other OData endpoint, or standard SQL Server/MySQL database.
This page provides a guide to Establishing a Connection to Redis in CData Cloud, as well as information on the available resources, and a reference to the available connection properties.
Establishing a Connection shows how to authenticate to Redis and configure any necessary connection properties to create a database in CData Cloud
Accessing data from Redis through the available standard services and CData Cloud administration is documented in further details in the CData Cloud Documentation.
Connect to Redis by selecting the corresponding icon in the Database tab. Required properties are listed under Settings. The Advanced tab lists connection properties that are not typically required.
Set the Server connection property to the name or address of the server your Redis instance is running on.
If your Redis server is running on a port other than the default (6379), you can specify your port in the Port property.
The Cloud supports Password and ACL authentication. Connections to Redis instances that aren't password protected are supported as well.
Set the AuthScheme property to None. This indicates the Redis instance is not password protected (using the requirepass directive in the configuration file).
Set the AuthScheme property to Password and set the Password property to the password used to authenticate with a password protected Redis instance using the Redis AUTH command.
Set the following to connect:
You can set UseSSL to negotiate SSL/TLS encryption when you connect.
The Cloud enables you to model Redis key-value pairs as tables.
The Cloud enables two major paradigms for modeling Redis key-value pairs as tables.
Redis key patterns can be modeled as tables. See Freeform Querying of Redis Keys for a breakdown of the different configuration options.
It is also possible to query keys directly as if they are tables.
If you would like to query specific keys as tables, see Modeling Redis Hashes as Tables.
If you would like to query all keys in the Redis keystore from a single table, see the Keys table.
See Redis Data Types for a list of the Redis data types supported by the Cloud.
Use the available Stored Procedures to submit commands (in native redis-cli syntax) to the Redis server for direct execution.
The Cloud can be configured to shape the discovered metadata.
Use the DefineTables, TablePattern, and PatternSeparator connection properties to customize how tables and columns are inferred from the Redis key store.
Presume the following hashes have been created in the Redis server (either with redis-cli or the RunCommand storec procedure).
> hmset user:1000 name "John Smith" email "[email protected]" password "s3cret" OK > hmset user:1001 name "Mary Jones" email "[email protected]" password "hidden" OK > hmset user:1002 name "Sally Brown" email "[email protected]" password "p4ssw0rd" OK > hmset customer:200 name "John Smith" account "123456" balance "543.21" OK > hmset customer:201 name "Mary Jones" account "123457" balance "654.32" OK > hmset customer:202 name "Sally Brown" account "123458" balance "765.43" OK
When these properties are used to define the Cloud's behavior, the Redis keys will be pivoted, so that each Redis key that matches the pattern in the definition is represented as a single row in the table. Each value associated with that Redis key becomes a column for the table.
The DefineTables connection property allows you to explicitly define the names of the tables that will appear. To do so, set the property to a comma-separated string of name-value pairs, where the name is the name of the table and the value is the pattern used to assign Redis keys to that table.
The Cloud aggregates all of the Redis keys that match the specified patterns.
DefineTables=Users=user:*,Customers=customer:*;
With the property set as above, the Users and Customers tables will be exposed. If you were to query the tables, you would see the following results:
RedisKey | name | password | |
user:1000 | John Smith | [email protected] | s3cret |
user:1001 | Mary Jones | [email protected] | hidden |
user:1002 | Sally Brown | sally.b@example | p4ssw0rd |
RedisKey | name | account | balance |
customer:200 | John Smith | 123456 | 543.21 |
customer:201 | Mary Jones | 123456 | 654.32 |
customer:202 | Sally Brown | 123456 | 765.43 |
The TablePattern connection property allows you to define the separator(s) that determine how the Cloud defines tables. For the Redis keys described above, "user" and "customer" would be defined as tables if the separator is set to ":" since the unique piece of each Redis key appears after the ":". If you have a need to structure the tables differently, to drill down further, you can include multiple instances of the separator. Set the property to a pattern that includes the separator(s) needed to define your table structure. (Below is the default value.)
You can also manually specify the pattern separator indepently from the TablePattern using the PatternSeparator property.
TablePattern=*:*;
With the property set as above, the user and customer tables will be exposed. If you were to query the tables, you would see the following results:
RedisKey | name | password | |
user:1000 | John Smith | [email protected] | s3cret |
user:1001 | Mary Jones | [email protected] | hidden |
user:1002 | Sally Brown | sally.b@example | p4ssw0rd |
RedisKey | name | account | balance |
customer:200 | John Smith | 123456 | 543.21 |
customer:201 | Mary Jones | 123456 | 654.32 |
customer:202 | Sally Brown | 123456 | 765.43 |
The most direct way to work with Redis data with the Cloud is to use a Redis key as a table name. Below you will find sample data, queries, and results based on Redis data types.
Note: This page contains redis-cli syntax. Use either your own instance of redis-cli or the RunCommand procedure to send queries from the Cloud to the Redis server for direct execution.
Create a string in Redis:
> set mykey somevalue OKIf you perform a SELECT query on mykey the Cloud will return the following:
RedisKey | ValueIndex | Value | RedisType | ValueScore |
mykey | 1 | somevalue | String | NULL |
Create a list in Redis:
> rpush mylist A B C (integer) 3If you perform a SELECT query on mylist the Cloud will return the following:
RedisKey | ValueIndex | Value | RedisType | ValueScore |
mylist | 1 | A | List | NULL |
mylist | 2 | B | List | NULL |
mylist | 3 | C | List | NULL |
DELETE FROM Keys WHERE Value = 'myvalue' AND RedisKey = 'mylist'
Note that using ValueIndex in the WHERE clause of the DELETE statement is not supported.
Create a set in Redis:
> sadd myset 1 2 3 (integer) 3If you perform a SELECT query on myset the Cloud will return the following (note that Redis can return the elements of a set in any order):
RedisKey | ValueIndex | Value | RedisType | ValueScore |
myset | 1 | 2 | Set | NULL |
myset | 2 | 1 | Set | NULL |
myset | 3 | 3 | Set | NULL |
Create a ZSet (sorted set) in Redis:
> zadd hackers 1940 "Alan Kay" 1957 "Sophie Wilson" 1953 "Richard Stallman" 1949 "Anita Borg" (integer) 9If you perform a SELECT query on hackers the Cloud will return the following:
RedisKey | ValueIndex | Value | RedisType | ValueScore |
hackers | 1 | Alan Kay | ZSet | 1940 |
hackers | 2 | Anita Borg | ZSet | 1949 |
hackers | 3 | Richard Stallman | ZSet | 1953 |
hackers | 4 | Sophie Wilson | ZSet | 1957 |
Create a hash in Redis:
> hmset user:1000 username antirez birthyear 1977 verified 1 OKIf you perform a SELECT query on user:1000 the Cloud will return the following:
RedisKey | ValueIndex | Value | RedisType | ValueScore |
user:1000 | username | antirez | Hash | NULL |
user:1000 | birthyear | 1977 | Hash | NULL |
user:1000 | verified | 1 | Hash | NULL |
You can retrieve multiple Redis keys at once by using a pattern (e.g., "user:*") as a table name. For example, start by adding several keys to Redis that match a pattern:
> hmset user:1000 name "John Smith" email "[email protected]" password "s3cret" OK > hmset user:1001 name "Mary Jones" password "hidden" email "[email protected]" OK
If you use user:* as the table name, the Cloud will retrieve all Redis key-value pairs whose keys match the pattern. You can see the expected results below:
RedisKey | ValueIndex | Value | RedisType | ValueScore |
user:1000 | name | John Smith | Hash | NULL |
user:1000 | [email protected] | Hash | NULL | |
user:1000 | password | s3cret | Hash | NULL |
user:1001 | name | Mary Jones | Hash | NULL |
user:1001 | [email protected] | Hash | NULL | |
user:1001 | password | hidden | Hash | NULL |
The Cloud models the data in Redis as a list of tables in a relational database that can be queried using standard SQL statements.
Name | Description |
Keys | Returns keys present in the Redis store. |
Returns keys present in the Redis store.
This table allows you to query all Redis keys in one place. It models Redis key metadata in exactly the same way as described in Freeform Querying of Redis Keys.
Name | Type | ReadOnly | Description |
RedisKey [KEY] | String | True |
The name of the Redis key. |
ValueIndex | String | True |
Varies by type: 1 for strings; the one-based index for sets, lists, and sorted sets; or the associated field name for hashes. |
Value | String | True |
The value associated with the Redis key. |
RedisType | String | True |
The type associated with the Redis key. |
ValueScore | Double | True |
NULL for strings, lists, sets, and hashes. Returns the associated score for sorted sets. |
Stored procedures are function-like interfaces that extend the functionality of the Cloud beyond simple SELECT/INSERT/UPDATE/DELETE operations with Redis.
Stored procedures accept a list of parameters, perform their intended function, and then return any relevant response data from Redis, along with an indication of whether the procedure succeeded or failed.
Name | Description |
RunBatchCommand | Sequentially executes a batch of Redis commands using either a temporary table or a batch file. |
RunCommand | Passes a command to the Redis server for direct execution. Use standard redis-cli syntax. |
Sequentially executes a batch of Redis commands using either a temporary table or a batch file.
Batch commands are much more efficient because the Cloud does not need to send and wait for single commands to complete. Instead, the Cloud will send several commands and wait for them as a group.
Create a text document and populate it with one Redis command per line without any delimiters. Empty lines are skipped.
For example:
set key1 value1 set key2 value2 set key3 value3
Then, invoke the procedure with the path to the file supplied in the CommandFile input.
EXECUTE RunBatchCommand CommandFile = "C:\\Users\\username\\Public Documents\\batchfile.txt"
Populate a temporary table with Redis commands.
INSERT INTO Commands#TEMP (CommandLine) VALUES ("rpush mylist value1") INSERT INTO Commands#TEMP (CommandLine) VALUES ("rpush mylist value2") INSERT INTO Commands#TEMP (CommandLine) VALUES ("rpush mylist value3")
Then, invoke the procedure with the name of the temporary table provided in the CommandTable input.
EXECUTE RunBatchCommand CommandTable = "Commands#TEMP"
Name | Type | Required | Description |
CommandTable | String | False | Specifies a temporary table to be used in generating a batch of Redis commands for direct execution on the Redis server. |
CommandFile | String | False | The path to a file containing a batch of Redis commands. These commands will be sequentially and directly executed on the Redis server. |
KeyType | String | False | The format for the Redis server output. 'AUTO' returns the keys in list format (nested lists will each be one compound result). 'HASH' returns the keys as a hash (each group is a row, each property gets its own column).
The allowed values are AUTO, HASH. The default value is AUTO. |
Name | Type | Description |
* | String | Output will vary for each collection. |
Passes a command to the Redis server for direct execution. Use standard redis-cli syntax.
You can use this procedure to run a command directly that isn't exposed by the usual CRUD operations on tables. For example, the FLUSHDB command removes all keys from the current database:
EXECUTE RunCommand @CommandLine = 'FLUSHDB'
You can also run commands which require parameters by separating them with spaces, the same as in redis-cli. Double-quotes are also available if you need to embed spaces into a parameter value:
EXECUTE RunCommand @CommandLine = 'INFO "CPU"'
The Cloud will process the results of the command and return them in the appropriate format. For cases like FLUSHDB or INFO where the result is a simple value or a flat array, each element will be returned as a separate row.
'# CPU' 'used_cpu_sys:1272.08' 'used_cpu_user:537.84' 'used_cpu_sys_children:4.81' 'used_cpu_user_children:98.89'
More complex results, like the values returned from the COMMAND command, will be separated by row and then converted to JSON for final output.
'["slowlog","-2",[["admin"]],"0","0","0"]' '["persist","2",[["write","fast"]],"1","1","1"]' '["zrevrangebylex","-4",[["readonly"]],"1","1","1"]' '["sinter","-2",[["readonly","sort_for_script"]],"1","-1","1"]' '["lrange","4",[["readonly"]],"1","1","1"]' '["hmset","-4",[["write","denyoom","fast"]],"1","1","1"]' '["lpush","-3",[["write","denyoom","fast"]],"1","1","1"]' '["zremrangebyscore","4",[["write"]],"1","1","1"]' '["FT.DICTDEL","-1",[["readonly"]],"1","1","1"]' ...
Name | Type | Required | Description |
CommandLine | String | False | The command to pass directly to the Redis server for execution. |
KeyType | String | False | The format for the Redis server output. 'AUTO' returns the keys in list format (nested lists will each be one compound result). 'HASH' returns the keys as a hash (each group is a row, each property gets its own column).
The allowed values are AUTO, HASH. The default value is AUTO. |
Name | Type | Description |
* | String | Output will vary for each collection. |
You can query the system tables described in this section to access schema information, information on data source functionality, and batch operation statistics.
The following tables return database metadata for Redis:
The following tables return information about how to connect to and query the data source:
The following table returns query statistics for data modification queries, including batch operations::
Lists the available databases.
The following query retrieves all databases determined by the connection string:
SELECT * FROM sys_catalogs
Name | Type | Description |
CatalogName | String | The database name. |
Lists the available schemas.
The following query retrieves all available schemas:
SELECT * FROM sys_schemas
Name | Type | Description |
CatalogName | String | The database name. |
SchemaName | String | The schema name. |
Lists the available tables.
The following query retrieves the available tables and views:
SELECT * FROM sys_tables
Name | Type | Description |
CatalogName | String | The database containing the table or view. |
SchemaName | String | The schema containing the table or view. |
TableName | String | The name of the table or view. |
TableType | String | The table type (table or view). |
Description | String | A description of the table or view. |
IsUpdateable | Boolean | Whether the table can be updated. |
Describes the columns of the available tables and views.
The following query returns the columns and data types for the Customers table:
SELECT ColumnName, DataTypeName FROM sys_tablecolumns WHERE TableName='Customers'
Name | Type | Description |
CatalogName | String | The name of the database containing the table or view. |
SchemaName | String | The schema containing the table or view. |
TableName | String | The name of the table or view containing the column. |
ColumnName | String | The column name. |
DataTypeName | String | The data type name. |
DataType | Int32 | An integer indicating the data type. This value is determined at run time based on the environment. |
Length | Int32 | The storage size of the column. |
DisplaySize | Int32 | The designated column's normal maximum width in characters. |
NumericPrecision | Int32 | The maximum number of digits in numeric data. The column length in characters for character and date-time data. |
NumericScale | Int32 | The column scale or number of digits to the right of the decimal point. |
IsNullable | Boolean | Whether the column can contain null. |
Description | String | A brief description of the column. |
Ordinal | Int32 | The sequence number of the column. |
IsAutoIncrement | String | Whether the column value is assigned in fixed increments. |
IsGeneratedColumn | String | Whether the column is generated. |
IsHidden | Boolean | Whether the column is hidden. |
IsArray | Boolean | Whether the column is an array. |
IsReadOnly | Boolean | Whether the column is read-only. |
IsKey | Boolean | Indicates whether a field returned from sys_tablecolumns is the primary key of the table. |
Lists the available stored procedures.
The following query retrieves the available stored procedures:
SELECT * FROM sys_procedures
Name | Type | Description |
CatalogName | String | The database containing the stored procedure. |
SchemaName | String | The schema containing the stored procedure. |
ProcedureName | String | The name of the stored procedure. |
Description | String | A description of the stored procedure. |
ProcedureType | String | The type of the procedure, such as PROCEDURE or FUNCTION. |
Describes stored procedure parameters.
The following query returns information about all of the input parameters for the SelectEntries stored procedure:
SELECT * FROM sys_procedureparameters WHERE ProcedureName='SelectEntries' AND Direction=1 OR Direction=2
Name | Type | Description |
CatalogName | String | The name of the database containing the stored procedure. |
SchemaName | String | The name of the schema containing the stored procedure. |
ProcedureName | String | The name of the stored procedure containing the parameter. |
ColumnName | String | The name of the stored procedure parameter. |
Direction | Int32 | An integer corresponding to the type of the parameter: input (1), input/output (2), or output(4). input/output type parameters can be both input and output parameters. |
DataTypeName | String | The name of the data type. |
DataType | Int32 | An integer indicating the data type. This value is determined at run time based on the environment. |
Length | Int32 | The number of characters allowed for character data. The number of digits allowed for numeric data. |
NumericPrecision | Int32 | The maximum precision for numeric data. The column length in characters for character and date-time data. |
NumericScale | Int32 | The number of digits to the right of the decimal point in numeric data. |
IsNullable | Boolean | Whether the parameter can contain null. |
IsRequired | Boolean | Whether the parameter is required for execution of the procedure. |
IsArray | Boolean | Whether the parameter is an array. |
Description | String | The description of the parameter. |
Ordinal | Int32 | The index of the parameter. |
Describes the primary and foreign keys.
The following query retrieves the primary key for the Customers table:
SELECT * FROM sys_keycolumns WHERE IsKey='True' AND TableName='Customers'
Name | Type | Description |
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
IsKey | Boolean | Whether the column is a primary key in the table referenced in the TableName field. |
IsForeignKey | Boolean | Whether the column is a foreign key referenced in the TableName field. |
PrimaryKeyName | String | The name of the primary key. |
ForeignKeyName | String | The name of the foreign key. |
ReferencedCatalogName | String | The database containing the primary key. |
ReferencedSchemaName | String | The schema containing the primary key. |
ReferencedTableName | String | The table containing the primary key. |
ReferencedColumnName | String | The column name of the primary key. |
Describes the foreign keys.
The following query retrieves all foreign keys which refer to other tables:
SELECT * FROM sys_foreignkeys WHERE ForeignKeyType = 'FOREIGNKEY_TYPE_IMPORT'
Name | Type | Description |
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
PrimaryKeyName | String | The name of the primary key. |
ForeignKeyName | String | The name of the foreign key. |
ReferencedCatalogName | String | The database containing the primary key. |
ReferencedSchemaName | String | The schema containing the primary key. |
ReferencedTableName | String | The table containing the primary key. |
ReferencedColumnName | String | The column name of the primary key. |
ForeignKeyType | String | Designates whether the foreign key is an import (points to other tables) or export (referenced from other tables) key. |
Describes the primary keys.
The following query retrieves the primary keys from all tables and views:
SELECT * FROM sys_primarykeys
Name | Type | Description |
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
KeySeq | String | The sequence number of the primary key. |
KeyName | String | The name of the primary key. |
Describes the available indexes. By filtering on indexes, you can write more selective queries with faster query response times.
The following query retrieves all indexes that are not primary keys:
SELECT * FROM sys_indexes WHERE IsPrimary='false'
Name | Type | Description |
CatalogName | String | The name of the database containing the index. |
SchemaName | String | The name of the schema containing the index. |
TableName | String | The name of the table containing the index. |
IndexName | String | The index name. |
ColumnName | String | The name of the column associated with the index. |
IsUnique | Boolean | True if the index is unique. False otherwise. |
IsPrimary | Boolean | True if the index is a primary key. False otherwise. |
Type | Int16 | An integer value corresponding to the index type: statistic (0), clustered (1), hashed (2), or other (3). |
SortOrder | String | The sort order: A for ascending or D for descending. |
OrdinalPosition | Int16 | The sequence number of the column in the index. |
Returns information on the available connection properties and those set in the connection string.
When querying this table, the config connection string should be used:
jdbc:cdata:redis:config:
This connection string enables you to query this table without a valid connection.
The following query retrieves all connection properties that have been set in the connection string or set through a default value:
SELECT * FROM sys_connection_props WHERE Value <> ''
Name | Type | Description |
Name | String | The name of the connection property. |
ShortDescription | String | A brief description. |
Type | String | The data type of the connection property. |
Default | String | The default value if one is not explicitly set. |
Values | String | A comma-separated list of possible values. A validation error is thrown if another value is specified. |
Value | String | The value you set or a preconfigured default. |
Required | Boolean | Whether the property is required to connect. |
Category | String | The category of the connection property. |
IsSessionProperty | String | Whether the property is a session property, used to save information about the current connection. |
Sensitivity | String | The sensitivity level of the property. This informs whether the property is obfuscated in logging and authentication forms. |
PropertyName | String | A camel-cased truncated form of the connection property name. |
Ordinal | Int32 | The index of the parameter. |
CatOrdinal | Int32 | The index of the parameter category. |
Hierarchy | String | Shows dependent properties associated that need to be set alongside this one. |
Visible | Boolean | Informs whether the property is visible in the connection UI. |
ETC | String | Various miscellaneous information about the property. |
Describes the SELECT query processing that the Cloud can offload to the data source.
See SQL Compliance for SQL syntax details.
Below is an example data set of SQL capabilities. Some aspects of SELECT functionality are returned in a comma-separated list if supported; otherwise, the column contains NO.
Name | Description | Possible Values |
AGGREGATE_FUNCTIONS | Supported aggregation functions. | AVG, COUNT, MAX, MIN, SUM, DISTINCT |
COUNT | Whether COUNT function is supported. | YES, NO |
IDENTIFIER_QUOTE_OPEN_CHAR | The opening character used to escape an identifier. | [ |
IDENTIFIER_QUOTE_CLOSE_CHAR | The closing character used to escape an identifier. | ] |
SUPPORTED_OPERATORS | A list of supported SQL operators. | =, >, <, >=, <=, <>, !=, LIKE, NOT LIKE, IN, NOT IN, IS NULL, IS NOT NULL, AND, OR |
GROUP_BY | Whether GROUP BY is supported, and, if so, the degree of support. | NO, NO_RELATION, EQUALS_SELECT, SQL_GB_COLLATE |
OJ_CAPABILITIES | The supported varieties of outer joins supported. | NO, LEFT, RIGHT, FULL, INNER, NOT_ORDERED, ALL_COMPARISON_OPS |
OUTER_JOINS | Whether outer joins are supported. | YES, NO |
SUBQUERIES | Whether subqueries are supported, and, if so, the degree of support. | NO, COMPARISON, EXISTS, IN, CORRELATED_SUBQUERIES, QUANTIFIED |
STRING_FUNCTIONS | Supported string functions. | LENGTH, CHAR, LOCATE, REPLACE, SUBSTRING, RTRIM, LTRIM, RIGHT, LEFT, UCASE, SPACE, SOUNDEX, LCASE, CONCAT, ASCII, REPEAT, OCTET, BIT, POSITION, INSERT, TRIM, UPPER, REGEXP, LOWER, DIFFERENCE, CHARACTER, SUBSTR, STR, REVERSE, PLAN, UUIDTOSTR, TRANSLATE, TRAILING, TO, STUFF, STRTOUUID, STRING, SPLIT, SORTKEY, SIMILAR, REPLICATE, PATINDEX, LPAD, LEN, LEADING, KEY, INSTR, INSERTSTR, HTML, GRAPHICAL, CONVERT, COLLATION, CHARINDEX, BYTE |
NUMERIC_FUNCTIONS | Supported numeric functions. | ABS, ACOS, ASIN, ATAN, ATAN2, CEILING, COS, COT, EXP, FLOOR, LOG, MOD, SIGN, SIN, SQRT, TAN, PI, RAND, DEGREES, LOG10, POWER, RADIANS, ROUND, TRUNCATE |
TIMEDATE_FUNCTIONS | Supported date/time functions. | NOW, CURDATE, DAYOFMONTH, DAYOFWEEK, DAYOFYEAR, MONTH, QUARTER, WEEK, YEAR, CURTIME, HOUR, MINUTE, SECOND, TIMESTAMPADD, TIMESTAMPDIFF, DAYNAME, MONTHNAME, CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, EXTRACT |
REPLICATION_SKIP_TABLES | Indicates tables skipped during replication. | |
REPLICATION_TIMECHECK_COLUMNS | A string array containing a list of columns which will be used to check for (in the given order) to use as a modified column during replication. | |
IDENTIFIER_PATTERN | String value indicating what string is valid for an identifier. | |
SUPPORT_TRANSACTION | Indicates if the provider supports transactions such as commit and rollback. | YES, NO |
DIALECT | Indicates the SQL dialect to use. | |
KEY_PROPERTIES | Indicates the properties which identify the uniform database. | |
SUPPORTS_MULTIPLE_SCHEMAS | Indicates if multiple schemas may exist for the provider. | YES, NO |
SUPPORTS_MULTIPLE_CATALOGS | Indicates if multiple catalogs may exist for the provider. | YES, NO |
DATASYNCVERSION | The CData Data Sync version needed to access this driver. | Standard, Starter, Professional, Enterprise |
DATASYNCCATEGORY | The CData Data Sync category of this driver. | Source, Destination, Cloud Destination |
SUPPORTSENHANCEDSQL | Whether enhanced SQL functionality beyond what is offered by the API is supported. | TRUE, FALSE |
SUPPORTS_BATCH_OPERATIONS | Whether batch operations are supported. | YES, NO |
SQL_CAP | All supported SQL capabilities for this driver. | SELECT, INSERT, DELETE, UPDATE, TRANSACTIONS, ORDERBY, OAUTH, ASSIGNEDID, LIMIT, LIKE, BULKINSERT, COUNT, BULKDELETE, BULKUPDATE, GROUPBY, HAVING, AGGS, OFFSET, REPLICATE, COUNTDISTINCT, JOINS, DROP, CREATE, DISTINCT, INNERJOINS, SUBQUERIES, ALTER, MULTIPLESCHEMAS, GROUPBYNORELATION, OUTERJOINS, UNIONALL, UNION, UPSERT, GETDELETED, CROSSJOINS, GROUPBYCOLLATE, MULTIPLECATS, FULLOUTERJOIN, MERGE, JSONEXTRACT, BULKUPSERT, SUM, SUBQUERIESFULL, MIN, MAX, JOINSFULL, XMLEXTRACT, AVG, MULTISTATEMENTS, FOREIGNKEYS, CASE, LEFTJOINS, COMMAJOINS, WITH, LITERALS, RENAME, NESTEDTABLES, EXECUTE, BATCH, BASIC, INDEX |
PREFERRED_CACHE_OPTIONS | A string value specifies the preferred cacheOptions. | |
ENABLE_EF_ADVANCED_QUERY | Indicates if the driver directly supports advanced queries coming from Entity Framework. If not, queries will be handled client side. | YES, NO |
PSEUDO_COLUMNS | A string array indicating the available pseudo columns. | |
MERGE_ALWAYS | If the value is true, The Merge Mode is forcibly executed in Data Sync. | TRUE, FALSE |
REPLICATION_MIN_DATE_QUERY | A select query to return the replicate start datetime. | |
REPLICATION_MIN_FUNCTION | Allows a provider to specify the formula name to use for executing a server side min. | |
REPLICATION_START_DATE | Allows a provider to specify a replicate startdate. | |
REPLICATION_MAX_DATE_QUERY | A select query to return the replicate end datetime. | |
REPLICATION_MAX_FUNCTION | Allows a provider to specify the formula name to use for executing a server side max. | |
IGNORE_INTERVALS_ON_INITIAL_REPLICATE | A list of tables which will skip dividing the replicate into chunks on the initial replicate. | |
CHECKCACHE_USE_PARENTID | Indicates whether the CheckCache statement should be done against the parent key column. | TRUE, FALSE |
CREATE_SCHEMA_PROCEDURES | Indicates stored procedures that can be used for generating schema files. |
The following query retrieves the operators that can be used in the WHERE clause:
SELECT * FROM sys_sqlinfo WHERE Name = 'SUPPORTED_OPERATORS'
Note that individual tables may have different limitations or requirements on the WHERE clause; refer to the Data Model section for more information.
Name | Type | Description |
NAME | String | A component of SQL syntax, or a capability that can be processed on the server. |
VALUE | String | Detail on the supported SQL or SQL syntax. |
Returns information about attempted modifications.
The following query retrieves the Ids of the modified rows in a batch operation:
SELECT * FROM sys_identity
Name | Type | Description |
Id | String | The database-generated Id returned from a data modification operation. |
Batch | String | An identifier for the batch. 1 for a single operation. |
Operation | String | The result of the operation in the batch: INSERTED, UPDATED, or DELETED. |
Message | String | SUCCESS or an error message if the update in the batch failed. |
The connection string properties are the various options that can be used to establish a connection. This section provides a complete list of the options you can configure in the connection string for this provider. Click the links for further details.
For more information on establishing a connection, see Establishing a Connection.
Property | Description |
AuthScheme | The authentication mechanism that the provider will use to authenticate with Redis. |
Server | The host name or IP address of the server hosting the Redis instance. |
Port | The port for the Redis database. |
LogicalDatabase | The index of the Redis Logical Database. |
User | The username provided for authentication with Redis ACL. |
Password | The password used to authenticate with Redis. |
EnableCluster | This field sets whether the Redis Cluster Mode is enabled. |
UseSSL | This field sets whether SSL is enabled. |
ReplicaSet | This property allows you to specify multiple servers in addition to the one configured in Server and Port . Specify both a server name and port; separate servers with a comma. |
Property | Description |
DefineTables | Define the tables exposed by the provider using table names and Redis key patterns. |
PatternSeparator | Define the table pattern's delimiter. |
ReaderEndpoints | The slave hosts and port array, which indicates the Redis Master/Slave cluster's slave instances, are split by a comma. |
TablePattern | Define the tables exposed by the provider using Redis key patterns. |
Property | Description |
SSLStartMode | This property determines how the provider starts the SSL negotiation. |
SSLServerCert | The certificate to be accepted from the server when connecting using TLS/SSL. |
Property | Description |
SSHAuthMode | The authentication method used when establishing an SSH Tunnel to the service. |
SSHClientCert | A certificate to be used for authenticating the SSHUser. |
SSHClientCertPassword | The password of the SSHClientCert key if it has one. |
SSHClientCertSubject | The subject of the SSH client certificate. |
SSHClientCertType | The type of SSHClientCert private key. |
SSHServer | The SSH server. |
SSHPort | The SSH port. |
SSHUser | The SSH user. |
SSHPassword | The SSH password. |
SSHServerFingerprint | The SSH server fingerprint. |
UseSSH | Whether to tunnel the Redis connection over SSH. Use SSH. |
Property | Description |
Verbosity | The verbosity level that determines the amount of detail included in the log file. |
Property | Description |
BrowsableSchemas | This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC. |
Property | Description |
IgnoreTypeErrors | Removes support for the specified data types and ignores casting exceptions for those types. |
MaxRows | Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses. |
ParallelMode | This option sets whether the provider should use multiple connections when connecting to Redis. |
PseudoColumns | This property indicates whether or not to include pseudo columns as columns to the table. |
QueryTimeout | The timeout in seconds for which the provider will wait for the query response. The default value is -1, which indicates the provider should never time out. |
RowScanDepth | The maximum number of rows to scan to look for the columns available in a table. |
TableScanDepth | The maximum number of keys to scan when looking for tables available in your Redis database. |
Timeout | The value in seconds until the timeout error is thrown, canceling the operation. |
This section provides a complete list of the Authentication properties you can configure in the connection string for this provider.
Property | Description |
AuthScheme | The authentication mechanism that the provider will use to authenticate with Redis. |
Server | The host name or IP address of the server hosting the Redis instance. |
Port | The port for the Redis database. |
LogicalDatabase | The index of the Redis Logical Database. |
User | The username provided for authentication with Redis ACL. |
Password | The password used to authenticate with Redis. |
EnableCluster | This field sets whether the Redis Cluster Mode is enabled. |
UseSSL | This field sets whether SSL is enabled. |
ReplicaSet | This property allows you to specify multiple servers in addition to the one configured in Server and Port . Specify both a server name and port; separate servers with a comma. |
The authentication mechanism that the provider will use to authenticate with Redis.
string
"Password"
Choose one of the following:
The host name or IP address of the server hosting the Redis instance.
string
""
The host name or IP address of the server hosting the Redis instance.
The port for the Redis database.
string
"6379"
The port for the Redis database.
The index of the Redis Logical Database.
string
"0"
The index of the Redis Logical Database. The default value is 0.
The username provided for authentication with Redis ACL.
string
""
The username provided for authentication with Redis ACL.
The password used to authenticate with Redis.
string
""
The password used to authenticate with Redis.
This field sets whether the Redis Cluster Mode is enabled.
bool
false
This field sets whether the Redis Cluster Mode is enabled.
This field sets whether SSL is enabled.
bool
true
This field sets whether the Cloud will attempt to negotiate TLS/SSL connections to the server. By default, the Cloud checks the server's certificate against the system's trusted certificate store. To specify another certificate, set SSLServerCert.
This property allows you to specify multiple servers in addition to the one configured in Server and Port . Specify both a server name and port; separate servers with a comma.
string
""
This property only works when EnableCluster is True. This property allows you to specify the other servers in the replica set in addition to the one configured in Server and Port. You must specify all servers in the replica set using ReplicaSet, Server, and Port.
Specify both a server name and port in ReplicaSet; separate servers with a comma. For example:
Server=localhost;Port=6379;ReplicaSet=localhost:6380,localhost:6381;
To find the primary server, the Cloud queries the servers in ReplicaSet and the server specified by Server and Port.
This section provides a complete list of the Connection properties you can configure in the connection string for this provider.
Property | Description |
DefineTables | Define the tables exposed by the provider using table names and Redis key patterns. |
PatternSeparator | Define the table pattern's delimiter. |
ReaderEndpoints | The slave hosts and port array, which indicates the Redis Master/Slave cluster's slave instances, are split by a comma. |
TablePattern | Define the tables exposed by the provider using Redis key patterns. |
Define the tables exposed by the provider using table names and Redis key patterns.
string
""
This property is used to define the key pattern within Redis that will appear as tables. The value is a comma-separated list of name-value pairs in the form [Table Name]=[Redis key pattern]. Table Name is the name of the table you want to use for the data and will be used when issuing queries. The Redis key pattern is the pattern to be used to group and pivot corresponding keys into the named table.
For example:
DefineTables="DefinedTable1=table1:*,DefinedTable2=table2:*"
Given this value, all of the keys that begin with "table1:" will be found in DefinedTable1, while all keys that begin with "table2:" will be found in DefinedTable2.
If there is any conflict between tables defined with this property and those defined by the TablePattern, these statically defined tables will take precedence.
Define the table pattern's delimiter.
string
":"
This property is used in tandem with TablePattern to define the delimiter character for the pattern, which determines where the table names derived from the key pattern will end.
This is especially useful when there is more than one delimiter in your TablePattern.
For example, if TablePattern is set to *@*:* and there is a key called "first@second:1", a pattern separator of "@" produces the table name "first" and a PatternSeparator of ":" produces the table name "first@second".
Note that the behavior of the pattern separator is greedy, meaning the last instance of the separator character is used to specify the end of the table name.
For example, if there is a key called "first:second:1", a pattern separator of ":" produces the table name "first:second".
The slave hosts and port array, which indicates the Redis Master/Slave cluster's slave instances, are split by a comma.
string
""
The slave hosts and port array indicate the Redis Master/Slave cluster's slave instances. For example: 'ReaderEndpoints=app:6381,app:6382;'
Define the tables exposed by the provider using Redis key patterns.
string
"*:*"
This property is used to define the key patterns within Redis that will appear as tables. The value is a Redis key pattern. The Redis key pattern is a string pattern containing a separator to determine a hierarchical structure for the key-values stored in the Redis data store. Any other string patterns in the value will limit which keys will be pivoted and returned as tables.
For example, TablePattern="*:*" causes the ":" character to be used as the separator. Given the following keys,
user:1001, user:1002, user:1003, admin:001, admin:002, admin:003
two tables would be exposed, user and admin, with the related keys corresponding to individual rows in each table.
This section provides a complete list of the SSL properties you can configure in the connection string for this provider.
Property | Description |
SSLStartMode | This property determines how the provider starts the SSL negotiation. |
SSLServerCert | The certificate to be accepted from the server when connecting using TLS/SSL. |
This property determines how the provider starts the SSL negotiation.
string
"None"
The SSLStartMode property may have one of the following values:
Automatic | If the remote port is set to the standard plain text port of the protocol (where applicable), the Cloud will behave the same as if SSLStartMode is set to Explicit. In all other cases, SSL negotiation will be implicit. |
Implicit | The SSL negotiation will start immediately after the connection is established. |
Explicit | The Cloud will first connect in plaintext, and then explicitly start SSL negotiation through a protocol command such as STARTTLS. |
None | No SSL negotiation, no SSL security. All communication will be in plain text mode. |
The certificate to be accepted from the server when connecting using TLS/SSL.
string
""
If using a TLS/SSL connection, this property can be used to specify the TLS/SSL certificate to be accepted from the server. Any other certificate that is not trusted by the machine is rejected.
This property can take the following forms:
Description | Example |
A full PEM Certificate (example shortened for brevity) | -----BEGIN CERTIFICATE----- MIIChTCCAe4CAQAwDQYJKoZIhv......Qw== -----END CERTIFICATE----- |
A path to a local file containing the certificate | C:\cert.cer |
The public key (example shortened for brevity) | -----BEGIN RSA PUBLIC KEY----- MIGfMA0GCSq......AQAB -----END RSA PUBLIC KEY----- |
The MD5 Thumbprint (hex values can also be either space or colon separated) | ecadbdda5a1529c58a1e9e09828d70e4 |
The SHA1 Thumbprint (hex values can also be either space or colon separated) | 34a929226ae0819f2ec14b4a3d904f801cbb150d |
If not specified, any certificate trusted by the machine is accepted.
Use '*' to signify to accept all certificates. Note that this is not recommended due to security concerns.
This section provides a complete list of the SSH properties you can configure in the connection string for this provider.
Property | Description |
SSHAuthMode | The authentication method used when establishing an SSH Tunnel to the service. |
SSHClientCert | A certificate to be used for authenticating the SSHUser. |
SSHClientCertPassword | The password of the SSHClientCert key if it has one. |
SSHClientCertSubject | The subject of the SSH client certificate. |
SSHClientCertType | The type of SSHClientCert private key. |
SSHServer | The SSH server. |
SSHPort | The SSH port. |
SSHUser | The SSH user. |
SSHPassword | The SSH password. |
SSHServerFingerprint | The SSH server fingerprint. |
UseSSH | Whether to tunnel the Redis connection over SSH. Use SSH. |
The authentication method used when establishing an SSH Tunnel to the service.
string
"Password"
A certificate to be used for authenticating the SSHUser.
string
""
SSHClientCert must contain a valid private key in order to use public key authentication. A public key is optional, if one is not included then the Cloud generates it from the private key. The Cloud sends the public key to the server and the connection is allowed if the user has authorized the public key.
The SSHClientCertType field specifies the type of the key store specified by SSHClientCert. If the store is password protected, specify the password in SSHClientCertPassword.
Some types of key stores are containers which may include multiple keys. By default the Cloud will select the first key in the store, but you can specify a specific key using SSHClientCertSubject.
The password of the SSHClientCert key if it has one.
string
""
This property is only used when authenticating to SFTP servers with SSHAuthMode set to PublicKey and SSHClientCert set to a private key.
The subject of the SSH client certificate.
string
"*"
When loading a certificate the subject is used to locate the certificate in the store.
If an exact match is not found, the store is searched for subjects containing the value of the property.
If a match is still not found, the property is set to an empty string, and no certificate is selected.
The special value "*" picks the first certificate in the certificate store.
The certificate subject is a comma separated list of distinguished name fields and values. For instance "CN=www.server.com, OU=test, C=US, [email protected]". Common fields and their meanings are displayed below.
Field | Meaning |
CN | Common Name. This is commonly a host name like www.server.com. |
O | Organization |
OU | Organizational Unit |
L | Locality |
S | State |
C | Country |
E | Email Address |
If a field value contains a comma it must be quoted.
The type of SSHClientCert private key.
string
"PEMKEY_FILE"
This property can take one of the following values:
Types | Description | Allowed Blob Values |
MACHINE/USER | Blob values are not supported. | |
JKSFILE/JKSBLOB | base64-only | |
PFXFILE/PFXBLOB | A PKCS12-format (.pfx) file. Must contain both a certificate and a private key. | base64-only |
PEMKEY_FILE/PEMKEY_BLOB | A PEM-format file. Must contain an RSA, DSA, or OPENSSH private key. Can optionally contain a certificate matching the private key. | base64 or plain text. Newlines may be replaced with spaces when providing the blob as text. |
PPKFILE/PPKBLOB | A PuTTY-format private key created using the puttygen tool. | base64-only |
XMLFILE/XMLBLOB | An XML key in the format generated by the .NET RSA class: RSA.ToXmlString(true). | base64 or plain text. |
The SSH server.
string
""
The SSH server.
The SSH port.
string
"22"
The SSH port.
The SSH user.
string
""
The SSH user.
The SSH password.
string
""
The SSH password.
The SSH server fingerprint.
string
""
The SSH server fingerprint.
Whether to tunnel the Redis connection over SSH. Use SSH.
bool
false
By default the Cloud will attempt to connect directly to Redis. When this option is enabled, the Cloud will instead establish an SSH connection with the SSHServer and tunnel the connection to Redis through it.
This section provides a complete list of the Logging properties you can configure in the connection string for this provider.
Property | Description |
Verbosity | The verbosity level that determines the amount of detail included in the log file. |
The verbosity level that determines the amount of detail included in the log file.
string
"1"
The verbosity level determines the amount of detail that the Cloud reports to the Logfile. Verbosity levels from 1 to 5 are supported. These are detailed in the Logging page.
This section provides a complete list of the Schema properties you can configure in the connection string for this provider.
Property | Description |
BrowsableSchemas | This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC. |
This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC.
string
""
Listing the schemas from databases can be expensive. Providing a list of schemas in the connection string improves the performance.
This section provides a complete list of the Miscellaneous properties you can configure in the connection string for this provider.
Property | Description |
IgnoreTypeErrors | Removes support for the specified data types and ignores casting exceptions for those types. |
MaxRows | Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses. |
ParallelMode | This option sets whether the provider should use multiple connections when connecting to Redis. |
PseudoColumns | This property indicates whether or not to include pseudo columns as columns to the table. |
QueryTimeout | The timeout in seconds for which the provider will wait for the query response. The default value is -1, which indicates the provider should never time out. |
RowScanDepth | The maximum number of rows to scan to look for the columns available in a table. |
TableScanDepth | The maximum number of keys to scan when looking for tables available in your Redis database. |
Timeout | The value in seconds until the timeout error is thrown, canceling the operation. |
Removes support for the specified data types and ignores casting exceptions for those types.
string
""
A comma-separated list of data types for which to ignore casting exceptions and treat as strings. For example, IgnoreTypeErrors=Date,Time.
If the value can be parsed as the specified type, it is returned as a string; otherwise, the value is returned as NULL instead.
Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses.
int
-1
Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses.
This option sets whether the provider should use multiple connections when connecting to Redis.
bool
false
The default is that parallel mode is disabled, which means that the Cloud will use only one connection when communicating with Redis. This works well for smaller databases, but can cause performance and memory usage issues on larger databases.
If parallel mode is enabled, the Cloud will open different connections to Redis for discovering keys and reading data. This makes interacting with larger databases more efficient but can add overhead for smaller databases.
If parallel mode is enabled, you can tune how much memory is used by the Cloud by using the hidden MaxPageSize property (see Other). The default value is 5, but you can increase it to make the Cloud faster or decrease it to make the Cloud use less memory.
This property indicates whether or not to include pseudo columns as columns to the table.
string
""
This setting is particularly helpful in Entity Framework, which does not allow you to set a value for a pseudo column unless it is a table column. The value of this connection setting is of the format "Table1=Column1, Table1=Column2, Table2=Column3". You can use the "*" character to include all tables and all columns; for example, "*=*".
The timeout in seconds for which the provider will wait for the query response. The default value is -1, which indicates the provider should never time out.
string
"-1"
The timeout in seconds for which the Cloud will wait for the query response. The default value is -1, which indicates the Cloud should never time out.
The maximum number of rows to scan to look for the columns available in a table.
int
50
The columns in a table must be determined by scanning table rows. This value determines the maximum number of rows that will be scanned.
Setting a high value may decrease performance. Setting a low value may prevent the data type from being determined properly, especially when there is null data.
The maximum number of keys to scan when looking for tables available in your Redis database.
string
"-1"
Since Redis is schemaless, the Cloud determines tables by finding keys that match the TablePattern. This value determines the maximum number of keys that will be scanned for each entry in TablePattern.
To disable this limit and always scan all keys, set the value of this property to "-1". Otherwise, set this property to a positive integer to limit the keys scanned to that amount.
The value in seconds until the timeout error is thrown, canceling the operation.
int
60
If Timeout = 0, operations do not time out. The operations run until they complete successfully or until they encounter an error condition.
If Timeout expires and the operation is not yet complete, the Cloud throws an exception.