I don't think it's on the server side, because if I use the same data sources in native interfaces (pyspark for example vs. displayed in spark sql) or the drill command line, those extra formatting options don't appear.
On Wed, Apr 6, 2016 at 8:31 PM, Corneau Damien <cornead...@gmail.com> wrote: > There is also this kind of behaviour for IDs which can be annoying. > However I don't remember if its the server sending that, or the front-end > making this transformation > > On Thu, Apr 7, 2016 at 8:32 AM, Christopher Matta <ch...@mapr.com> wrote: > >> Yea this has always bothered me. Do commas even need to be displayed it >> the field is an int? Are they adding anything? >> >> >> On Wednesday, April 6, 2016, John Omernik <j...@omernik.com> wrote: >> >>> Note this is also the case in the spark sql interpreter. >>> >>> Thanks! >>> >>> On Wed, Apr 6, 2016 at 4:10 PM, John Omernik <j...@omernik.com> wrote: >>> >>>> Are there display settings in the jdbc interpreter. Something in how >>>> data is being returned from Apache Drill is making some assumptions about >>>> formatting that is bothering me, for example, a zip code field is being >>>> read (I assume) as an int, and commas are being added in the display. The >>>> commas don't exist in the raw data, only in the output form jdbc. >>>> >>>> Thoughts? >>>> >>>> John >>>> >>> >>> >> >> -- >> -- >> Chris Matta >> 215-701-3146 >> ch...@mapr.com >> >> >
