[
https://issues.apache.org/jira/browse/CASSANDRA-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Morton updated CASSANDRA-2694:
------------------------------------
Description:
The JDBC driver uses CFMetaData.fromThrift(), it was calling
validateMemtableSettings() which used static methods on DatabaseDescriptor.
This causes cassandra.yaml to be loaded and means the client side needs access
to the file.
I think this needs to be fixed for 0.8, I have the patch.
**Updated** changed title from "remove references to DatabaseDescriptor in
CFMetaData"
was:
The JDBC driver uses CFMetaData.fromThrift(), it was calling
validateMemtableSettings() which used static methods on DatabaseDescriptor.
This causes cassandra.yaml to be loaded and means the client side needs access
to the file.
I think this needs to be fixed for 0.8, I have the patch.
Summary: stop JDBC driver from needing access to cassandra.yaml (was:
remove references to DatabaseDescriptor in CFMetaData)
> stop JDBC driver from needing access to cassandra.yaml
> ------------------------------------------------------
>
> Key: CASSANDRA-2694
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2694
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.0 beta 2
> Reporter: Aaron Morton
> Assignee: Aaron Morton
> Priority: Minor
> Fix For: 0.8.0
>
> Attachments: 0001-2694.patch
>
>
> The JDBC driver uses CFMetaData.fromThrift(), it was calling
> validateMemtableSettings() which used static methods on DatabaseDescriptor.
> This causes cassandra.yaml to be loaded and means the client side needs
> access to the file.
> I think this needs to be fixed for 0.8, I have the patch.
> **Updated** changed title from "remove references to DatabaseDescriptor in
> CFMetaData"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
