You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2021/11/11 20:25:00 UTC

[jira] [Comment Edited] (PHOENIX-6561) Allow pherf to intake phoenix Connection properties as argument.

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

Geoffrey Jacoby edited comment on PHOENIX-6561 at 11/11/21, 8:24 PM:
---------------------------------------------------------------------

[~jisaac] [~lokiore] - Reopening this JIRA because the 4.x patch is causing a build error. (PhoenixUtil is using a HashMap without importing it). Could you please fix when you get a minute? 


was (Author: gjacoby):
[~jisaac] [~lokiore] - Reopening this JIRA because the 4.x patch is causing a build error. (PhoenixUtil is using a HashMap without importing it)

> Allow pherf to intake phoenix Connection properties as argument.
> ----------------------------------------------------------------
>
>                 Key: PHOENIX-6561
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6561
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Lokesh Khurana
>            Assignee: Lokesh Khurana
>            Priority: Minor
>             Fix For: 4.17.0, 5.2.0, 4.16.2, 5.1.3
>
>
> Currently pherf doesn't allow connection properties to be passed as arguments, it allows for some cases through scenario files, but for dynamic properties selection that might not work, also for WriteWorkload no property is being allowed to pass during connection creation.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)