Mon, Jun 4, 2018 at 6:02 PM Lerh Chuan Low wrote:
> Hi Eric,
>
> I think it has something to do with the same reason it is disabled in DTCS:
> https://issues.apache.org/jira/browse/CASSANDRA-9234 can shed more light.
>
>
>
> On 5 June 2018 at 09:02, Eric Stevens wrote:
I'm trying to understand the reasoning behind this stanza in Time Windowed
Compaction Strategy's init:
https://github.com/apache/cassandra/blob/cassandra-3.0.15/src/java/org/apache/cassandra/db/compaction/TimeWindowCompactionStrategy.java#L63-L69
Reposted (and slightly reformatted) here for conven
The answer to Question 3 is "yes." One of the more subtle points about
tombstones is that Cassandra won't remove them during compaction if there
is a bloom filter on any SSTable on that replica indicating that it
contains the same partition (not primary) key. Even if it is older than
gc_grace, an
Let met just say that as an observer to this conversation -- and someone
who believes that compatibility, extensibility, and frankly competition
bring out the best in products -- I'm fairly surprised and disappointed
with the apparent hostility many community members have shown toward a
sincere att
Trying to coordinate it around the eclipse seems neat on the surface, but
practically it's probably not a great idea as most major cities along the
eclipse line have largely sold out their hotel rooms for that event.
On Fri, Jun 2, 2017 at 3:13 PM Carlos Rolo wrote:
> I might try to get some int
In the spirit of what Eric mentions, as a community member, I'm
enthusiastically +1 on the idea.
On Fri, Apr 21, 2017 at 9:28 AM, Eric Evans
wrote:
> On Fri, Apr 21, 2017 at 4:32 AM, benjamin roth wrote:
> > I am not a PMC member or sth but just my 2 cents:
>
> Somewhat off-topic here, but I'd
> Right now all the compaction strategies share the assumption that the data
> structure and layout on disk is fixed. With pluggable storage engine, we
> need to special case each compaction strategy (or at least the Abstract
> class of compaction strategy) for each engine.
As Ben points out, comp
Thu, Jan 5, 2017 at 3:17 PM, Eric Stevens wrote:
>
> > Thanks for the quick response.
> >
> > Looking at it, I'm not sure if it's quite the right thing for me. Maybe
> I
> > used the wrong terminology; it actually doesn't matter if the node is
&
1:03 PM Brandon Williams wrote:
> Probably want to do something like SystemKeyspace.bootstrapComplete()
>
> On Thu, Jan 5, 2017 at 1:58 PM, Eric Stevens wrote:
>
> > I'm working on a bug report in my Deleting Compaction Strategy project.
> >
> > Some of the provided
I'm working on a bug report in my Deleting Compaction Strategy project.
Some of the provided deletion strategies allow for a series of deletion
rules to be added to a CQL table, before compaction begins, a snapshot of
the current rules are read out of the CQL table and a deletion plan is
produced
Hi Sagar, you'll probably do better to ask this question on the users group
rather than the dev group. Dev groups are about internal development while
users groups are about using the software.
On Sat, Dec 17, 2016 at 5:08 AM Sagar Jambhulkar
wrote:
Hi,
Needed a suggestion for a schema query. I
We've had some luck with bulk known key reads with grouping by replica and
doing SELECT... WHERE key IN(...). Not compatible with all data models, but
it works well where we can get away with it.
As a more general purpose construct it makes sense to me. In our driver
layer we have abstracted batch
I agree with Benedict that we really shouldn't be getting into a legalese
debate on this subject, however "it didn't happen" has been brought up as a
hammer in this conversation multiple times, and I think it's important that
we put it to rest. It's pretty clear cut that projects are free to
disre
There are a few strengths of discussion on the ticketing system over
mailing lists. Mailing lists were fundamentally designed in the 1970's and
early 1980's, and the state of the art from a user experience perspective
has barely advanced since then.
* Mailing lists tend to end up with fragmented
; Melinda
>
> Sent from the Best-est iPhone
>
> > On Jul 5, 2016, at 10:27 AM, Eric Stevens wrote:
> >
> > Hi Melinda, these questions are probably better suited for the users
> group
> > rather than the dev group (which concerns itself with database internals
Hi Melinda, these questions are probably better suited for the users group
rather than the dev group (which concerns itself with database internals
and feature development). I'd recommend reposting over there.
On Mon, Jul 4, 2016 at 6:16 AM Melinda Zoe
wrote:
> Hello Group,
>
> I’ve been follow
The file format is SSTable:
http://wiki.apache.org/cassandra/ArchitectureSSTable
If you're getting into byte-level detail, I highly recommend you
familiarize yourself with the read and/or write path first, because that
deep in the bowels there are some non-obvious things going on where
Cassandra d
> Where else to discuss it? It should be constructive, yes. But we are all
> here to learn and grow with Cassandra. The original question is a good
> one. The direction it took was poor.
Agreed, hijacking unrelated threads is not good netizenry. There's
obviously a lot of strong opinions here, b
> A key portion of your software’s stack, a client driver to use it, exists
outside of Apache in separate communities. This is an inherent risk to the
project.
That's not at all obvious to me. The driver you're concerned about is not
under ASF, but it is Apache licensed, if DataStax took it in a
We have been working on filtering compaction for a month or so (though we
call it deleting compaction, its implementation is as a filtering
compaction strategy). The feature is nearing completion, and we have used
it successfully in a limited production capacity against DSE 4.8 series.
Our use ca
20 matches
Mail list logo
