[
https://issues.apache.org/jira/browse/CASSANDRA-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968322#comment-13968322
]
Edward Capriolo commented on CASSANDRA-6985:
--------------------------------------------
It is a bit of a stretch to say we dont know what the new api will look like.
Basically it will look like the current api but some classes will have private
members or some classes will pass an instance.
I really do not think one big commit is a great idea. Some of these things are
cosmetic, but some of them, like say a memtable with static synchronized could
create a bug that would be easy to miss in a sea of changes.
I think doing something like this cuts down the surface area of the big commit.
Also since not many of these classes have direct testing changing swaths of
them in one go seems scary to me.
But dif that is how you wqnt to handle it sit tight rfor about two weeks.
> ReadExecutors should not rely on static StorageProxy
> ----------------------------------------------------
>
> Key: CASSANDRA-6985
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6985
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Priority: Minor
> Fix For: 3.0
>
> Attachments: CASSANDRA_6985.1.patch
>
>
> All the Read Executor child classes require use of the Storage Proxy to carry
> out read. We can pass the StorageProxy along in the constructor.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
