Description
more info could be found at
Tests:
Both configs could be set with new value and following behaviours are expected :
sql-client.display.max-column-width, default value is 30 | table.display.max-column-width, default value is 30 | ||
sqlclient | Streaming | text longer than the value will be truncated and replaced with “...” | Text longer than the value will be truncated and replaced with “...” |
sqlclient | Batch | text longer than the value will be truncated and replaced with “...” | Text longer than the value will be truncated and replaced with “...” |
Table API | Streaming | No effect. table.display.max-column-width with the default value 30 will be used |
Text longer than the value will be truncated and replaced with “...” |
Table API | Batch | No effect. table.display.max-column-width with the default value 30 will be used |
Text longer than the value will be truncated and replaced with “...” |
Please pay attention that this task offers a backward compatible solution and deprecated sql-client.display.max-column-width, which means once sql-client.display.max-column-width is used, it falls into the old scenario where table.display.max-column-width didn't exist, any changes of table.display.max-column-width won't take effect. You should test it either by only using table.display.max-column-width or by using sql-client.display.max-column-width, but not both of them back and forth.
Attachments
Attachments
Issue Links
- is related to
-
FLINK-30025 Unified the max display column width for SqlClient and Table APi in both Streaming and Batch execMode
- Resolved