Creating a user-defined aggregate function (UDA)

User-Defined Aggregates (UDAs) can be used to manipulate stored data across rows of data, returning a result that is further manipulated by a final function.

DataStax Enterprise allows users to define aggregate functions that can be applied to data stored in a table as part of a query result. The aggregate function must be created prior to its use in a SELECT statement and the query must only include the aggregate function itself, but no columns. The state function is called once for each row, and the value returned by the state function becomes the new state. After all rows are processed, the optional final function is executed with the last state value as its argument. Aggregation is performed by the coordinator.

Tip: Use OpsCenter to view the CQL for a defined UDA in a keyspace.

The example shown computes the team average for race time for all the cyclists stored in the table. The race time is computed in seconds.


  • Create a state function, as a user-defined function (UDF), if needed. This function adds all the race times together and counts the number of entries.
    CREATE OR REPLACE FUNCTION cycling.avgState (
      state tuple<int, bigint>,
      val int
      RETURNS tuple<int, bigint> 
      LANGUAGE java AS 
          if (val != null) { 
            state.setInt(0, state.getInt(0) + 1); 
            state.setLong(1, state.getLong(1) + val.intValue()); 
          return state; 
  • Create a final function, as a user-defined function (UDF), if needed. This function computes the average of the values passed to it from the state function.
    CREATE OR REPLACE FUNCTION cycling.avgFinal (
      state tuple<int,bigint>
      RETURNS double 
      LANGUAGE java AS 
          double r = 0; 
          if (state.getInt(0) == 0) return null; 
          r = state.getLong(1); 
          r /= state.getInt(0); 
          return Double.valueOf(r);
  • Create the aggregate function using the state and final functions, and add an STYPE to define the data type for the function. Different STYPEs distinguishes between functions with the same name. An aggregate can be replaced with a different aggregate if OR REPLACE is used as shown in the examples above. Optionally, the IF NOT EXISTS keywords can be used to create the aggregate only if another aggregate with the same signature does not exist in the keyspace. OR REPLACE and IF NOT EXISTS cannot be used in the same command.
    CREATE OR REPLACE AGGREGATE cycling.average (
      SFUNC avgState 
      STYPE tuple<int,bigint> 
      FINALFUNC avgFinal 
      INITCOND (0, 0)

What's next

For more information on user-defined aggregates, see Cassandra Aggregates - min, max, avg, group by and A few more Cassandra aggregates.