PrettyPrint Improvements

[asfimport]

We have some pretty printing capabilities, but we may want to think at a high level about the design first.

Reporter: Will Jones / @wjones127

Related issues:

• [Python] Pretty printing very large ChunkedArray objects can use unbounded memory (is a parent of)
• [C++] Implement PrettyPrint for Scalars (is a parent of)
• [C++][Python][R] PrettyPrint ignores timezone (is a parent of)
• [Python] Add character limit to ChunkedArray repr (is a parent of)
• [C++][Python] Add a space after commas in pretty-print output (is a parent of)
• [C++] Right-justify array values in PrettyPrint (is a parent of)
• [C++] Adding tabular pretty printing of Table / RecordBatch (is related to)

_{Note: This issue was originally created as ARROW-18359. Please see the migration documentation for further details.}

[asfimport]

Joris Van den Bossche / @jorisvandenbossche:
Also linking ARROW-14799, as that is another high-level potential change for Tables/RecordBatches

[asfimport]

Dewey Dunnington / @paleolimbot:
I'm not sure if this is covered by one of the subtasks, but really huge binary arrays take forever to print...I am guessing because it tries to convert the entire binary array to a string before selecting the few characters that will actually be shown:

library(arrow)
#> Some features are not enabled in this build of Arrow. Run `arrow_info()` for more information.
#> 
#> Attaching package: 'arrow'
#> The following object is masked from 'package:utils':
#> 
#>     timestamp

really_big_raw <- raw(1e9)
really_big_binary <- Array$create(list(really_big_raw), type = binary())
system.time(really_big_binary$ToString())
#>    user  system elapsed 
#>  12.396   1.660  14.269

(I ran into that one because the current encoding for geospatial data in Parquet files is binary() and the elements can be huge)

[asfimport]

David Li / @lidavidm:
I'd say it's sorta related to ARROW-4099 but not quite the same, and worth a new subtask