If I recall correctly, Google BigQuery has SELECT AS STRUCT. It’s not standard, but if it does what you need we could consider adopting that syntax.
Julian > On Apr 4, 2018, at 10:23 AM, Albert <[email protected]> wrote: > > if it is not SQL standard, it's just a matter of categorizing it to some > dialect ? > >> On Wed, Apr 4, 2018 at 10:19 AM, Michael Mior <[email protected]> wrote: >> >> Apologies for my silence. I don't really have thoughts on the matter at >> this point. It might be helpful if you can give an example of what you're >> proposing. Unless I'm missing something (very possible), it's not part of >> the SQL standard. >> >> -- >> Michael Mior >> [email protected] >> >> 2018-04-03 18:48 GMT-04:00 Shuyi Chen <[email protected]>: >> >>> Friendly ping, any thoughts? Much appreciated. >>> >>> Shuyi >>> >>>> On Tue, Mar 27, 2018 at 11:59 PM, Shuyi Chen <[email protected]> wrote: >>>> >>>> Hi community, >>>> >>>> I am thinking of adding the following support in Calcite to support >> named >>>> row construction, e.g. >>>> >>>> SELECT (a as first_name, b as last_name, (c as zip code, d as street, e >>> as >>>> state) as address) as record FROM example_table >>>> >>>> The output will be struct with field names specified in the SQL. The >>> usage >>>> scenario is that say, in streaming SQL, the downstream sink's schema >> can >>>> not be changed, so we will need to use SQL to construct a struct with >> the >>>> proper naming according to the schema in order to write to the >> downstream >>>> sinks. Thanks a lot. >>>> >>>> Shuyi >>>> >>>> -- >>>> "So you have to trust that the dots will somehow connect in your >> future." >>>> >>> >>> >>> >>> -- >>> "So you have to trust that the dots will somehow connect in your future." >>> >> > > > > -- > ~~~~~~~~~~~~~~~ > no mistakes > ~~~~~~~~~~~~~~~~~~
