We're shadowing some production traffics to a Rocksandra cluster (
https://github.com/Instagram/cassandra/tree/rocks_3.0), the P99 latency is
significantly improved (about 6x for read, 12x for write). Here are the
test details:
https://docs.google.com/document/d/1cEM8ZqB5tOYVdsh1LpqSZ-eLasumWfzn_T
Kurt's proposal to freeze the 2.7 implementation and offer a Python 3
implementation alongside it appeals to my desire to free ourselves of
design choices made for the sake of Python 2/3 cross compatibility. It also
has the advantage of keeping Python 2.7 users on a time tested product.
On the dow
Seems pretty straightforward to me. Create a python 3 version as soon as
possible and make it available, keep the python 2.7 version as default
until the next major release after 4.0 (assuming around/after python 2.7
EOL), then switch default and leave continued support for 2.7 cqlsh up to
the comm
Hi Murukesh
Here is my Cassandra.yaml file in GitHub gist
https://gist.github.com/vvinayreddy/bdaf6c54fa426256bfca69bfca32c0a6
Thanks and Regards
Vinay Kumar Vongour
-Original Message-
From: Murukesh Mohanan
Sent: Friday, June 01, 2018 1:10 PM
To: dev@cassandra.apache.org
Subject: Re:
All for using six and supporting both. Sorry, I read your initial email as
wanting to drop support for 2 at the end of the year.
> On Jun 1, 2018, at 1:01 PM, Jonathan Haddad wrote:
>
> And that's why I said supporting both with six is the right path
> forward, later dropping support for 2. I'
If anything, riding on their coattails will mean we'll drop support a year
or two later, after we see their experiences - which will be nicely in line
with the Python upstream EOL date of 2020. (Of course, distro vendors will
provide support after that, say till 2025.) So perhaps 2020 should be a
r
Attachments don't work well with mailing lists. You might want to post the
yaml to a GitHub gist or some other public pastebin site and provide the
link instead. Also, I think this topic is more suited to the user@ mailing
list rather then this development-focused mailing list.
On Sat, Jun 2, 2018
And that's why I said supporting both with six is the right path
forward, later dropping support for 2. I'm not advocating we drop 2
support now, and I'm not asking for any sort of commitment. I didn't
think adding support for 3 would be so controversial.
On Fri, Jun 1, 2018 at 9:40 AM Jeremiah D
The community of people doing python development and the community of people
running Cassandra servers are not the same. I am not fine riding the coat
tails of libraries used in python development. As others have stated we need
to be following the lead of the OS vendors that people will be dep
Both can work. I did a lot of the work on the port of the Python
driver's object mapper (formerly cqlengine) to Python 3. It's
reasonably straightforward if you use the six library.
Both pandas and numpy are dropping support for Python 2 at the end of
this year. I'm fine with riding on their co
Support for, but not the very script, right? Because, as gently pointed
out by several realists here, Python 2 is far from dead and arguably
still the majority usage. That's only just now beginning to change. I
think it will be more than 2 years before people begin asking what
Python 2 was.
Hi all
Hope you all doing good
I am working on benchmarking Cassandra using Cassandra stress tool and results
are not very impressive. I really some help to tune Cassandra to get great
results. Below is my environment and test results and attached is
Cassandra.yaml I am using for the test.
I a
Supporting both as a next step is logical, removing support for 2 in the
next year or two seems reasonable enough. Gotta rip the band aid off at
some point.
On Fri, Jun 1, 2018 at 2:34 AM Michael Burman wrote:
> Hi,
>
> Deprecating in this context does not mean removing it or it being
> replaced
Hi,
Deprecating in this context does not mean removing it or it being
replaced by 3 (RHEL 7.x will remain with Python 2.x as default). It
refers to future versions (>7), but there are none at this point. It
appears Ubuntu has deviated from Debian in this sense, but Debian has
not changed yet
On 2018/06/01 07:40:04, Michael Burman wrote:
>
> IIRC, there's no major distribution yet that defaults to Python 3 (I
> think Ubuntu & Debian are still defaulting to Python 2 also). This will
> happen eventually (maybe), but not yet. Discarding Python 2 support
> would mean more base-OS work
Hi,
Should definitely be cross compatible with Python 2/3. Most of the
systems (such as those running on RHEL7 or distros based on it like
CentOS) are shipping with 2.7 only by default. And these systems are
probably going to be used for a long time to run Cassandra.
IIRC, there's no major d
16 matches
Mail list logo
