Re: Way to unsubscribe from mailing lists

2017-04-25 Thread Jeff Jirsa
+1 vote to add it 

-- 
Jeff Jirsa


> On Apr 25, 2017, at 6:26 PM, Michael Shuler  wrote:
> 
>> On 04/25/2017 12:52 PM, Mark Thomas wrote:
>>> On 25/04/17 16:11, Michael Shuler wrote:
>>> Many lists include a footer that have unsub info - does ezmlm support
>>> footer append? I wouldn't mind it, if it helps users, and it seems
>>> simpler than trying to filter random messages.
>> 
>> Yes it does. And the default footer includes unsubscribe info.
> 
> Is anyone opposed to including a footer on all the
> *@cassandra.apache.org lists? I think this could be helpful.
> 
> I've appended a default-ish ezmlm "trailer text" that I found in a doc.
> 
> -- 
> Kind regards,
> Michael
> 
> ---
>  To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>  For additional commands, e-mail: dev-h...@cassandra.apache.org


Re: Way to unsubscribe from mailing lists

2017-04-25 Thread Michael Shuler
On 04/25/2017 12:52 PM, Mark Thomas wrote:
> On 25/04/17 16:11, Michael Shuler wrote:
>> Many lists include a footer that have unsub info - does ezmlm support
>> footer append? I wouldn't mind it, if it helps users, and it seems
>> simpler than trying to filter random messages.
> 
> Yes it does. And the default footer includes unsubscribe info.

Is anyone opposed to including a footer on all the
*@cassandra.apache.org lists? I think this could be helpful.

I've appended a default-ish ezmlm "trailer text" that I found in a doc.

-- 
Kind regards,
Michael

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


Re: Cassandra on RocksDB experiment result

2017-04-25 Thread Dikang Gu
I created several tickets to start the discussion, please free feel to
comment on the JIRAs. I'm also open for suggestions about other efficient
ways to discuss it.

https://issues.apache.org/jira/browse/CASSANDRA-13474
https://issues.apache.org/jira/browse/CASSANDRA-13475
https://issues.apache.org/jira/browse/CASSANDRA-13476

Thanks
Dikang.

On Mon, Apr 24, 2017 at 9:53 PM, Dikang Gu  wrote:

> Thanks everyone for the feedback and suggestions! They are all very
> helpful. I'm looking forward to having more discussions about the
> implementation details.
>
> As the next step, we will be focus on three areas:
> 1. Pluggable storage engine interface.
> 2. Wide column support on RocksDB.
> 3. Streaming support on RocksDB.
>
> I will go ahead and create some JIRAs, to start the discussion about
> pluggable storage interface, and how to plug RocksDB into Cassandra.
>
> Please let me know your thoughts.
>
> Thanks!
> Dikang.
>
> On Mon, Apr 24, 2017 at 12:42 PM, Patrick McFadin 
> wrote:
>
>> Dikang,
>>
>> First I want to thank you and everyone else at Instragram for the
>> engineering talent you have devoted to the Cassandra project. Here's yet
>> another great example.
>>
>> He's going to hate me for dragging him into this, but Vijay Parthasarathy
>> has done some exploratory work before on integrating non-java storage to
>> Cassandra. Might be helpful person to consult.
>>
>> Patrick
>>
>>
>>
>> On Sun, Apr 23, 2017 at 4:25 PM, Nate McCall  wrote:
>>
>> > > Please take a look and let me know your thoughts. I think the biggest
>> > > latency win comes from we get rid of most Java garbages created by
>> > current
>> > > read/write path and compactions, which reduces the JVM overhead and
>> makes
>> > > the latency to be more predictable.
>> > >
>> >
>> > I want to put this here for the record:
>> > https://issues.apache.org/jira/browse/CASSANDRA-2995
>> >
>> > There are some valid points in the above about increased surface area
>> > and end-user confusion. That said, just under six years is a long
>> > time. I think we are a more mature project now and I completely agree
>> > with others about the positive impacts of testability this would
>> > inherently provide.
>> >
>> > +1 from me.
>> >
>> > Dikang, thank you for opening this discussion and sharing your efforts
>> so
>> > far.
>> >
>>
>
>
>
> --
> Dikang
>
>


-- 
Dikang


Re: Way to unsubscribe from mailing lists

2017-04-25 Thread Dave Lester
If there's community consensus that this would help, mailing list footers can 
be added via an INFRA request. Here are some example requests from Hadoop and 
Spark:

https://issues.apache.org/jira/browse/INFRA-10725
https://issues.apache.org/jira/browse/INFRA-8051

Dave

On 2017-04-25 08:11 (-0700), Michael Shuler  wrote: 
> On 04/25/2017 09:56 AM, Eric Evans wrote:
> > On Tue, Apr 25, 2017 at 2:56 AM, Alain RODRIGUEZ  wrote:
> >> Should / could we have INFRA automatically unsubscribing people sending
> >> those messages? I believe this would be the best solution, as more people
> >> mentioned a year ago. I would like at least those messages to be filtered,
> >> even that is a bit more selfish as it would not end the subscription for
> >> the person sending the message, it would at least reduce the noise.
> > 
> > I'd be in favor of filtering them from the list, with an
> > auto-responder that explained *why* it wasn't delivered, and what they
> > need to do to unsubscribe (and maybe setting the reply-to to
> > {list}-unsubscribe@cassandra.a.o).
> > 
> > I'm fairly certain the list software doesn't come ready to do this
> > though; I imagine the response from INFRA will be something like
> > "patches welcome", so we should be ready to rollup our sleeves.
> 
> Many lists include a footer that have unsub info - does ezmlm support
> footer append? I wouldn't mind it, if it helps users, and it seems
> simpler than trying to filter random messages.
> 
> -- 
> Michael
> 
> 


Re: Way to unsubscribe from mailing lists

2017-04-25 Thread Mark Thomas
On 25/04/17 16:11, Michael Shuler wrote:
> Many lists include a footer that have unsub info - does ezmlm support
> footer append? I wouldn't mind it, if it helps users, and it seems
> simpler than trying to filter random messages.

Yes it does. And the default footer includes unsubscribe info.

Mark



Re: Way to unsubscribe from mailing lists

2017-04-25 Thread Salih Gedik
For some reason I don't really think that they are real persons who want to 
unsubscribe. I feel like they are classic spam pharmacy and advertising better 
uptime for C*

Cheers

Salih Gedik




Salih Gedik

>> On 25 Apr 2017, at 17:56, Eric Evans  wrote:
>> 
>> On Tue, Apr 25, 2017 at 2:56 AM, Alain RODRIGUEZ  wrote:
>> Should / could we have INFRA automatically unsubscribing people sending
>> those messages? I believe this would be the best solution, as more people
>> mentioned a year ago. I would like at least those messages to be filtered,
>> even that is a bit more selfish as it would not end the subscription for
>> the person sending the message, it would at least reduce the noise.
> 
> I'd be in favor of filtering them from the list, with an
> auto-responder that explained *why* it wasn't delivered, and what they
> need to do to unsubscribe (and maybe setting the reply-to to
> {list}-unsubscribe@cassandra.a.o).
> 
> I'm fairly certain the list software doesn't come ready to do this
> though; I imagine the response from INFRA will be something like
> "patches welcome", so we should be ready to rollup our sleeves.
> 
> 
> -- 
> Eric Evans
> john.eric.ev...@gmail.com



Re: Way to unsubscribe from mailing lists

2017-04-25 Thread Michael Shuler
On 04/25/2017 09:56 AM, Eric Evans wrote:
> On Tue, Apr 25, 2017 at 2:56 AM, Alain RODRIGUEZ  wrote:
>> Should / could we have INFRA automatically unsubscribing people sending
>> those messages? I believe this would be the best solution, as more people
>> mentioned a year ago. I would like at least those messages to be filtered,
>> even that is a bit more selfish as it would not end the subscription for
>> the person sending the message, it would at least reduce the noise.
> 
> I'd be in favor of filtering them from the list, with an
> auto-responder that explained *why* it wasn't delivered, and what they
> need to do to unsubscribe (and maybe setting the reply-to to
> {list}-unsubscribe@cassandra.a.o).
> 
> I'm fairly certain the list software doesn't come ready to do this
> though; I imagine the response from INFRA will be something like
> "patches welcome", so we should be ready to rollup our sleeves.

Many lists include a footer that have unsub info - does ezmlm support
footer append? I wouldn't mind it, if it helps users, and it seems
simpler than trying to filter random messages.

-- 
Michael



Re: Way to unsubscribe from mailing lists

2017-04-25 Thread Eric Evans
On Tue, Apr 25, 2017 at 2:56 AM, Alain RODRIGUEZ  wrote:
> Should / could we have INFRA automatically unsubscribing people sending
> those messages? I believe this would be the best solution, as more people
> mentioned a year ago. I would like at least those messages to be filtered,
> even that is a bit more selfish as it would not end the subscription for
> the person sending the message, it would at least reduce the noise.

I'd be in favor of filtering them from the list, with an
auto-responder that explained *why* it wasn't delivered, and what they
need to do to unsubscribe (and maybe setting the reply-to to
{list}-unsubscribe@cassandra.a.o).

I'm fairly certain the list software doesn't come ready to do this
though; I imagine the response from INFRA will be something like
"patches welcome", so we should be ready to rollup our sleeves.


-- 
Eric Evans
john.eric.ev...@gmail.com


Re: Guidelines on testing

2017-04-25 Thread Stefan Podkowinski
I don't see any reasons not to make this part of our guidelines. The
idea of having a list of what should be tested in each kind of test
makes sense. I also like the examples how to improve tests dealing with
global state.

Some of the integration test cases, such as "dry
start"/"restart"/"shutdown"/"upgrade", could use some further
description and how-to examples. Are there any existing tests we can
link for reference?

We also already have a testing related page in our documentation:
http://cassandra.apache.org/doc/latest/development/testing.html
Not sure if it would make sense to merge or create an additional document.


On 24.04.2017 18:13, Blake Eggleston wrote:
> About a month ago, in the ‘Code quality, principles and rules’ thread, I’d 
> proposed adding some testing standards to the project in lieu of revisiting 
> the idea of removing singletons. The idea was that we could drive incremental 
> improvement of the test coverage and testability situation that could be 
> applied in day to day work. I’ve pushed a first draft to my repo here:
> 
> https://github.com/bdeggleston/cassandra/blob/testing-doc/TESTING.md
> 
> Please take a look and let me know what you think. With the blessing of the 
> pmc, I’d like this, or something like it, to be adopted as the reference for 
> contributors and reviewers when deciding if a contribution is properly tested.
> 
> Blake
> 


Way to unsubscribe from mailing lists

2017-04-25 Thread Alain RODRIGUEZ
Hi,

I am seeing a lot of people trying (and failing) to unsubscribe from
Cassandra mailing lists lately by sending an email to the list with
"unsubscribe" message either in the subject or the body of the email
instead of writing an email to dev-unsubscr...@cassandra.apache.org or
user-unsubscr...@cassandra.apache.org.

Last year I tried to template an answer for those messages, but it was
annoying to answer all the people (I am not a robot) and my message was
considered to be "too French". So I stopped. But at least it opened an
interesting discussion and suggestions were made but never applied
http://www.mail-archive.com/user@cassandra.apache.org/msg48355.html.

I know this 'spam' it is not a big deal, but seeing this kind of message
regularly for years is somehow frustrating me and this useless noise is
annoying, it makes more thread on busy mailing lists. Some unsubscribe
messages are even in the middle of other threads. On the other side I
believe it might be quite easy to 'fix'.

Should / could we have INFRA automatically unsubscribing people sending
those messages? I believe this would be the best solution, as more people
mentioned a year ago. I would like at least those messages to be filtered,
even that is a bit more selfish as it would not end the subscription for
the person sending the message, it would at least reduce the noise.

How do I make this actionable, should I create a JIRA? Is this message
enough for someone to take over? Should this go through a vote?

C*heers,
---
Alain Rodriguez - @arodream - al...@thelastpickle.com
France

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com