You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2018/05/09 20:57:00 UTC
[jira] [Updated] (PHOENIX-4678) IndexScrutinyTool generates
malformed query due to incorrect table name(s)
[ https://issues.apache.org/jira/browse/PHOENIX-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-4678:
----------------------------------
Fix Version/s: 5.0.0
> 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: 5.0.0, 4.15.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)