[
https://issues.apache.org/jira/browse/CALCITE-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432698#comment-17432698
]
Mark Grey edited comment on CALCITE-4362 at 10/21/21, 8:09 PM:
---------------------------------------------------------------
{{If the name literals matter for the implementation, another example of such a
pseudocolumn in BigQuery is _TABLE_SUFFIX, which is used when querying sharded
(as opposed to the newer partitioned) tables.}}
was (Author: deacondesperado):
If the name literals matter for the implementation, another example of such a
pseudocolumn in BigQuery is `_TABLE_SUFFIX`, which is used when querying
sharded (as opposed to the newer partitioned) tables.
> Unable to parse queries that use BigQuery pseudo columns
> _PARTITIONDATE/_PARTITIONTIME
> --------------------------------------------------------------------------------------
>
> Key: CALCITE-4362
> URL: https://issues.apache.org/jira/browse/CALCITE-4362
> Project: Calcite
> Issue Type: Bug
> Components: babel
> Reporter: Justin Swett
> Assignee: Julian Hyde
> Priority: Major
>
> BigQuery supports partitioned tables using pseudo columns "_PARTITIONDATE"
> e.g. The following table has two columns you can select from but also
> partitions the data by creation date
> {code:java}
> CREATE or REPLACE TABLE #{table} (
> transaction_id STRING,
> order_date DATE )
> PARTITION BY _PARTITIONDATE
> {code}
>
> The following queries cannot be validated
> {code:java}
> select * from #{table} where _PARTITIONDATE = '2020-11-03' ;
> -- OR
> select * from #{table} where _PARTITIONTIME = '2020-11-03' ;{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
