INTO (Azure Stream Analytics)

Article
08/02/2024

INTO (Output Stream)

INTO explicitly specifies an output stream, and is always associated with an SELECT expression. If not specified, the default output stream is "output".

Syntax

SQL

[ INTO <output_stream> ]

Arguments

output_stream

Specifies the name of an output stream.

Limitations and Restrictions

You cannot use SELECT … INTO in a WITH clause. For example, INTO clause can only be used in the out-most subquery.

Example

SQL

WITH WAVehicle AS (  
    SELECT TollId, EntryTime AS VehicleEntryTime, LicensePlate, State, Make, Model, VehicleType,    VehicleWeight, Toll, Tag  
    FROM TollTagEntry TIMESTAMP BY EntryTime  
    WHERE State = "WA"
)  
  
SELECT * INTO WAVehicleArchive FROM WAVehicle;  
  
SELECT DateAdd(minute,-3,System.Timestamp()) AS WinStartTime, System.Timestamp() AS WinEndTime, COUNT(*) INTO WAVehicleCount FROM WAVehicle GROUP BY TumblingWindow(minute, 3)

INTO (Shard Count)

INTO explicitly specifies the number of shards in an input step when specifying a partitioning scheme (PARTITION BY). If partition count is not specified, the number of shards is carried over if the PARTITION BY is the same or two otherwise.

INTO is a hint to the system, and may be ignored should the system determine the explicit specification is not beneficial.

INTO Syntax

SQL

[ INTO <shard_count> ]

INTO Arguments

shard_count

Specifies the number of shards in the upstream step.

INTO Limitations and Restrictions

Shard count must be greater than 1. When joining several streams, the partition count of all inputs must be the same.

INTO Example

SQL

WITH Step1 AS (
    SELECT * 
    FROM input 
    PARTITION BY DeviceId
    INTO 10
)

SELECT * INTO [output] FROM Step1 PARTITION BY DeviceId

Share via