Wysakowicz' <mailto:dwysakow...@apache.org>;
mailto:user@flink.apache.org
*Cc:* Richards, Adam S [Engineering] <mailto:adam.richa...@ny.email.gs.com>
*Subject:* RE: Table API: Joining on Tables of Complex Types
Very well - I'll give this a try. Thanks, Dawid.
*// *ah**
*
eed.
// ah
-Original Message-
From: Timo Walther
Sent: Friday, January 17, 2020 11:29 AM
To: user@flink.apache.org
Subject: Re: Table API: Joining on Tables of Complex Types
Hi Andreas,
if dataset.getType() returns a RowTypeInfo you can ignore this log message. The
type extractor runs b
.gs.com>>; user@flink.apache.org
<mailto:user@flink.apache.org>
*Cc:* Richards, Adam S [Engineering] <mailto:adam.richa...@ny.email.gs.com>>
*Subject:* Re: Table API: Joining on Tables of Complex Types
Hi Andreas,
Converting your GenericRecords to Rows would
ilto:andreas.ha...@ny.email.gs.com>>;
user@flink.apache.org<mailto:user@flink.apache.org>
Cc: Richards, Adam S [Engineering]
mailto:adam.richa...@ny.email.gs.com>>
Subject: Re: Table API: Joining on Tables of Complex Types
Hi Andreas,
Converting your GenericRecords to
Very well - I'll give this a try. Thanks, Dawid.
// ah
From: Dawid Wysakowicz
Sent: Wednesday, January 8, 2020 7:21 AM
To: Hailu, Andreas [Engineering] ;
user@flink.apache.org
Cc: Richards, Adam S [Engineering]
Subject: Re: Table API: Joining on Tables of Complex Types
Hi An
Hailu, Andreas [Engineering] ;
> user@flink.apache.org
> *Cc:* Richards, Adam S [Engineering]
> *Subject:* Re: Table API: Joining on Tables of Complex Types
>
>
>
> Hi Andreas,
>
> First of all I would highly recommend converting a non-structured
> types to structured
gt;complex object with accessors into a Table of structured types. Or by
>structured types, did you mean Row?
// ah
From: Dawid Wysakowicz
Sent: Monday, January 6, 2020 9:32 AM
To: Hailu, Andreas [Engineering] ;
user@flink.apache.org
Cc: Richards, Adam S [Engineering]
Subject: Re: Table API: Joi
Hi Andreas,
First of all I would highly recommend converting a non-structured types
to structured types as soon as possible as it opens more possibilities
to optimize the plan.
Have you tried:
Table users =
batchTableEnvironment.fromDataSet(usersDataset).select("getField(f0,
userName) as userNam
