+1
On Thu, Aug 27, 2020 at 1:31 PM Jasonstack Zhao Yang
wrote:
>
> +1
>
> On Thu, 27 Aug 2020 at 04:52, Ekaterina Dimitrova
> wrote:
>
> > +1
> >
> > On Wed, 26 Aug 2020 at 16:48, Caleb Rackliffe
> > wrote:
> >
> > > +1
> > >
> > >
> > >
> > > On Wed, Aug 26, 2020, 3:45 PM Patrick McFadin
> >
> About space efficiency, one of the biggest drawback of SASI was the huge
space required for index structure when using CONTAINS logic because of the
decomposition of text columns into n-grams. Will SAI suffer from the same
issue in future iterations ?
SAI does not have specific ngram support atm
+1 for the migration.
Thanks for owning and leading this, Sam
On Fri, Jan 4, 2019 at 02:58 Sam Tunnicliffe wrote:
> As per the announcement on 7th December 2018[1], ASF infra are planning to
> shutdown the service behind git-wip-us.apache.org and migrate all
> existing repos to gitbox.apache.or
opted out of)
3. GitHub activity can be relayed to IRC channels on the Freenode
network.
I think we probably want to enable #1 & #2 to maintain parity with what we
have already with the main cassandra repo.
Thanks,
-Jason
[1] https://gitbox.apache.org/
[2] https://reference.apache.org/pmc/github
It looks like we have consensus to move forward with the sidecar
I will be shepherding the project, and to that end, I'll create a repo
against which we can start working.
Thanks,
-Jason
On Fri, Nov 30, 2018 at 7:54 AM sankalp kohli
wrote:
> If no one has more feedback, we should crea
+1.
On Mon, Dec 17, 2018 at 7:36 AM Michael Shuler
wrote:
> +1
>
> --
> Michael
>
> On 12/17/18 9:19 AM, Benedict Elliott Smith wrote:
> > I propose these changes <
> https://cwiki.apache.org/confluence/display/CASSANDRA/JIRA+Workflow+Proposals>*
> to the Jira Workflow for the project. The vote
To clarify my position: Github PRs are great for *reviewing* code, and the
commentary is much easier to follow imo. But for *merging* code, esp into
our multi-branch strategy, PRs don't fit well, unless there's some
technique I and perhaps others are unaware of.
On Thu, Dec 13, 2018 at 9:47 AM Ari
I'm with Sylvain and Aleksey. Our multi-branch strategy does not work well
(if at all) with Github PR-style workflows (and, yes, I and most c*
maintainers have played this game). The cassandra-dtests repo is different
as we don't really branch there, so might be fine for Github PRs - except
for the
JIRA, and we'll go from
there? In the meantime, maybe enable the JDK's SSL debugging [2] on the 3.x
node to see exactly what it is trying to do? Also, you can enable wire
tracing on the 4.0 node by setting this value to true [3] and recompiling.
We can followup further in the jira.
RA-14746>
CASSANDRA-13254 <https://issues.apache.org/jira/browse/CASSANDRA-13254>
CASSANDRA-14606 <https://issues.apache.org/jira/browse/CASSANDRA-14606>
Thanks,
-Jason
On Tue, Sep 25, 2018 at 4:05 AM, Benedict Elliott Smith wrote:
> Do we want to manage more versions than we do
Hi Robert,
Thanks for taking on this work. Is this message a heads up that a patch is
coming/complete, or to spawn a discussion about including this in 4.0?
Thanks,
-Jason
On Tue, Sep 11, 2018 at 2:32 AM, Robert Stupp wrote:
> In an effort to clean up our hygiene and limit the dependenc
+1 to Jon's sentiment. Further, perhaps we should use that time after
GA'ing 4.0 to poll our users what they need/want from the next major
release of the database.
On Wed, Sep 5, 2018 at 9:31 AM, Jonathan Haddad wrote:
> I'm thinking a month or two after 4.0 would give us time to unwind after
>
ject umbrella, we need to
evaluate each driver implementation's merit on a case-by-case basis. I'm
not sure how we divvy up that work, or whom to entrust with that work, but
it's something to keep in mind.
Thanks,
-Jason
On Fri, Aug 31, 2018 at 8:38 AM, Chris Bannister
wrote
Some of our java8 code will not compile under java11 (see CASSANDRA-9608);
the symbols have literally been removed (Unsafe.monitorEnter() /
Unsafe.monitorExit() ). Setting -source to "8" will not help. Thus, we need
two compilers for the foreseeable future.
On Thu, Aug 23, 2018 at 3:44 PM, Suman
+1 for separate repo. For pretty much all the same reasons Aleksey
elucidated.
On Tue, Aug 21, 2018 at 10:20 AM, Aleksey Yeshchenko
wrote:
> Sure, allow me to elaborate - at least a little bit. But before I do, just
> let me note that this wasn’t a veto -1, just a shorthand for “I don’t like
> t
or at least two years from now.
As I asked, "does anybody feeling strongly?". Personally, I'm sorta +0 to
+0.5, but I was just throwing this out there in case someone does really
think it best we upgrade (and wants to make a contribution).
-Jason
On Wed, Aug 15, 2018 at 7:25 AM
which appear not too difficult to resolve (I
didn't look too closely, tbh).
If anyone wants to tackle this LHF I can rustle up some review time.
Thanks,
-Jason
restored CMS as the default GC alg in CASSANDRA-14636.
Thanks,
-Jason
On Wed, Aug 8, 2018 at 4:33 PM, Jason Brown wrote:
> Hi Jon,
>
> Thanks for pointing that out. Looks like I missed that during the
> CASSANDRA-9608 review. Robert and I didn't discuss that online or o
appropriate to return to CMS. We can certainly have a
discussion thread about switching the default, but until we have that that,
I think it's more honest to revert to CMS. If there's no immediate push
back on reverting, I'll have a patch within a day to revert.
Thanks,
-Jason
e
stronger.
Also, feel free to reach out to me with questions on these.
Thanks!
-Jason
* test_describecluster_more_information_three_datacenters -
nodetool_test.TestNodetool
- versions: 3.11, 3.0, 2.2
https://issues.apache.org/jira/browse/CASSANDRA-14484#
* test_closing_c
Ran the tests again, just for sanity sake, and all seems within acceptable
levels (in order to get the data loss bugs resolved).
+1
On Wed, Jul 25, 2018 at 1:24 PM, Nate McCall wrote:
> +1
>
> On Wed, Jul 25, 2018, 7:47 PM Michael Shuler
> wrote:
>
> > I propose the following artifacts for r
Ran the tests again, just for sanity sake, and all seems within acceptable
levels.
+1
On Wed, Jul 25, 2018 at 1:25 PM, Nate McCall wrote:
> +1
>
> On Wed, Jul 25, 2018, 7:49 PM Michael Shuler
> wrote:
>
> > I propose the following artifacts for release as 2.2.13.
> >
> > sha1: 3482370df5672c93
Ran the tests again, just for sanity sake, and all seems within acceptable
levels (in order to get the data loss bugs resolved).
+1
On Wed, Jul 25, 2018 at 1:24 PM, Nate McCall wrote:
> +1
>
> On Wed, Jul 25, 2018, 7:46 PM Michael Shuler
> wrote:
>
> > I propose the following artifacts for r
.
Current HEAD of 3.0 & 3.11 branches have significantly lower failing
dtests, and the failing tests on HEAD are a subset of those from the last
release.
On Tue, Jul 24, 2018 at 9:03 AM, dinesh.jo...@yahoo.com.INVALID <
dinesh.jo...@yahoo.com.invalid> wrote:
> Hi Jason,
> I a
minor fixes. I will triage
the dtest failures over the coming days. There are some open tickets, and
I'll try to corral those with any new ones.
Thanks,
-Jason
On Mon, Jul 23, 2018 at 10:26 AM, dinesh.jo...@yahoo.com.INVALID <
dinesh.jo...@yahoo.com.invalid> wrote:
> I can he
to unblock
those fixes.
Will have an update shortly ...
-Jason
On Mon, Jul 23, 2018 at 9:18 AM, Jason Brown wrote:
> Hi all,
>
> First, thanks Joey for running the tests. Your pass/fail counts are
> basically what in line with what I've seen for the last several months. (I
>
to actually cutting a
release. We're getting up to almost *six months* since the last release.
Are there any grand objections at this point?
Thanks,
-Jason
On Tue, Jul 17, 2018 at 4:01 PM, Joseph Lynch wrote:
> We ran the tests against 3.0, 2.2 and 3.11 using circleci and there are
Hey all,
The recent builds were -1'd, but it appears the issues have been resolved
(2.2.13 with CASSANDRA-14423, and 3.0.17 / 3.11.3 reverting
CASSANDRA-14252). Can we go ahead and reroll now?
Thanks,
-Jason
> I saw your message on IRC Jason, Kurt forwarded it to me. Thanks for the
> > heads up!
> >
> > 3.11 presently doesn't build, I think it may have been due to an
> accidental
> > merge gone bad. The original JIRA
> > https://issues.apache.org/jira/browse/C
wrt releasing 3.11, +1 to this ... and additionally, 3.0 and 2.2.
I'd propose we cut early next week (Monday) and anything that can get
reviewed/committed from Kurt's list would be great.
On Wed, Jun 6, 2018 at 5:22 AM, kurt greaves wrote:
> We probably need to release 3.11.3 at some point soon
Hey all,
Before we go bananas, let's see if Sylvain, the primary author of the
original patch, has the opportunity to chime with some explanatory notes or
other guidance. There may be some subtle points or considerations that are
not obvious, and I'd hate to lose that context.
Thank
isberg
> wrote:
> >>
> >>> Hi,
> >>>
> >>> +1 to having a feature freeze date. June 1st is earlier than I would
> have
> >>> picked.
> >>>
> >>> Ariel
> >>>
> >>> On Thu, A
+1
On Wed, Apr 4, 2018 at 8:31 PM, Blake Eggleston
wrote:
> +1
>
> On 4/4/18, 5:48 PM, "Jeff Jirsa" wrote:
>
> Earlier than I’d have personally picked, but I’m +1 too
>
>
>
> --
> Jeff Jirsa
>
>
> > On Apr 4, 2018, at 5:06 PM, Nate McCall wrote:
> >
> > Top-posting as
encryption) - which I
doubt I would be able to get to any time this year. It would definitely be
nice to have a clarified encryption/security story for 4.0.
https://issues.apache.org/jira/browse/CASSANDRA-11990 - Address rows rather
than partitions in SASI
- a nice update for SASI, but not critical.
I'm coming to be on-board with #3.
One thing to watch out for (we can't account for it now) is how our
dependencies choose to move forward. If we need to upgrade a jar (netty,
for example) due to some leak or vulnerability, and it only runs on a
higher version, we may be forced to upgrade the base
again,
> what is the Apache Software Foundation's approach to this that affects so
> many of their projects?
>
> On Wed, Mar 21, 2018 at 12:55 PM, Jason Brown
> wrote:
>
> > Well, that was quick. TL;DR Redistributing any part of the OpenJDK is
> > basically
e; reviewer
availability is already stretched thin and I'm afraid of deepening the
review queue, especially mine :)
Thanks,
-Jason
On Thu, Mar 22, 2018 at 6:41 AM, Josh McKenzie wrote:
> > Some of us have big patches in flight, things that actually
> > pay off some technical
Well, that was quick. TL;DR Redistributing any part of the OpenJDK is
basically a no-go.
Thus, that option is off the table.
On Wed, Mar 21, 2018 at 10:46 AM, Jason Brown wrote:
> ftr, I've sent a message to legal-discuss to inquire about the licensing
> aspect of the OpenJDK as
ftr, I've sent a message to legal-discuss to inquire about the licensing
aspect of the OpenJDK as we've been discussing. I believe anyone can follow
the thread by subscribing to the legal-discuss@ ML, or you can wait for
updates on this thread as I get them.
On Wed, Mar 21, 2018 at 9:49
ndows deployment and macOS development).
-Jason
On Wed, Mar 21, 2018 at 9:26 AM, Michael Burman wrote:
> On 03/21/2018 04:52 PM, Josh McKenzie wrote:
>
> This would certainly mitigate a lot of the core problems with the new
>> release model. Has there been any public statements
fwiw, a naive internet search turned up [1]. tl;dr use the java 9's jlink
(or java8's javapackager) to build a full app+jre package for distribution.
I started digging into the legal aspects, and (trying to) searching
legal-discuss@. May just send an email to them later today to speed up this
disc
nt to get in the way of that.
> >>
> >> Which is how you end up with what Jordan and ElasticSearch suggest. I'm
> still +1 on that although in my heart of hearts I want to only support the
> latest OpenJDK on trunk and after we cut a release only change the JDK if
> t
...). However, if
we have the changes necessary for the JDK releases higher than the LTS (if
we following the elastic search model), perhaps it'll be a reasonably
smooth transition?
On Tue, Mar 20, 2018 at 1:31 PM, Jason Brown wrote:
> copied directly from dev channel, just to keep with th
wrote:
> > > My suggestion would be to keep trunk on the latest LTS by default, but
> > > with compatibility with the latest release if possible. Since Oracle
> > > LTS releases are every 3 years, I would not want to tie us to that
> > > rel
;> Wouldn't that potentially leave us in a situation where we're ready
>> for a C* release but blocked waiting on a new LTS cut? For example, if
>> JDK 9 were the currently supported LTS and trunk was on JDK 11, we'd
>> either have to get trunk to work wi
ready
> for a C* release but blocked waiting on a new LTS cut? For example, if
> JDK 9 were the currently supported LTS and trunk was on JDK 11, we'd
> either have to get trunk to work with 9 or wait for 11 to resolve
> that.
>
> On Tue, Mar 20, 2018 at 9:32 AM, Jason Brown wr
ributors and operators there,
instead of rehashing the same conversation.
I look forward to a lively discussion. Thanks!
-Jason
[1] http://www.oracle.com/technetwork/java/eol-135779.html
[2]
https://blogs.oracle.com/java-platform-group/faster-and-easier-use-and-redistribution-of-java-se
[3]
https://ww
All,
This is completely OFF-TOPIC for this mailing list. Please stop.
-Jason
On Thu, Mar 15, 2018 at 10:09 AM, daemeon reiydelle
wrote:
> Not so sure they are C* relevant, I build (100's of GPU enabled node) HPC's
> that use them for ML, AI, Graph analytics, etc. with the
I feel like we've had a very similar conversation (not so) recently:
https://lists.apache.org/thread.html/9952c419398a1a2f22e2887e3492f9d6899365f0ea7c2b68d6fbe0d4@%3Cuser.cassandra.apache.org%3E
Which led to the creation of this JIRA:
https://issues.apache.org/jira/browse/CASSANDRA-13645
On Wed,
note
that the timeouts are currently not due to size.
I have no idea about the BatchMetricsTest, but I can see if it is related
to the others. @dikang, Do you have any details to share about the
failures?
-Jason
On Tue, Feb 27, 2018 at 5:16 PM, Dinesh Joshi <
dinesh.jo...@yahoo.com.invalid&g
leads somewhere positive, that benefits everyone,
-Jason
On Wed, Feb 21, 2018 at 2:53 PM, Kenneth Brotman <
kenbrot...@yahoo.com.invalid> wrote:
> Hi Akash,
>
> I get the part about outside work which is why in replying to Jeff Jirsa I
> was suggesting the big companies could jus
sion at vote/release time (if
not sooner) to triage flaky tests, but I see that as a good thing.
Thanks,
-Jason
[1]
https://testing.googleblog.com/2016/05/flaky-tests-at-google-and-how-we.html
On Fri, Feb 16, 2018 at 12:47 AM, Dinesh Joshi <
dinesh.jo...@yahoo.com.invalid> wrote:
>
Nate, I can do this.
On Thu, Feb 15, 2018 at 2:51 PM, Nate McCall wrote:
> >
> > My circleci test runs fail on lack of resources and I understand now
> > that Jason used the circleci configuration from the trunk branch to run
> > the 3.0 and 3.11 branches. These branche
I ran the unit tests and they are green:
https://circleci.com/gh/jasobrown/workflows/cassandra/tree/3.11.2-candidate-2
+1. Thanks, Michael.
On Wed, Feb 14, 2018 at 1:34 PM, Nate McCall wrote:
> +1
>
> On Thu, Feb 15, 2018 at 10:09 AM, Michael Shuler
> wrote:
> > I propose the following artifac
I ran the unit tests, and all are green:
https://circleci.com/gh/jasobrown/workflows/cassandra/tree/3.0.16-candidate-2
+1. Thank you, Michael.
On Wed, Feb 14, 2018 at 12:51 PM, Brandon Williams wrote:
> +1
>
> On Wed, Feb 14, 2018 at 2:40 PM, Michael Shuler
> wrote:
>
> > I propose the followi
Thanks for all your work, Michael. It is appreciated.
-Jason
On Wed, Feb 14, 2018 at 9:33 AM, Michael Shuler
wrote:
> Thanks for all the feedback on this tentative release commit.
>
> Commit 1d506f9 (current cassandra-3.11 branch HEAD) just passed testall
> 100% for me in CI, so I&
gt; Michael
>
> On 02/14/2018 07:30 AM, Jason Brown wrote:
> > I think we can attempt another build and vote now.
> >
> > On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown
> wrote:
> >
> >> CASSANDRA-14219 is committed and tests look clean (
> https://circleci.
I think we can attempt another build and vote now.
On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown wrote:
> CASSANDRA-14219 is committed and tests look clean (https://circleci.com/
> workflow-run/d0a2622a-e74f-4c46-b0ad-a84ca063736f).
>
> On Tue, Feb 13, 2018 at 1:47 PM, Brandon Willi
CASSANDRA-14234 (which fixes ReadCommandTest) is now committed. I think we
can attempt another build and vote.
Thanks,
-Jason
On Tue, Feb 13, 2018 at 6:16 PM, Jason Brown wrote:
> Thank you, Kurt. I'll get to it within the next 12-24 hours (kids'
> homework time
Thank you, Kurt. I'll get to it within the next 12-24 hours (kids' homework
time in the U.S. now ;) )
-Jason
On Tue, Feb 13, 2018 at 5:10 PM, kurt greaves wrote:
> CASSANDRA-14234 <https://issues.apache.org/jira/browse/CASSANDRA-14234>
> patch
> in for ReadCommandTest
, 2018 at 1:47 PM, Brandon Williams wrote:
> I change my vote to -1 binding here, too.
>
> On Tue, Feb 13, 2018 at 3:45 PM, Jason Brown wrote:
>
> > -1, binding. Unit tests are broken:
> > https://circleci.com/gh/jasobrown/cassandra/452#tests/containers/60
> > <
CASSANDRA-14219 is committed and tests look clean (
https://circleci.com/workflow-run/d0a2622a-e74f-4c46-b0ad-a84ca063736f).
On Tue, Feb 13, 2018 at 1:47 PM, Brandon Williams wrote:
> I change my vote to -1 binding as well.
>
> On Tue, Feb 13, 2018 at 3:43 PM, Jason Brown wrote:
ests? If so, can you include
it in the future [VOTE] emails?
Thanks,
-Jason
On Tue, Feb 13, 2018 at 10:53 AM, Josh McKenzie
wrote:
> +1
>
> On Feb 13, 2018 9:36 AM, "Gary Dusbabek" wrote:
>
> > +1
> >
> > On Mon, Feb 12, 2018 at 9:40 PM, Michael Shuler
, but there are four outstanding failures. I
created CASSANDRA-14219 last week, and assigned it to Dave, but he might
have missed the notification. Dinesh Joshi has a patch that I will review
ASAP.
Michael, is there a link of where you ran the tests? If so, can you include
it in the future [VOTE] emails?
T
+1
On Tue, Feb 13, 2018 at 7:55 AM, Jon Haddad wrote:
> +1
>
>
> > On Feb 13, 2018, at 7:21 AM, Marcus Eriksson wrote:
> >
> > +1
> >
> > On Tue, Feb 13, 2018 at 4:18 PM, Gary Dusbabek
> wrote:
> >
> >> +1
> >>
> >> On Mon, Feb 12, 2018 at 2:30 PM, Michael Shuler >
> >> wrote:
> >>
> >>> I pr
+1
On Tue, Feb 13, 2018 at 7:20 AM, Marcus Eriksson wrote:
> +1
>
> On Tue, Feb 13, 2018 at 1:30 PM, Aleksey Yeshchenko
> wrote:
>
> > +1
> >
> > —
> > AY
> >
> > On 12 February 2018 at 20:30:58, Michael Shuler (mich...@pbandjelly.org)
> > wrote:
> >
> > I propose the following artifacts for re
ll if version 1.1.11 is
> > > > fixed for this, or if that might be less breakage? There are a pretty
> > > > significant number of API-looking changes from 1.1.3 to 1.2.3, so I
> do
> > > > not wish to break other user's applications, as I have experie
used in our
> default settings (or by any install I have ever seen).
> >
> > -Jeremiah
> >
> >> On Feb 13, 2018, at 11:48 AM, Jason Brown wrote:
> >>
> >> Ariel,
> >>
> >> If this is a legit CVE, then we would want to patch al
Ariel,
If this is a legit CVE, then we would want to patch all the current
versions we support - which is 2.1 and higher.
Also, is this worth stopping the current open vote for this patch? (Not in
a place to look at the patch and affects to impacted branches right now).
Jason
On Tue, Feb 13
y externally visible
changes.
Thanks,
-Jason
On Mon, Dec 4, 2017 at 5:33 PM, Jon Haddad wrote:
> Sure, I’m fine w/ letting the _ms settings work indefinitely. Can revisit
> retiring them if there’s ever a real need, am OK if that never happens.
>
> I’ll create the JIRA.
>
> >
Varun,
Please open a JIRA ticket with all the details of what you are seeing.
Thanks,
-Jason
On Mon, Oct 9, 2017 at 7:54 PM, Varun Barala
wrote:
> Hi developers,
>
> Recently, I was removing one node from the cluster without downtime.
>
> Cluster size :: 3 node [test clu
+1
On Mon, Oct 2, 2017 at 11:00 Jon Haddad wrote:
> +1
>
> > On Oct 2, 2017, at 11:00 AM, Brandon Williams wrote:
> >
> > +1
> >
> > On Oct 2, 2017 12:58 PM, "Aleksey Yeshchenko" wrote:
> >
> >> +1
> >>
> >> —
> >> AY
> >>
> >> On 2 October 2017 at 18:18:26, Michael Shuler (mich...@pbandjelly.
+1
On Mon, Oct 2, 2017 at 11:01 Aleksey Yeshchenko wrote:
> +1
>
> —
> AY
>
> On 2 October 2017 at 18:58:57, Michael Shuler (mich...@pbandjelly.org)
> wrote:
>
> I propose the following artifacts for release as 3.11.1.
>
> sha1: 983c72a84ab6628e09a78ead9e20a0c323a005af
> Git:
>
> http://git-wip-
+1
On Thu, Sep 28, 2017 at 12:05 PM, Brandon Williams wrote:
> +1
>
> On Sep 28, 2017 1:12 PM, "Michael Shuler" wrote:
>
> > I propose the following artifacts for release as 2.1.19.
> >
> > sha1: 428eaa3e37cab7227c81fdf124d29dfc1db4257c
> > Git:
> > http://git-wip-us.apache.org/repos/asf?p=cass
+1
On Thu, Sep 28, 2017 at 12:05 PM, Brandon Williams wrote:
> +1
>
> On Sep 28, 2017 1:41 PM, "Michael Shuler" wrote:
>
> > I propose the following artifacts for release as 2.2.11.
> >
> > sha1: c510e001481637e1f74d9ad176f8dc3ab7ebd1e3
> > Git:
> > http://git-wip-us.apache.org/repos/asf?p=cass
Jeff, fantastic idea. +1
John, i'd prefer to get the non-PA ones out of the way first. With PA,
someone at least tried to improve to software.
I'm not at a computer now, but it would be instructive to have a beak down
of those types of tickets by age. I can do that later.
Jason
On T
Hi Andrew,
This question is best for the user@ list, included here.
Thanks,
-Jason
On Wed, Aug 30, 2017 at 10:00 AM, Andrew Whang
wrote:
> In evaluating 3.x, we found that hints are unable to be replayed between
> 2.x and 3.x nodes. This introduces a risk during the upgrade path fo
Noam,
I can review in the next day ot two.
-Jason
On Thu, Aug 24, 2017 at 6:59 AM, Noam Hasson wrote:
> Hi,
>
> Regarding CASSANDRA-13772
> <https://issues.apache.org/jira/browse/CASSANDRA-13772>, I sent a patch a
> week ago and there is no activity since.
>
Malcolm,
You should be able to comment on and assign tickets to yourself, and all
the standard Jira use stuff. What specific behavior is not working for you?
Thanks
-Jason
On Fri, Jul 21, 2017 at 08:36 Malcolm Taylor wrote:
> Please grant me (malcolmt) contributor rights for the Cassan
+1
On Wed, Jun 21, 2017 at 17:52 Brandon Williams wrote:
> +1
>
> On Wed, Jun 21, 2017 at 3:18 PM, Michael Shuler
> wrote:
>
> > I propose the following artifacts for release as 2.1.18.
> >
> > sha1: 9369db1dfd92d4eb76284cfb68b1ffb9d22c9b06
> > Git:
> > http://git-wip-us.apache.org/repos/asf?p=
+1
On Wed, Jun 21, 2017 at 16:52 Jeff Jirsa wrote:
> +1
>
> On Wed, Jun 21, 2017 at 1:20 PM, Michael Shuler
> wrote:
>
> > I propose the following artifacts for release as 2.2.10.
> >
> > sha1: 83f28ce3c4eeff75ce70855a56b6155047ce8e9a
> > Git:
> > http://git-wip-us.apache.org/repos/asf?p=cassan
+1
On Tue, Jun 20, 2017 at 10:37 AM, Jeff Jirsa wrote:
> +1
>
>
> On Mon, Jun 19, 2017 at 4:10 PM, Michael Shuler
> wrote:
>
> > I propose the following artifacts for release as 3.11.0.
> >
> > sha1: 88dee7e9d515ad94ecf8f2309f1e6138ec79e1a2
> > Git:
> > http://git-wip-us.apache.org/repos/asf?p=
+1
On Mon, Jun 19, 2017 at 14:12 Brandon Williams wrote:
> +1
>
> On Mon, Jun 19, 2017 at 3:37 PM, Michael Shuler
> wrote:
>
> > I propose the following artifacts for release as 3.0.14.
> >
> > sha1: f3e38cb638113c2a23855a104d6082da5bc10ddb
> > Git:
> > http://git-wip-us.apache.org/repos/asf?p=
rror"
test_XYZ_feature(error)
def test_XYZ_feature(self, error):
Does this seem legit, or is there something better that is recommended?
WRT to the byteman changes, should I take a similar approach, where I split
out the byteman scripts for each variant, and then pass that script's file
name into an overloaded function?
Thanks!
-Jason
bah! sent too soon. will finish up and resend asap
On Sat, Jun 17, 2017 at 8:20 AM, Jason Brown wrote:
> Hey all,
>
> As I'm finalizing work on CASSANDRA-8457 and CASSANDRA-12229 (switching to
> netty for internode messaging and streaming), I need to update the a
> handfu
Hey all,
As I'm finalizing work on CASSANDRA-8457 and CASSANDRA-12229 (switching to
netty for internode messaging and streaming), I need to update the a
handful of existing dtests due to changes in
a) byteman injections (primarily for streaming)
b) grepping log for errors (primarily for TLS)
As
n add one that would
be great).
I can't look right now, but do we have similar documentation on the Apache
docs?
Thanks,
Jason
On Thu, Jun 15, hose2017 at 01:46 Tomas Repik wrote:
> And yet another glitch in the ob at:
> https://docs.datastax.com/en/cassandra/3.0/cassand
Bah! Jeff beat me to responding with essentially the same message. +1 for
Tuesday and the venue.
On Tue, Jun 13, 2017 at 11:44 AM, Jeff Jirsa wrote:
> Looks great to me - especially the venue. Date wise, Tuesday (19th) lets
> people fly in on Monday instead of costing a weekend, so selfishly th
s) selective than in years past - I don't know how that'll
happen, but perhaps we can find a way with PMC voting or something along
those lines.
I like the idea of a NGCC, but we shouldn't subscribe to it as the only
medium for discussions of big issues/features/concerns.
-Jason
Varun,
This a message better for the user@ ML.
Thanks,
-Jason
On Tue, May 16, 2017 at 3:41 AM, varun saluja wrote:
> Hi Experts,
>
> We are facing issue on production cluster. Compaction on system.hint table
> is running from last 2 days.
>
>
> pending tasks: 1
t want to push away contributors if they can add something
to the project - as long as it is maintainable.
Thanks,
-Jason
[1] https://mesos.apache.org/documentation/latest/committers/
On Fri, May 12, 2017 at 4:35 AM, Sylvain Lebresne
wrote:
> On Fri, May 12, 2017 at 12:29 AM, Jason Brown
Hey Fedor,
I'll try to make some time in the next week to get to it, as my hands are
all over streaming for 4.0.
Thanks for being patient,
-Jason
On Tue, May 9, 2017 at 11:16 PM, Fedor Bobin
wrote:
> Hello,
>
> Could someone provide feedback (and possible merge) my PR [1]
&
ow to host/ship any pluggable dependencies. Much
like what we had with jna before they relicensed, we'll probably ship some
things in-tree and some things users will have to fetch and deploy
themselves; it's a case-by-case basis.
Thanks,
-Jason
On Thu, May 11, 2017 at 2:59 PM, 大平怜 w
I've taken
CASSANDRA-13507
CASSANDRA-13517
-Jason
On Wed, May 10, 2017 at 9:45 PM, Lerh Chuan Low
wrote:
> I'll try my hand on https://issues.apache.org/jira/browse/CASSANDRA-13182.
>
> On 11 May 2017 at 05:59, Blake Eggleston wrote:
>
> > I've taken
storage engine
interface, although it may turn out that it's infeasible/impractical given
the current system. And that's OK.
Thanks,
-Jason
On Thu, Apr 20, 2017 at 4:25 PM, Jeff Jirsa wrote:
> Let's try to make this actionable. Long time
> contributors/committers/members of t
Alex and Sam T think CASSANDRA-13113 is not a deal breaker in terms of
regression (from reading their comments on the JIRA), and Sam mentioned to
me that it only affects trunk, so I'm going to +1 and will poke on
CASSAADNRA-13113 to get it done as soon as it can be :)
-Jason
On Thu, Apr 13,
+1
On Tue, Apr 11, 2017 at 4:26 PM, Brandon Williams wrote:
> +1
>
> On Tue, Apr 11, 2017 at 1:59 PM, Michael Shuler
> wrote:
>
> > I propose the following artifacts for release as 3.0.13.
> >
> > sha1: 91661ec296c6d089e3238e1a72f3861c449326aa
> > Git:
> > http://git-wip-us.apache.org/repos/asf
this is probably better for the user@ mail list.
On Tue, Apr 4, 2017 at 4:10 PM, abdulmuqeet md wrote:
> Hi ,
> I am tryin to set cassandra locally on virtual box with ubuntu. It set up
> properly without any issues, but when I run:
> nodetool status , I get sockettimeout read exception. I have
With 8 binding +1's, 9 non-binding +1's, and no -1, tis vote passes. I'll
request INFRA to make the change.
Thanks,
-Jason
On Wed, Mar 29, 2017 at 8:58 PM, Ben Bromhead wrote:
> +1 nb
>
> On Wed, 29 Mar 2017 at 12:20 Aleksey Yeschenko wrote:
>
> > +1
thout needing to be added to the contributors
group first.
https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to
get this done with INFRA.
Vote will be open for 72 hours.
Thanks,
-Jason Brown
1 - 100 of 276 matches
Mail list logo
