Re: Error Messages that are difficult to parse.

2017-09-26 Thread John Omernik
important bug, since it seems we don't know > which column is triggering the Exception. In case there isn't an existing > bug, could you file one for this? > > > > -Original Message- > From: John Omernik [mailto:j...@omernik.com] > Sent: Monday, September 25, 2

RE: Error Messages that are difficult to parse.

2017-09-25 Thread Kunal Khatua
k.com] Sent: Monday, September 25, 2017 11:44 AM To: user Subject: Re: Error Messages that are difficult to parse. This is so odd... select a.sa, a.sp, a.da, a.dp, subject_name from ( select b.sa, b.sp, b.da, b.dp, CASE WHEN b.tls.SNI[0] is null then '' else b.tls.SNI[0] END as subje

Re: Error Messages that are difficult to parse.

2017-09-25 Thread John Omernik
This is so odd... select a.sa, a.sp, a.da, a.dp, subject_name from ( select b.sa, b.sp, b.da, b.dp, CASE WHEN b.tls.SNI[0] is null then '' else b.tls.SNI[0] END as subject_name from `ciscojoy/2017-09-22/*.json` b ) a where subject_name <> '' limit 10 This query works select subject_name from

Re: Error Messages that are difficult to parse.

2017-09-25 Thread John Omernik
So I think I addressed the first one with select CASE when tbl.field.subfield[0] is null then '' else tbl.field.subfield[0] end as myfield from table as tbl That seems to work on small queries but when I try to group by myfield I get Error Returned - Code: 500 Error Text: SYSTEM ERROR: NumberFo