Re: Large schemas lead to long DataStream-to-table transformation names

2023-03-06 Thread Xingcan Cui
Oh, I just realized that FLIP-195 has already solved this. We'll upgrade our Flink version to 1.15+. Thanks! On Mon, Mar 6, 2023 at 10:08 AM Xingcan Cui wrote: > Hi Jark, > > Yes. I believe field names of the table would be enough to describe the > conversion operator. I'll try to improve this.

Re: Large schemas lead to long DataStream-to-table transformation names

2023-03-06 Thread Xingcan Cui
Hi Jark, Yes. I believe field names of the table would be enough to describe the conversion operator. I'll try to improve this. Best, Xingcan On Sun, Mar 5, 2023 at 9:18 PM Jark Wu wrote: > Hi Xingcan, > > I think `physicalDataType.toString()` is indeed verbose in this case. > Normal table sca

Re: Large schemas lead to long DataStream-to-table transformation names

2023-03-05 Thread Jark Wu
Hi Xingcan, I think `physicalDataType.toString()` is indeed verbose in this case. Normal table scan generates descriptions using field names instead of the full schema. Will that help in your case? Best, Jark On Sat, 4 Mar 2023 at 06:57, Xingcan Cui wrote: > Hi all, > > We are dealing with som

Large schemas lead to long DataStream-to-table transformation names

2023-03-03 Thread Xingcan Cui
Hi all, We are dealing with some streams with large (nested) schemas. When using `t ableEnv.createTemporaryView()` to register a DataStream to a table, the transformation always gets a large name. It's not a big problem, but quite annoying since the UI and logs are hard to read. Internally, `Exte