[ 
https://issues.apache.org/jira/browse/PHOENIX-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903593#comment-15903593
 ] 

Rajeshbabu Chintaguntla commented on PHOENIX-3727:
--------------------------------------------------

[~jamestaylor] [~samarthjain] My patch at PHOENIX-3351 added a regression that 
pkvalue of salted byte is replaced by multi tenant value or view index id when 
upsert select happen at client. This patch fixes that. Would be better to have 
ti 4.10.0.

> Upserts into salted table are failing in Phoenix-Calcite
> --------------------------------------------------------
>
>                 Key: PHOENIX-3727
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3727
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Rajeshbabu Chintaguntla
>            Assignee: Rajeshbabu Chintaguntla
>              Labels: calcite
>             Fix For: 4.10.0
>
>         Attachments: PHOENIX-3727.patch
>
>
> {noformat}
> testMutableTableIndexMaintanenceSaltedSalted(org.apache.phoenix.end2end.index.SaltedIndexIT)
>   Time elapsed: 4.607 sec  <<< ERROR!
> java.sql.SQLException: 2
>       at 
> org.apache.phoenix.end2end.index.SaltedIndexIT.testMutableTableIndexMaintanence(SaltedIndexIT.java:123)
>       at 
> org.apache.phoenix.end2end.index.SaltedIndexIT.testMutableTableIndexMaintanenceSaltedSalted(SaltedIndexIT.java:74)
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 2
>       at 
> org.apache.phoenix.end2end.index.SaltedIndexIT.testMutableTableIndexMaintanence(SaltedIndexIT.java:123)
>       at 
> org.apache.phoenix.end2end.index.SaltedIndexIT.testMutableTableIndexMaintanenceSaltedSalted(SaltedIndexIT.java:74)
> {noformat}
> This is because for salted tables we are changing column indexes within 
> UpsertCompiler#upsertSelect so with preparedStatements we increment 
> columnindexes by 1 so at some point of time we get 
> ArrayIndexOutOfBoundsException.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to