@Samba, that's a very good point, I definitely do not expect all storage
engines provide exactly same features, and each storage engine should have
it's own strength and sweet spots as well. For features not supported by
certain storage engine, I think it should throw exceptions and fail the
reques
Another option would be to add a unsubscribe header, not sure if we already
do but I think that causes gmail/outlook to add a unsubscribe button
http://www.list-unsubscribe.com/
On Wed, Apr 26, 2017 at 11:24 AM, Eric Evans
wrote:
> On Wed, Apr 26, 2017 at 9:36 AM, Jake Farrell wrote:
> > moder
On Wed, Apr 26, 2017 at 9:36 AM, Jake Farrell wrote:
> moderators can also subscribe/unsubscribe people by sending an email using
> the following pattern
>
> example to unsubscribe u...@example.com:
> dev-unsubscribe-user=example@cassandra.apache.org
Doing so seem prone to abuse though.
--
On 04/26/2017 07:51 AM, Nate McCall wrote:
> I'm fine with that footer. I see that from other lists I'm on and it
> doesn't bother me.
https://issues.apache.org/jira/browse/INFRA-14017 request made.
--
Michael
some features may work with some storage engine but with others; for
example, storing large blobs may be efficient in one storage engine while
quite worse in another. perhaps some storage engines may want to SKIP some
features or add more.
if a storage engine skips a feature, how should the query
moderators can also subscribe/unsubscribe people by sending an email using
the following pattern
example to unsubscribe u...@example.com:
dev-unsubscribe-user=example@cassandra.apache.org
-Jake
On Wed, Apr 26, 2017 at 8:51 AM, Nate McCall wrote:
> > Is anyone opposed to including a footer
> 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 unsubscr
