[
https://issues.apache.org/jira/browse/PHOENIX-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15549323#comment-15549323
]
Julian Hyde commented on PHOENIX-3347:
--------------------------------------
Up to you. Maybe a PHOENIX member in SqlConformance. Or maybe not. Whatever is
the most concise way to represent what dialect of SQL Phoenix supports.
At some point I thought we'd create an interface (name TBD) and have {{enum
SqlConformance}} implement it. Thus you could roll your own conformance.
> Change conformance or remove SELECT statements without FROM clauses
> -------------------------------------------------------------------
>
> Key: PHOENIX-3347
> URL: https://issues.apache.org/jira/browse/PHOENIX-3347
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Eric Lomore
> Assignee: Eric Lomore
>
> Current conformance settings do not allow SELECT statements without a FROM
> clause. Either need to change conformance or stop supporting SELECT without
> FROM as Phoenix currently does.
> According to the Calcite parser,
> {{FROM is mandatory in standard SQL, optional in dialects such as MySQL,
> PostgreSQL. The parser allows SELECT without FROM, but the validator fails if
> conformance is, say, STRICT_2003.}}
> Based on PhoenixCalciteEmbeddedDriver.java, we are using ORACLE_10
> conformance which does not support this
> {code}setPropertyIfNotSpecified(
> info2,
> CalciteConnectionProperty.CONFORMANCE.camelName(),
> SqlConformance.ORACLE_10.toString()){code}
> Confirming this is the fact that it is specifically the SqlValidator throwing
> the exception in relevant test cases
> {{Caused by: org.apache.calcite.sql.validate.SqlValidatorException: SELECT
> must have a FROM clause}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
