[
https://issues.apache.org/jira/browse/PHOENIX-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175801#comment-14175801
]
Hudson commented on PHOENIX-973:
--------------------------------
FAILURE: Integrated in Phoenix | 3.0 | Hadoop1 #264 (See
[https://builds.apache.org/job/Phoenix-3.0-hadoop1/264/])
PHOENIX-973 Lexer skips unexpected characters (jtaylor: rev
ef062ad250fc6203cf613dea7417160a68efabd4)
*
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
* phoenix-core/src/test/java/org/apache/phoenix/parse/QueryParserTest.java
* phoenix-core/src/main/java/org/apache/phoenix/util/MetaDataUtil.java
* phoenix-core/src/test/java/org/apache/phoenix/query/BaseTest.java
* phoenix-core/src/main/antlr3/PhoenixSQL.g
* phoenix-core/src/main/java/org/apache/phoenix/schema/SequenceKey.java
* phoenix-core/src/main/java/org/apache/phoenix/util/UpgradeUtil.java
> Lexer skips unexpected characters
> ---------------------------------
>
> Key: PHOENIX-973
> URL: https://issues.apache.org/jira/browse/PHOENIX-973
> Project: Phoenix
> Issue Type: Bug
> Reporter: Samarth Jain
> Fix For: 5.0.0, 4.2, 3.2
>
> Attachments: PHOENIX-973.patch
>
>
> While working on refactoring Phoenix tests, I see sequences created with null
> names like _SEQ_T.null. Of course, parser doesn't like when it sees the
> sequence name as null causing DROP SEQUENCE _SEQ_T.null to fail.
> [~jamestaylor] mentioned we use sequence names with _SEQ_T for creating ids
> for indexes on views. So that is likely the area where this bug resides.
> Needs further investigation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
