[Optional] When set, what mode of hive partitioning to use when reading data. Two modes are
supported. (1) AUTO: automatically infer partition key name(s) and type(s). (2) STRINGS:
automatically infer partition key name(s). All types are interpreted as strings. Not all
storage formats support hive partitioning. Requesting hive partitioning on an unsupported
format will lead to an error. Currently supported types include: AVRO, CSV, JSON, ORC and
[Optional] If set to true, queries over this table require a partition filter that can be
used for partition elimination to be specified. Note that this field should only be true when
creating a permanent external table or querying a temporary external table. Hive-partitioned
loads with requirePartitionFilter explicitly set to true will fail.
[Optional] When hive partition detection is requested, a common prefix for all source uris
should be supplied. The prefix must end immediately before the partition key encoding begins.
For example, consider files following this data layout.
gs://bucket/path_to_table/dt=2018-12-31/country=CA/id=3/file.avro When hive partitioning is
requested with either AUTO or STRINGS detection, the common prefix can be either of
gs://bucket/path_to_table or gs://bucket/path_to_table/ (trailing slash does not matter).