The schema that's provided here does not include any headers used by Cloudflare Access (namely, RequestHeaders. This is known and addressed here.
However, I cannot add this to the BigQuery Schema easily, as the RequestHeaders isn't mentioned in the default schema, so I'm trying to hack around it by adding it manually inside the BigQuery Console.
This (I think) uses a RECORD data type, which requires nested fields to be added. But, FieldNames cannot have dashes (-) in them, only alphanumeric/underscore characters.
But the field I need to add to store usernames is cf-access-user (technically RequestHeaders.cf-access-user) has dashes... so in essence I cannot add in this field to BigQuery, unless I figure out some sort of magic to automatically convert the dashes into another name (to which, I'm having a heck of a time doing because I'm a newbie at BQ).
Any advice/insight you can provide would be extremely helpful.
The schema that's provided here does not include any headers used by Cloudflare Access (namely, RequestHeaders. This is known and addressed here.
However, I cannot add this to the BigQuery Schema easily, as the
RequestHeadersisn't mentioned in the default schema, so I'm trying to hack around it by adding it manually inside the BigQuery Console.This (I think) uses a
RECORDdata type, which requires nested fields to be added. But, FieldNames cannot have dashes(-)in them, only alphanumeric/underscore characters.But the field I need to add to store usernames is
cf-access-user(technicallyRequestHeaders.cf-access-user) has dashes... so in essence I cannot add in this field to BigQuery, unless I figure out some sort of magic to automatically convert the dashes into another name (to which, I'm having a heck of a time doing because I'm a newbie at BQ).Any advice/insight you can provide would be extremely helpful.