[ 
https://issues.apache.org/jira/browse/PHOENIX-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469727#comment-16469727
 ] 

Hudson commented on PHOENIX-4678:
---------------------------------

FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #1878 (See 
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/1878/])
PHOENIX-4678 ndexScrutinyTool generates malformed query due to incorrect 
(jtaylor: rev 4dac9d632454864bb526c7fa144eb49cad850260)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/util/SchemaUtil.java


> IndexScrutinyTool generates malformed query due to incorrect table name(s)
> --------------------------------------------------------------------------
>
>                 Key: PHOENIX-4678
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4678
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Critical
>             Fix For: 4.14.0, 5.0.0
>
>         Attachments: PHOENIX-4678.diff
>
>
> {noformat}
> HADOOP_CLASSPATH="/usr/local/lib/hbase/conf:$(hbase mapredcp)" hadoop jar 
> /usr/local/lib/phoenix-5.0.0-SNAPSHOT/phoenix-5.0.0-SNAPSHOT-client.jar 
> org.apache.phoenix.mapreduce.index.IndexScrutinyTool -dt J -it 
> INDEX1{noformat}
> This ends up running queries like {{SELECT ... FROM .J}} and {{SELECT ... 
> FROM .INDEX1}}.
> This is because SchemaUtil.getQualifiedTableName is not properly handling an 
> empty schema name, only a null schema name.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to