[
https://issues.apache.org/jira/browse/CALCITE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-497.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0-incubating
Fixed in
http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/175d0705.
In the change I have implemented, if a field is a record type, you can access
its fields (and recursively their fields) without qualifiers if the field names
are unique.
So, this is useful for any document-oriented schema that is strongly typed, not
just Phoenix. Phoenix would just use two levels (a column group is represented
as a record, and each column in that group is a field of that record), but we
could handle any number of levels, and we can handle a row type whose fields
are a mixture of scalars and records.
> Support optional qualifier for column name references
> -----------------------------------------------------
>
> Key: CALCITE-497
> URL: https://issues.apache.org/jira/browse/CALCITE-497
> Project: Calcite
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Julian Hyde
> Labels: phoenix
> Fix For: 1.0.0-incubating
>
>
> Some systems, such as HBase, have a named group to which columns belong (i.e.
> a column family in this case). To disambiguate column references (i.e. if the
> same column name is used in different column families), it's useful to allow
> an optional qualifier. This is similar to the RECORD field mechanism that
> Calcite already supports, but in this case the record name would be optional,
> since it's not necessary if the column names are unique. For example:
> http://phoenix.apache.org/language/index.html#column_ref
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
