Jason Brown updated CASSANDRA-14395:
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)


I made two minor changes on commit:
 * made {{logger}} instances {{static final}}
 * removed the jolokia license file. [~djoshi3] sorry if I confused you, as 
what i meant to say is that if we ship the jar in-tree, we should have the 
license file, as well (like we do in cassandra proper). However, this raises 
the question of how to correctly address transitive dependencies that we don't 
ship in-tree. Admittedly, I've been doing it "the cassandra way" forĀ a long 
time (with jars in-tree), so I'm not sure how properly include licenses with a 
maven-like system. I'll create a followup ticket to figure it out.

Otherwise, this is a good first step toward shipping a working sidecar. 
Committed as sha {{a15ed267d1977e38ba36d061139839fad7b865f2}}. Thanks, 

> C* Management process
> ---------------------
>                 Key: CASSANDRA-14395
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14395
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Dinesh Joshi
>            Assignee: Dinesh Joshi
>            Priority: Major
>         Attachments: Looking towards an Official Cassandra Sidecar - 
> Netflix.pdf
> I would like to propose amending Cassandra's architecture to include a 
> management process. The detailed description is here: 
> https://docs.google.com/document/d/1UV9pE81NaIUF3g4L1wxq09nT11AkSQcMijgLFwGsY3s/edit
> I'd like to propose seeding this with a few simple use-cases such as Health 
> Checks, Bulk Commands with a simple REST API interface. 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to