[
https://issues.apache.org/jira/browse/PHOENIX-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176163#comment-14176163
]
Hudson commented on PHOENIX-1242:
---------------------------------
FAILURE: Integrated in Phoenix | 3.0 | Hadoop1 #267 (See
[https://builds.apache.org/job/Phoenix-3.0-hadoop1/267/])
PHOENIX-1242: ArrayoutofBoundException Phoenix mapping to exisiting Hbase
(Alicia Ying Shu) (jeffreyz: rev 8aeb7a7a70ae6f8033284a911a367c8498e7ed83)
* phoenix-core/src/main/java/org/apache/phoenix/schema/PDataType.java
*
phoenix-core/src/test/java/org/apache/phoenix/schema/MappingTableDataTypeTest.java
> ArrayoutofBoundException Phoenix mapping to exisiting Hbase
> -----------------------------------------------------------
>
> Key: PHOENIX-1242
> URL: https://issues.apache.org/jira/browse/PHOENIX-1242
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.0.0
> Reporter: nicolas maillard
> Assignee: Alicia Ying Shu
> Priority: Minor
> Fix For: 5.0.0, 4.2, 3.2
>
> Attachments: Phoenix-1242-V1.patch, phoenix-1242.patch
>
>
> In a Phoenix mapping to an existing Hbase Table in case of mis-typing say try
> to cast a long an actual string type, Phoenix will break with:
> java.lang.ArrayIndexOutOfBoundsException: 324
> This is a user mis-use but the error message is misleading. The problem is
> trying to copy a string to a long a fixed Bytes[] in long decodeLong.
> Maybe a test to check if the translation is possible and a type error if size
> don't match would provide for a more explicit error message for the user to
> understand what he did wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
