Input Table Schema
| Column | Data Type | Description |
|---|---|---|
| time_column | TIME, TIMESTAMP, INTEGER, BIGINT, SMALLINT, or DATE | Click times (in milliseconds if data type is INTEGER, BIGINT, or SMALLINT). |
| session_timeout | DOUBLE PRECISION | Timeout threshold for a session. |
| partition_column | Any | Column that partitions input. Input data must be partitioned such that each partition contains all rows of an entity. For example, an entity could be user ID if you want to analyze users’ web behavior. It would require partitioning web actions by each user and then sessionizing them according to given criteria. This provides sessionized actions for each user. Conversely, an entity could be device ID if evaluating IoT device activity over network traffic. |
| order_column | Any | Column by which input data is ordered. |
No input table column can have the name 'sessionid' or 'clicklag' because these are output table column names.
Tip: To create a single timestamp column from separate date and time columns:
SELECT (datecolumn || ' ' || timecolumn)::timestamp AS mytimestamp FROM table;