[
https://issues.apache.org/jira/browse/PHOENIX-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782777#comment-17782777
]
ASF GitHub Bot commented on PHOENIX-7038:
-----------------------------------------
jpisaac commented on PR #1682:
URL: https://github.com/apache/phoenix/pull/1682#issuecomment-1793114010
> In my ideal world we'd have some kind of whitelist for properties that are
known to be safe to override (or an inverse blacklist)
> (Of course users could still wreak havoc by modifying the hbase-site.xml
used by the client)
@stoty You are right, in the SFDC world, we do have such a whitelist in the
app. Something we can think of bringing down into the Phoenix layer.
> Implement Connection Query Service Metrics
> ------------------------------------------
>
> Key: PHOENIX-7038
> URL: https://issues.apache.org/jira/browse/PHOENIX-7038
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Mihir Monani
> Assignee: Mihir Monani
> Priority: Major
>
> With JDBC connection string, Clients can provide connection query service
> name. With use of Connection Query Service Name, different kinds of
> clients/use-case in single JVM can create connection with different
> configuration like time-outs, retries, sleep between retries.
> Connection URL Example : jdbc:phoenix:localhost:2181:CONN_QUERY_SERVICE_2
> Here CONN_QUERY_SERVICE_2 is connection query service name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
