phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4678) IndexScrutinyTool generates malformed query due to incorrect table name(s)
Date Wed, 28 Mar 2018 19:12:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser updated PHOENIX-4678:
--------------------------------
    Attachment: PHOENIX-4678.diff

> 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)

Mime
View raw message