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
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
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 cha
FWIW, I think it's possible to merge in a separate repository into a
subdirectory while keeping git history, but I don't know if the other way
will be possible if commits span other parts of the repo as well\* (which
will likely happen sooner or later). So a separate repo is a choice we can
backtra
Is there a roadmap or release schedule, so we can get an idea of what
the Reaper devs have planned for it?
Yours,
Murukesh Mohanan
On Tue, 28 Aug 2018 at 10:02, Jeff Jirsa wrote:
>
> Can you get all of the contributors cleared?
> What’s the architecture? Is it centralized? Is there
I think you're conflating two things here. There's the loss resulting from
using some operators, and loss involved in casting. Dividing an integer by
another integer to obtain an integer result can result in loss, but there's
no implicit casting there and no loss due to casting. Casting an integer
On Tue, 11 Dec 2018 at 10:51, Benedict Elliott Smith
wrote:
>
> On 10 Dec 2018, at 16:21, Ariel Weisberg wrote:
> >
> > Hi,
> >
> > RE #1, does this mean if you submit a ticket and you are not a contributor
> > you can't modify any of the fields including description or adding/removing
> > atta
Do we need to moderate heavily from the get-go, or should we implement all
this after a couple of trial calls to see how bad things are?
On Sat, 10 Aug 2019, 08:27 Scott Andreas, wrote:
> On the "virtual" side --
>
> I've spent some time this week reviewing how the Kubernetes community
> conduct
Don't we have a pr@ mailing list for these?
Yours,
Murukesh Mohanan
On Thu, 27 Feb 2020 at 03:56, GitBox wrote:
> dcapwell commented on a change in pull request #1: Introduce the extracted
> in-JVM DTest API
> URL:
> https://github.com/apache/cassandra-in-jvm
For clarification, when you say "this would clean the master
branch history", would the content directory be removed from past commits
using bfg or similar tools?
(I'm fine with either way; just curious.)
On Fri, 1 May 2020, 07:12 Anthony Grasso, wrote:
> Hi everyone,
>
> Thanks to hard work by
ld
discuss that at a later date, and move on with this proposal first.)
[1]: https://www.python.org/dev/peps/pep-8015/
[2]: https://www.python.org/dev/peps/pep-8016/
[3]: https://www.python.org/dev/peps/pep-0013/
[4]: https://wiki.php.net/rfc/abolish-narrow-margins
Yours,
Murukesh Mohanan
On Fri
ndoc clobbered the "MV select" part in
https://polandll.github.io/site/ASCIIDOC_POC/4.0/cassandra/cql/mvs.html
into the preceding note.
I wonder if it will be worth it to try rSt -> HTML (using the current build
tools) -> AsciiDoc (using Pandoc).
Yours,
Murukesh Mohanan
On Th
--
bar | 103
The property (which is also called `slow_query_log_timeout_in_ms`) shows up
in the system_schema table.
It seems that the file to modify would be
src/java/org/apache/cassandra/db/ColumnFamilyStoreCQLHelper.java, but I
didn't have any luck modifying it.
Any pointers, please?
--
Murukesh Mohanan,
Yahoo! Japan
---
bar | 103
The property (which is also called `slow_query_log_timeout_in_ms`) shows up
in the system_schema table.
It seems that the file to modify would be
src/java/org/apache/cassandra/db/ColumnFamilyStoreCQLHelper.java, but I
didn't have any luck modifying it.
Any pointers, please?
--
Murukesh Mohanan,
Yahoo! Japan
--
Murukesh Mohanan,
Yahoo! Japan
.
> >
> > Enjoy!
> >
> > [1]: (CHANGES.txt)
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.11
> > [2]: (NEWS.txt)
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.11
> > [3]: https://issues.apache.org/jira/browse/CASSANDRA
> >
>
> --
Murukesh Mohanan,
Yahoo! Japan
For CASSANDRA-13000 (slow query log analysis tool), I uploaded a script. If I
were to submit it as a patch, where should I place it? In bin/, or tools/bin/?
Since it is not directly concerned with running Cassandra, it seems like it
should be in tools/bin. Or, is there a third location?
I'm looking at CASSANDRA-13001 (pluggable slow query logging / handling). I
wrote a hacky patch, where my main goal was to touch as few files as possible -
so I did what I could within MonitoringTask, mostly. However, it seems that I
completely misunderstood what the feature request was. Jon Had
Le Mercredi 1 mars 2017 6h19, Murukesh Mohanan
> a écrit :
>
> I'm looking at CASSANDRA-13001 (pluggable slow query logging / handling). I
> wrote a hacky patch, where my main goal was to touch as few files as possible
> - so I did what I could within MonitoringTask
ust
> > removing it entirely, and replacing it with a link to the hosted docs.
> I'd
> > prefer we just remove it myself, makes things less confusing for
> newcomers.
> >
> > Does that seem reasonable to everyone?
>
--
Murukesh Mohanan,
Yahoo! Japan
Python recently made a switch to Github, and I was an interested onlooker. One
thing I found relevant to Cassandra was a new tool added by Larry Hastings,
called blurb (https://github.com/larryhastings/blurb):
> blurb is a tool designed to rid CPython core development of the scourge of
> Misc/N
.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
> --
Murukesh Mohanan,
Yahoo! Japan
The bin/cassandra script has an explanation
(https://github.com/apache/cassandra/blob/trunk/bin/cassandra#L24):
# As a convenience, a fragment of shell is sourced in order to set one or
# more of these variables. This so-called `include' can be placed in a
# number of locations and will be sear
What you complain about may be useful to someone else who might appreciate the
added flexibility. I'd personally be opposed to a single script, as I'd rather
not edit something that might cause conflicts or be overwritten on upgrades
(the location of the include and environment files being confi
urse, /bin/sh need not be bash, but I'm not sure
what the equivalent method would be for dash or other shells.
On 2017-07-12 00:15 (+0900), "Murukesh Mohanan"
wrote:
> What you complain about may be useful to someone else who might appreciate
> the added flexibility. I'
Related: https://issues.apache.org/jira/browse/CASSANDRA-10190
On 2017-07-20 18:17 (+0900), Tomas Repik wrote:
> Hi,
>
> the clock for Python 2.7 is ticking [1], and yes, there are still more than
> two years, but sooner or later cqlsh should be ported to Python 3. Is anybody
> already workin
odestyle/Default_1_.xml
> into my project and formatting seemed to work.
>
> However, I'm wondering what options/code.style.schemes.xml file is exactly
> used for? Could anyone please give me an idea if I need to configure this
> as well?
>
> Thanks,
> Preetika
>
>
> --
Murukesh Mohanan,
Yahoo! Japan
hours), out.xunit.xml is not appearing, nosetests process runs. I
> > killed java processes, but nothing changed for 2 hours - nosetests
> process
> > still runs, but files are unchanged.
> >
> > Any help would be appreciated,
> > Sergey
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
> --
Murukesh Mohanan,
Yahoo! Japan
I think videos were recorded of the NGCC 2017 sessions. Are those published
somewhere, and if not, will they be?
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.a
-30','
>> > 2017-10-31','2017-11-01','2017-11-02','2017-11-03','
>> > 2017-11-04','2017-11-05','2017-11-06', *'2017-11-07'*);
>> >
>> > *The 'values' column may have large j
I feel exposing them like as API has few advantages like, it
> > is more open (different types of clients can use) and more expressible
> > for request and response. Does the option of exposing such
> > functionality through API (REST) was considered at any point of time?
> > Are there any advantages or compelling reasons to stick with MBeans?
> >
> > Thanks!
> >
>
--
Murukesh Mohanan,
Yahoo! Japan
the online documentation in a
> separate repository that is managed as the current repository under the
> guidance of the Apache Cassandra PMC (Project Management Committee); and
> that in the new repository . . .
>
>
>
> Please see the jira. I hope it's a good answer to everyone.
>
>
>
> KennethBrotman
>
>
>
>
>
> --
Murukesh Mohanan,
Yahoo! Japan
repository
> > > > under the guidance of the Apache Cassandra PMC (Project Management
> > > > Committee); and that in the new repository . . .
> > > >
> > > >
> > > >
> > > > Please see the jira. I hope it's a good answer to everyone.
>
> --
> Eric Evans
> john.eric.ev...@gmail.com
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
> --
Murukesh Mohanan,
Yahoo! Japan
The complete error is needed. I get something similar if I hadn't run `pip3
install -r requirements.txt`:
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/_pytest/config.py", line 328, in
_getconftestmodules
return self._path2confmods[path]
KeyError: local('/
ages/py/_path/local.py",
> > > line 668, in pyimport
> > > __import__(modname)
> > > File "/usr/local/lib/python2.7/dist-packages/_pytest/assertion/
> > > rewrite.py", line 213, in load_module
> > > py.builtin.exec_(co, mod.__dict__)
>
34 matches
Mail list logo
