[
https://issues.apache.org/jira/browse/PHOENIX-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913939#comment-13913939
]
James Taylor commented on PHOENIX-19:
-------------------------------------
Not sure exactly what you're asking exactly. Do you want to dynamically set a
property in a test, along the lines of what you do when you update your
hbase-sites.xml? Take a look at
org.apache.phoenix.end2end.index.SaltedIndexTest, the @BeforeClass method, as
that's what you'd want your test to do:
{code}
@BeforeClass
public static void doSetup() throws Exception {
Map<String,String> props = Maps.newHashMapWithExpectedSize(3);
// Don't split intra region so we can more easily know that the n-way
parallelization is for the explain plan
props.put(QueryServices.MAX_INTRA_REGION_PARALLELIZATION_ATTRIB,
Integer.toString(1));
// Forces server cache to be used
props.put(QueryServices.INDEX_MUTATE_BATCH_SIZE_THRESHOLD_ATTRIB,
Integer.toString(2));
// Drop the HBase table metadata for this test
props.put(QueryServices.DROP_METADATA_ATTRIB, Boolean.toString(true));
// Must update config before starting server
startServer(getUrl(), new ReadOnlyProps(props.entrySet().iterator()));
}
{code}
> Enhance JDBC connection of Phoenix to support connecting to a Secure HBase
> cluster.
> -----------------------------------------------------------------------------------
>
> Key: PHOENIX-19
> URL: https://issues.apache.org/jira/browse/PHOENIX-19
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Anil Gupta
> Labels: hbase, jdbc, secure
> Fix For: 3.0.0
>
>
> This is being moved from github
> https://github.com/forcedotcom/phoenix/issues/550 to JIRA.
> As per my discussion with James Taylor over here
> https://groups.google.com/forum/#!searchin/phoenix-hbase-user/secure$20cluster/phoenix-hbase-user/XHg2wXK4Hqo/qVTm92WLxUkJ
> and some other email exchanges. This ticket is to enhance the JDBC driver of
> phoenix so that user can pass keytab and principal to connect to a secure
> cluster.
> As per our discussion over email, could you please outline the changes
> required to make this enhancement?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
