...
Page properties | ||||||||
---|---|---|---|---|---|---|---|---|
|
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
...
It is not configurable. By default, PrintStyle.DEFAULT_MAX_COLUMN_WIDTHis used. [1]
Test didn't cover case with text whose length exceeds PrintStyle.DEFAULT_MAX_COLUMN_WIDTH, i.e. 30. [2]
Job running in streaming execution mode with SqlClient
...
It only works for jobs running in streaming execution mode. There is a bug in documentation [23].
Job running in batch execution mode with Table API
It is not configurable. By default, PrintStyle.DEFAULT_MAX_COLUMN_WIDTHis used. [24]
Job running in streaming execution mode with Table API
Same as in batch execution mode, it is not configurable. By default, PrintStyle.DEFAULT_MAX_COLUMN_WIDTHis used. [34]
Conceptually, there is no difference between printing table results of jobs running in batch and streaming exec mode. The snapshot at the calling time will be printed. [45]
Summary
Topics mentioned above are mixed with layered and orthogonal issues. In order to provide a clear big picture, all of them will be summarized in the following table:
...
Deprecated: sql-client.display.max-column-width, default value is 30 | table.display.max-column-width, default value is 30 | ||
sqlclient | Streaming | Changes will be forwarded to table.display.max-column-width | Text longer than the value will be truncated and replaced with “...” |
sqlclient | Batch | No effect. Changes will be forwarded to 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 | 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 “...” |
...