[ https://issues.apache.org/jira/browse/PHOENIX-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893254#comment-15893254 ]
Sergey Soldatov edited comment on PHOENIX-3346 at 3/2/17 11:39 PM: ------------------------------------------------------------------- tried that already when initially did split for MR/Tez :) But will check it again just in case. Tests start well and create HBase minicluster but not going further. Actually it seems that the problem is how failsafe and surefire run tests. Failsafe is using jar artifacts while surefire is using compiled classes. The rest is supposed to be the same. Since the hive jar built using assembly plugin there is a chance that some of META-INF stuff cause that problem. Just need some time to debug it. was (Author: sergey.soldatov): tried that already :) Tests start well and create HBase minicluster but not going further. Actually it seems that the problem is how failsafe and surefire run tests. Failsafe is using jar artifacts while surefire is using compiled classes. The rest is supposed to be the same. Since the hive jar built using assembly plugin there is a chance that some of META-INF stuff cause that problem. Just need some time to debug it. > Hive PhoenixStorageHandler doesn't work well with column mapping > ---------------------------------------------------------------- > > Key: PHOENIX-3346 > URL: https://issues.apache.org/jira/browse/PHOENIX-3346 > Project: Phoenix > Issue Type: Bug > Reporter: Sergey Soldatov > Assignee: Sergey Soldatov > Priority: Blocker > Labels: HivePhoenix > Fix For: 4.10.0 > > Attachments: PHOENIX-3346-1.patch > > > If column mapping is used during table creation, the hive table becomes > unusable and throws UnknownColumn exception. > There are several issues in the current implementation: > 1. During table creation mapping doesn't applies to primary keys > 2. During select query building no mapping happen > 3. PhoenixRow should have backward mapping from phoenix column names to hive > names. -- This message was sent by Atlassian JIRA (v6.3.15#6346)