[ 
https://issues.apache.org/jira/browse/CASSANDRA-13579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042219#comment-16042219
 ] 

Amitkumar Ghatwal commented on CASSANDRA-13579:
-----------------------------------------------

[~jjirsa] -  Thanks for your review . I can change the comment from 
// Package protected for tests
to
// Package public for tests
Yes we are targeting trunk/4.0/ and 3.x. [~ReiOdaira] - please confirm this as 
well.

> Request to change the accessibility of `RowCacheSerializer` needed for 
> CAPi-Flash Enablement.
> ---------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-13579
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13579
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local Write-Read Paths
>            Reporter: Amitkumar Ghatwal
>            Assignee: Amitkumar Ghatwal
>              Labels: patch
>             Fix For: 4.x
>
>         Attachments: cassandra_change_RowCacheSerializer_accessibility.patch
>
>
> Hi All,
> [~ReiOdaira] , and I are working on creating a plugin for vendor specific 
> (CAPI-Flash ) implementation. As for our CAPI Flash enablement code, we are 
> now working on the plugin approach .And for creating the same we would need a 
> change in the accessibility of `RowCacheSerializer` . 
> Please refer to jira ticket/dev mails for reference : 
> 1) https://issues.apache.org/jira/browse/CASSANDRA-13486
> 2) http://www.mail-archive.com/[email protected]/msg11102.html
> [[email protected]] [~jjirsa] : FYI . Adding a patch to change the 
> accessibility. Let me know once the change will be merged in the mainline.
> PR raised : https://github.com/apache/cassandra/pull/117
> Thanks !!!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to