[
https://issues.apache.org/jira/browse/CALCITE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270071#comment-14270071
]
Julian Hyde edited comment on CALCITE-497 at 1/8/15 9:28 PM:
-------------------------------------------------------------
{quote}Would it be possible to indicate in some way that it's ambiguous (i.e.
differentiate this from the case where none are found)? It might be confusing
otherwise.{quote}
Yes; please open a new issue.
was (Author: julianhyde):
.bq Would it be possible to indicate in some way that it's ambiguous (i.e.
differentiate this from the case where none are found)? It might be confusing
otherwise.
Yes; please open a new issue.
> 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)
