Supported SPL data types for views, charts, and tables

Teracloud® Streams supports only certain Streams Processing Language (SPL) data types in views, charts, and tables.

Table 1. Supported SPL data types for views, charts, and tables

A five column table that indicates which SPL data types are supported in views, charts, and tables. For charts, both X and Y-axis values are included.
SPL data types Supported in:
Views Charts:
Y axis		 Charts:
X axis		 Tables
blob Yes1 No No Yes1
boolean Yes Yes Yes Yes
complex32, complex64 Yes No No Yes
decimal32, decimal64, decimal128 Yes Yes Yes Yes
enum Yes No No Yes
float32, float64 Yes Yes Yes Yes
int8, int16, int32, int64 Yes Yes Yes Yes
list<T>, list<T>[n] Yes Yes2 Yes2 Yes3
map<K,V>, map<K,V>[n] Yes No No Yes4
optional<T>9 Yes No9 No9 Yes 9
rstring, rstring[n] Yes No Yes Yes
set<T>, set<T>[n] Yes No No Yes3
timestamp Yes No Yes5 Yes5
Tuple<...> Yes6 No7 No7 No7
uint8, uint16, uint32, uint64 Yes Yes Yes Yes
ustring Yes No Yes Yes
xml Yes No No Yes8
Table notes:
  1. In the Streams Console, this data type is supported for tables and shown as a string representation of the first 16 bytes of the blob in hexadecimal format.
  2. For guidelines when you are configuring lists for use in charts, see Guidelines for using lists in summary and scrolling event charts.
  3. Lists and sets show the first entry in the list and an ellipsis (for example, 1 ...). The hover help shows the value for the column as a list of values that are separated by a comma. For example, if the list is [1, 2, 3, 4], the hover help looks like 1, 2, 3, 4.
  4. Maps show the first entry in the map and an ellipsis inside braces (for example, {"1": "value", …}). The hover help shows the first entry in the table and the key value pairs separated by a comma, for example, "1": "value", "2" : "value", "3" : "value", "4".
  5. Timestamps on the X axis and in tables are displayed as a long data type value. Use this data type when you need a range of values wider than the values that are provided by the int data type.
  6. Tuples are not supported, but the attributes within a nested tuple can be chosen. The attributes are expressed by using dotted notation down to the primitive type.
  7. Embedded attributes are supported. Tuples are not supported.
  8. XML data types are shown in tables as a string.
  9. For an optional type:
    • If the underlying value of an optional type optional<T> is specified, the value is supported as shown in the table for type T.
    • If the optional type has a null value, tables in Streams Console show null.
    • Charts in Streams Console do not show null values.

Guidelines for using lists in summary and scrolling event charts

For lists in summary charts, where each event replaces the entire chart, use the following guidelines:
  • A numerical list can be configured to provide the Y-axis values. Each array element is plotted as a separate bar, one for each X attribute category. The list must be ordered. Colors can be assigned for each attribute and are used as the bar color for that attribute.
  • An alphanumeric list can be configured to provide the X-axis labels. The list must be ordered and the index must match the order that is used in the values list.
For lists in scrolling event charts, where each event is plotted as a new data point and the chart scrolls to the left, use the following guidelines:
  • A numerical list can be configured for the Y-axis values. Each array element is plotted as a separate bar or line. The list must maintain the same order to ensure the bar or line is plotted continuously.

    Colors cannot be assigned in this case as the array results in multiple lines per attribute for each event.

    Optionally, another list can be configured that specifies the labels for each line to use as the legend for the chart. If not provided, the labels are the attribute name with the index (for example, "myArray[1]").

  • If an alphanumeric list is configured for the X-axis labels, all the entries in the array are used to label each event.