Hi! This job will work as long as your SQL statement is valid. Did you meet some difficulties? Or what is your concern? A record of 100K is sort of large, but I've seen quite a lot of jobs with such record size so it is OK.
HG <hanspeter.sl...@gmail.com> 于2022年1月27日周四 02:57写道： > Hi, > > I need to calculate elapsed times between steps of a transaction. > Each step is an event. All steps belonging to a single transaction have > the same transaction id. Every event has a handling time. > All information is part of a large JSON structure. > But I can have the incoming source supply transactionId and handlingTime > separately. > That would save me retrieving the windowingKey = transactionID and > handlingTime out of the nested JSON > Basically I want to use the SQL api to do: > > select transactionId > , handlingTime - previousHandlingTime as elapsedTime > , largeJSON from ( > select transactionId > , handlingTime > , lag(handlingTime) over (partition by transactionID order by > handlingTime) as previousHandlingTime > , largeJSON > from source > ) > > The largeJSON can be about 100K. > Would this work? > > Regards Hans-Peter > >
