On October 30, 2022, all 1.2.x versions of the Splunk Data Stream Processor will reach its end of support date. See the Splunk Software Support Policy for details.
Select
This topic describes how to use the function in the .
Description
Assigns alternative names to fields or applies scalar functions to a group of fields. Returns a new record with only the provided fields.
When using this function in the UI, you can view the record's input and output schema. For example, if you are selecting data to be normalized from the Ingest service, then clicking the View Configurations tab in the select
function displays the default fields in the event schema. You can normalize fields using field aliases
or with an eval
expression.
Function Input/Output Schema
- Function Input
- collection<record<R>>
- This function takes in collections of records with schema R.
- Function Output
- collection<record<S>>
- This function outputs the same collection of records but with a different schema S.
Syntax
- select
- <expression> AS <field> ...
Required arguments
- function
- Syntax: collection<expression<any>>
- Description: The <expression> can be either a field name or a scalar function.
Usage
This section contains additional usage information about the Select function.
Difference between Select and Eval
Both functions are used to change the fields in the record. However, while the eval function keeps existing fields and adds new fields for the aliases in the eval, select only includes the fields explicitly specified in the select function.
SPL2 example
When working in the SPL View, you can write the function by providing the arguments in this exact order.
This example keeps timestamp
, id
, and owner
fields unchanged but renames logGroup
and logStream
fields.
... |select timestamp, id, owner, logGroup AS log_group, logStream AS log_stream | ...;
Rename | Sentiment Analysis (beta) |
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.1.0, 1.2.0, 1.2.1-patch02, 1.2.1, 1.2.2-patch02, 1.2.4, 1.2.5, 1.3.0, 1.3.1, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6
Feedback submitted, thanks!