[ https://issues.apache.org/jira/browse/HIVE-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004168#comment-14004168 ]
Sun Rui commented on HIVE-7097: ------------------------------- [~cartershanklin] Thanks for your explanation. I happened to use REGEX columns to shorten several queries. I can do a one-shot change to not use it, since the community have not opposed to this breaking of backward compatibility. Could you update the documentation to reflect the new behavior? > The Support for REGEX Column Broken in HIVE 0.13 > ------------------------------------------------ > > Key: HIVE-7097 > URL: https://issues.apache.org/jira/browse/HIVE-7097 > Project: Hive > Issue Type: Bug > Components: Query Processor > Affects Versions: 0.13.0 > Reporter: Sun Rui > > The Support for REGEX Column is OK in HIVE 0.12, but is broken in HIVE 0.13. > For example: > {code:sql} > select `key.*` from src limit 1; > {code} > will fail in HIVE 0.13 with the following error from SemanticAnalyzer: > {noformat} > FAILED: SemanticException [Error 10004]: Line 1:7 Invalid table alias or > column reference 'key.*': (possible column names are: key, value) > {noformat} > This issue is related to HIVE-6037. When set > "hive.support.quoted.identifiers=none", the issue will be gone. > I am not sure the configuration was intended to break regex column. But at > least the documentation needs to be updated: > https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Select#LanguageManualSelect-REGEXColumnSpecification > I would argue backward compatibility is more important. -- This message was sent by Atlassian JIRA (v6.2#6252)