You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Cody Marcel (JIRA)" <ji...@apache.org> on 2015/10/19 22:35:28 UTC

[jira] [Commented] (PHOENIX-2337) Pherf - Prefix values override rule values for writes

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

Cody Marcel commented on PHOENIX-2337:
--------------------------------------

[~jfernando_sfdc] Any thoughts here? I think we would want any data values generated to match the rule. I don't think we would want the prefix to override.

This test shows we get back the correct rule. If you actually step into the value generation you can see it's also correct. It generates a random sequential string with post-pended chars to equal length of 8 (001jYjbu). Then It hist the prefix notation and just applies that to the value before return. This makes the resulting data length 15 instead of the expected 8.

I would think that if you want a prefix and you set a length, it would need to have enough room or it should truncate the string to follow the rule.

> Pherf - Prefix values override rule values for writes
> -----------------------------------------------------
>
>                 Key: PHOENIX-2337
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2337
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.6.0
>            Reporter: Cody Marcel
>         Attachments: PHOENIX-2337.patch
>
>
> When data is generated the value is first created by the rule correctly, then the prefix is applied. This leads to a final result that is different than the expected rule.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)