You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Ethan Wang (JIRA)" <ji...@apache.org> on 2017/09/07 06:24:00 UTC
[jira] [Issue Comment Deleted] (PHOENIX-4150) Adding a policy
filter to whitelist the properties that allow to be passed to Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Wang updated PHOENIX-4150:
--------------------------------
Comment: was deleted
(was: Per we discussed [~tdsilva]
1, forEach part is an example in the comments for instruction. I can refactor them if needed.
2, so PropertyPolicy is following three other service override factory providers. Non of them has tests written. I wonder what's the best way of testing them. [~jamestaylor])
> Adding a policy filter to whitelist the properties that allow to be passed to Phoenix
> -------------------------------------------------------------------------------------
>
> Key: PHOENIX-4150
> URL: https://issues.apache.org/jira/browse/PHOENIX-4150
> Project: Phoenix
> Issue Type: Bug
> Reporter: Ethan Wang
> Assignee: Ethan Wang
> Attachments: PHOENIX-4150-v1.patch, PHOENIX-4150-v2.patch
>
>
> Adding a policy filter to whitelist the properties that allow to be passed to Phoenix.
> Feature proposal:
> When user getting phoenix connection via
> Connection conn = DriverManager.getConnection(connectionString, properties);
> A properties whitelist policy will essentially check each properties that passed in (likely happen at PhoenixDriver.java), so that the un-allowed property will result in an exception been thrown.
> Similar to HBaseFactoryProvider, proposing have a interface for whitelist policy and a default impl that will by default allow all properties. User can override the impl for this interface to start using whitelist feature
> [~jamestaylor] [~alexaraujo]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)