Ekaterina, thank you for spearheading JDK17 support for Apache Cassandra! Exciting to get to this point.- ScottOn Jul 24, 2023, at 7:11 PM, Ekaterina Dimitrova wrote:Good news! After run #1638-39 you should not see anything else failing than SSLFactory test class. This known issue will be fixed
Good news!
After run #1638-39 you should not see anything else failing than SSLFactory
test class. This known issue will be fixed by potentially adding bounty
castle. More info in CASSANDRA-17992 and this netty PR:
https://github.com/netty/netty/issues/10317
We can probably mark the test class
To clarify the repair solution timing, the one we have listed in the
article is not the recently developed one. We were hitting some
high-priority production challenges back in early 2018, and to address
that, we developed and rolled out the solution in production in just a few
months. The
Hi all,
There has been a last minute change in topic for the July Contributor
Meeting!
Caleb Rackliffe will be talking about CEP-7: Storage Attached Index, rather
than the previously advertised CEP-15. He'll talk through the history of
CEP-7, look at the current work as it approaches merge into
Hi German,
The goal is always to backport our learnings back to the community. For
example, I have already successfully backported the following two
enhancements/bug fixes back to the Open Source Cassandra, which are
described in the article. I am already currently working on open-source a
few
All,
We had a brief discussion in [2] about the Uber article [1] where they talk
about having integrated repair into Cassandra and how great that is. I
expressed my disappointment that they didn't work with the community on that
(Uber, if you are listening time to make amends ) and it turns
Ninja fix was required for Jenkins, new build started #1636
On Mon, 24 Jul 2023 at 15:42, Ekaterina Dimitrova
wrote:
> Done!
>
> All commits from 18255 are in.
> The first run to monitor will be in Jenkins #1635
>
> There will be still fixes to be applied for some unit and in-jvm tests
> that
Done!
All commits from 18255 are in.
The first run to monitor will be in Jenkins #1635
There will be still fixes to be applied for some unit and in-jvm tests that
were pending on the drop but I will do it when I see Jenkins kicking in
this run properly. (Which are those can be seen in
Thank you everyone! Voting passes with 8 +1s and no -1. Closing this thread
now.
Jyothsna Konisa.
On Sat, Jul 22, 2023 at 3:14 AM Brandon Williams wrote:
> +1
>
> Kind Regards,
> Brandon
>
> On Fri, Jul 21, 2023 at 11:58 AM Jyothsna Konisa
> wrote:
> >
> > Hi Everyone!
> >
> > I would like to
Starting commits for 18255. Please put on hold any trunk commits. I will
let you know when it is done. Thank you
On Mon, 24 Jul 2023 at 11:29, Ekaterina Dimitrova
wrote:
> Hi everyone,
>
> Happy Monday!
>
> I am working on dropping JDK 8 and adding JDK17 on trunk in both CI
> systems today.
>
The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.1.3.
Apache Cassandra is a fully distributed database. It is the right choice when
you need scalability and high availability without compromising performance.
http://cassandra.apache.org/
Downloads of source
Hi everyone,
Happy Monday!
I am working on dropping JDK 8 and adding JDK17 on trunk in both CI systems
today.
This requires numerous patches in a few repos so you will be seeing more
failures in CI throughout the day today, but it shouldn’t be anything more
爛 than what we have listed in the
> `column CONTAINS term`. Contains is used by both Java and Python for
> substring searches, so at least some users will be surprised by term-based
> behavior.
I wonder whether users are in their "programming language" headspace or in
their "querying a database" headspace when interacting with
I have a strong preference not to use the name of an SQL operator, since it precludes us later providing the SQL standard operator to users.What about CONTAINS TOKEN term? Or CONTAINS TERM term?On 24 Jul 2023, at 13:34, Andrés de la Peña wrote:`column = term` is definitively problematic because
`column = term` is definitively problematic because it creates an ambiguity
when the queried column belongs to the primary key. For some queries we
wouldn't know whether the user wants a primary key query using regular
equality or an index query using the analyzer.
`term_matches(column, term)`
Hi all,
With phase 1 of SAI wrapping up, I’d like to start the ball rolling on
aligning around phase 2 features.
In particular, we need to nail down the syntax for doing non-exact string
matches. We have a proof of concept that includes full Lucene analyzer and
filter functionality – just the
The vote passes with three binding and one non-binding +1s.
https://lists.apache.org/thread/8ot3wjc88k0rhx1m9m58k0bp4msbjw6w
I have been thinking about tiered storage wherein infrequently used data
can be moved off to slow (cold) storage (like S3). I think that CEP-17 in
conjunction with CEP-21 provides an opportunity for an interesting approach.
As I understand it CEP-17 clarified the SSTables interface(s) so that
18 matches
Mail list logo
