You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Mihai Budiu (Jira)" <ji...@apache.org> on 2026/05/08 23:35:00 UTC
[jira] [Resolved] (CALCITE-7448) Add support for ':' variant path access syntax
[ https://issues.apache.org/jira/browse/CALCITE-7448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mihai Budiu resolved CALCITE-7448.
----------------------------------
Fix Version/s: 1.42.0
Resolution: Fixed
Fixed in [https://github.com/apache/calcite/commit/c7c3f316b6b418714706d18a0f71480bfa5c2a24]
Thank you for your contribution [~tmate]
> Add support for ':' variant path access syntax
> ----------------------------------------------
>
> Key: CALCITE-7448
> URL: https://issues.apache.org/jira/browse/CALCITE-7448
> Project: Calcite
> Issue Type: New Feature
> Components: core
> Affects Versions: 1.41.0
> Reporter: Tamas Mate
> Priority: Major
> Labels: parser, pull-request-available
> Fix For: 1.42.0
>
>
> Implement support for colon field access syntax in the parser, for example:
> {code:java}
> v:field
> v:field.subfield
> v:['field name']
> arr[1]:field{code}
> Several systems (e.g. Snowflake, Databricks) support this kind of access, and with recent VARIANT support in Parquet it seems increasingly relevant for interoperability.
> * [Databricks - :: (colon colon sign) operator|https://docs.databricks.com/aws/en/sql/language-manual/functions/coloncolonsign]
> * [Databricks - : (colon sign) operator|https://docs.databricks.com/aws/en/sql/language-manual/functions/colonsign]
> * [Snowflake - :: operator|https://docs.snowflake.com/en/sql-reference/data-types-semistructured#using-variant-values]
> * [Snowflake - : Dot Notation|https://docs.snowflake.com/en/user-guide/querying-semistructured#label-querying-semistructured-data-dot-notation]
> One challenge is that ":" is already used in JSON constructor syntax, for example:
> {code:java}
> JSON_OBJECT('k': v)
> JSON_OBJECTAGG(k: v){code}
> The implementation needs to define how these cases interact, whether through
> disambiguation, dialect-specific behavior, or parser configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)