[
https://issues.apache.org/jira/browse/PHOENIX-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982460#comment-15982460
]
Ankit Singhal commented on PHOENIX-3710:
----------------------------------------
Thanks [~sergey.soldatov], changes look good. But at least to avoid regression,
if we can include below two test cases as
IT(IndexExtendedIT.testSecondaryIndex() can be reused for this)
* IndexTool with both tablename and indexname in lowercase
* To check whether the normalisation is correct for phoenix tableName of type
\"S:T\"
> Cannot use lowername data table name with indextool
> ---------------------------------------------------
>
> Key: PHOENIX-3710
> URL: https://issues.apache.org/jira/browse/PHOENIX-3710
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.8.0
> Reporter: Matthew Shipton
> Assignee: Sergey Soldatov
> Priority: Minor
> Attachments: PHOENIX-3710.patch, test.sh, test.sql
>
>
> {code}
> hbase org.apache.phoenix.mapreduce.index.IndexTool --data-table
> \"my_lowcase_table\" --index-table INDEX_TABLE --output-path /tmp/some_path
> {code}
> results in:
> {code}
> java.lang.IllegalArgumentException: INDEX_TABLE is not an index table for
> MY_LOWCASE_TABLE
> {code}
> This is despite the data table being explictly lowercased.
> Appears to be referring to the lowcase table, not the uppercase version.
> Workaround exists by changing the tablename, but this is not always feasible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
