Thanks Sam, I'm following #15193 and should catch the status change there.
Michael
On Tue, Oct 8, 2019 at 6:17 AM Sam Tunnicliffe wrote:
>
> CASSANDRA-15193 just got +1’d yesterday and would be good to include in the
> 3.0 and 3.11 releases. If you don’t mind holding off while
+1
--
Kind regards,
Michael
On Wed, Oct 9, 2019 at 9:06 AM Aleksey Yeshchenko
wrote:
>
> +1 as a rather reasonable starting point; we can make changes to the process
> in the future if need be.
>
> > On 8 Oct 2019, at 19:00, sankalp kohli wrote:
> >
> > Hi,
&
have been in JIRA for quite some time.
--
Kind regards,
Michael
On 10/17/19 8:41 AM, Joshua McKenzie wrote:
Might make sense to split the difference and have a loose reactive policy
of "consider / discuss a potential release when any of the following are
hit":
1. something cri
Oh! As an added bonus of migrating to proper bintray package repository
types, we also cure the pain of users attempting to install older
versions than the latest release, since all versions in the suite are
installable.
--
Michael
On 10/17/19 9:47 AM, Michael Shuler wrote:
Noted:
https
I propose the following artifacts for release as 2.2.15.
sha1: 4ee4ceea28a1cb77b283c7ce0135340ddff02086
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.15-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1179/org/apac
I propose the following artifacts for release as 3.11.5.
sha1: b697af87f8e1b20d22948390d516dba1fbb9eee7
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.5-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1184/org/apac
I propose the following artifacts for release as 4.0-alpha2.
sha1: ca928a49c68186bdcd57dea8b10c30991c6a3c55
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha2-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1185/
I propose the following artifacts for release as 3.0.19.
sha1: a81bfd6b7db3a373430b3c4e8f4e930b199796f0
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.19-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1183/org/apac
This vote passed with 8 binding +1, 2 non-binding +1, and no other votes.
Kind regards,
Michael Shuler
On 10/24/19 12:25 PM, Michael Shuler wrote:
I propose the following artifacts for release as 2.2.15.
sha1: 4ee4ceea28a1cb77b283c7ce0135340ddff02086
Git:
https://gitbox.apache.org/repos/asf
This vote passed with 8 binding +1, 3 non-binding +1, and no other votes.
Kind regards,
Michael Shuler
On 10/24/19 12:25 PM, Michael Shuler wrote:
I propose the following artifacts for release as 3.0.19.
sha1: a81bfd6b7db3a373430b3c4e8f4e930b199796f0
Git:
https://gitbox.apache.org/repos/asf
This vote passed with 7 binding +1, 2 non-binding +1, and no other votes.
Kind regards,
Michael Shuler
On 10/24/19 12:26 PM, Michael Shuler wrote:
I propose the following artifacts for release as 3.11.5.
sha1: b697af87f8e1b20d22948390d516dba1fbb9eee7
Git:
https://gitbox.apache.org/repos/asf
This vote passed with 6 binding +1, 3 non-binding +1, and no other votes.
Kind regards,
Michael Shuler
On 10/24/19 12:26 PM, Michael Shuler wrote:
I propose the following artifacts for release as 4.0-alpha2.
sha1: ca928a49c68186bdcd57dea8b10c30991c6a3c55
Git:
https://gitbox.apache.org/repos
I have updated the new releases in:
src/_data/releases.yaml
I ran through the docker build/run, yet the main index and download
pages of the site were not modified with the new release versions and
dates. I'm going to reset --hard and hand edit those pages. #justFYI
Michael
On 10/17
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.19.
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 sou
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.5.
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 sou
The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.0-alpha2.
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
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.15.
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 sou
Looks like the source markdown was added in the next commit.
http://svn.apache.org/viewvc?view=revision&revision=1857226
(which I see in git as commit 157df5cdfb83cb2edd0051002736316f5f470ad9)
Michael
On 10/30/19 3:29 PM, Nate McCall wrote:
Unfortunately my svn foo is about as atrophie
+1
Scott, was your NGCC talk videoed and uploaded anywhere? I would love to
watch, since I missed the event.
Kind regards,
Michael
On 11/1/19 9:07 AM, Scott Andreas wrote:
+1 nb
On Nov 1, 2019, at 5:36 AM, Benedict Elliott Smith wrote:
+1
On 01/11/2019, 12:33, "Mick Semb
t the general public
are downloading such test packages, then remove them."
http://www.apache.org/legal/release-policy.html#what
Michael
On 11/4/19 1:11 PM, Dinesh Joshi wrote:
I think this is a good idea. I am +1 on making this more discoverable on our
website. Please add instructions
I will also add that I did send the user@ list 4.0-alpha release notes,
along with dev@, and also added to the @cassandra tweet last week. I
thought those were acceptable to get a little wider audience, but didn't
want to link from downloads page, since this is explicit.
Michael
On 11/4
wiki != project website
I think this sounds completely reasonable for a wiki page, and anyone
can edit easily. Good suggestion.
Michael
On 11/4/19 3:18 PM, Joshua McKenzie wrote:
Is there an opportunity to consider a separate "upcoming release testing"
type page with download
ch
passed/failed, here's that info" could be that permanent place? If the
link to the job 404s at some point, who cares, we already have the
feedback and could be re-run, if someone desires.
--
Michael
-
T
On 1/11/20 9:17 AM, Michael Shuler wrote:
On 1/11/20 4:48 AM, Mick Semb Wever wrote:
This brings up the issue that links to builds on tickets should
ideally refer to information that is permanent.
This could be done by configuring builds to keep status and logs but
not the built
ration of all the results in
one comment would be the only way I can think of to prevent the
multi-post problem. (Which does get super annoying pretty quickly)
--
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@cassa
;t find this CI+ICLA policy info in the general ASF docs nor a
google search to locate it. Link?
Thanks!
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
thread started.
Thanks for the JIRA link - would be good to see this formalized
somewhere in policy docs, if it's what INFRA is actually enforcing.
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
Fo
On 1/23/20 3:53 PM, David Capwell wrote:
2) Nightly build email to dev@?
Nope. builds@c.a.o is where these go.
https://lists.apache.org/list.html?bui...@cassandra.apache.org
Michael
-
To unsubscribe, e-mail: dev-unsubscr
he most with the default.
I fully agree that science, maths, and support/ops experience should
guide the choice, but I don't believe that large/giant clusters and
admins are the target audience for the value we select.
--
Kind regards,
Michael
---
thethings and
check 'em, commands and console txt might be interesting. Next step
would be to do each package-type install and startup functional testing,
but I don't have that time right now :)
Warm regards,
Michael
On 1/30/20 1:46 PM, Mick Semb Wever wrote:
Proposing the test bui
uable resources with no
actual diff changes.
https://jenkins.io/doc/book/pipeline/syntax/#built-in-conditions
Michael
On 2/3/20 3:45 PM, Nate McCall wrote:
Mick, this is fantastic!
I'll wait another day to see if anyone else chimes in. (Would also love to
hear from CassCI folks, anyone e
cker rpm build suffers the same source problem
and the src.rpm is significantly larger, since I think it copies all the
downloaded maven artifacts in. It's fine for now, though :)
- UNRELEASED deb build
Thanks for the thorough review Michael.
I did not know about CASSANDRA-14962, but it shoul
.
Mick pinged me on slack, so fyi here, too - I'll work on this in the
morning if I can't get it in tonight.
--
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-m
is is common when docs get large.
I suppose the same could be done for
apache-cassandra-docs-,tar.gz, but I'm not sure about the
release policy part of things here. Needs research.
Please, open a JIRA on this as a packaging improvement.
Kind regards,
Michael
On 2/8/20 3:06 AM, Alex Ott wrote:
eduled yet, but will show up here on dev@ list.)
https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Contributor+Meeting
Michael
On 2/8/20 10:06 PM, Rahul Singh wrote:
Folks, (Initially meant for User , but realized after I wrote it , it’s more
sausage making talk which en user
+1
On 2/11/20 2:36 AM, Mick Semb Wever wrote:
Proposing the test build of Cassandra 3.0.20 for release.
sha1: 89edf5073ba4181dd2f70294cdbcb47f5a45c82e
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.20-tentative
Maven Artifacts:
https://repository.apache.o
+1
On 2/10/20 2:31 PM, Mick Semb Wever wrote:
Proposing the test build of Cassandra 2.2.16 for release.
sha1: c4d9e9ca4ade40b956e37935bce68737b0c063b9
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.16-tentative
Maven Artifacts:
https://repository.apache.o
+1
On 2/11/20 2:38 AM, Mick Semb Wever wrote:
Proposing the test build of Cassandra 3.11.6 for release.
sha1: cb779ab9a631c13a245926f55320392c4468c6f0
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.6-tentative
Maven Artifacts:
https://repository.apache.o
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.16.
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 sou
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.20.
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 sou
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.6.
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 sou
r two, once
15358 gets committed and can review release bits.
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
t to start
testing on different platforms. Also, how was this done before for major
versions? Any lessons learned? Or I am free to improvise :-)
It's your ticket, if you want to work on it in a way that suits you :)
Improvising is fine on this one, I think, since mu
d the link.
Michael
On 3/20/20 11:34 AM, David Capwell wrote:
+1 (non binding)
Sent from my iPhone
On Mar 20, 2020, at 9:32 AM, Oleksandr Petrov
wrote:
This is a somewhat special vote that requires at least minimal
understanding of the patch it is related to [1], since it's also the first
updated vote: -1
Thanks for the run through, Mick.
On 3/20/20 12:01 PM, Michael Shuler wrote:
+1
Code link is actually a branch at:
https://github.com/apache/cassandra-in-jvm-dtest-api/tree/CASSANDRA-15539
Just curious why master isn't the active dev branch, since there's
not
We did something similar on CassCI for the dev branch jobs and skipped
branch names that contained 'nobuild'.
jobs:
build:
branches:
ignore:
- /.*nobuild.*/
..would be the equivalent?
Michael
On 3/24/20 4:08 PM, David Capwell wrote:
It looks like you can config
st builds.
This seems like a pretty easy yaml change that should tick the box for
users that want to push scratch/WIP branches without using testing
resources.
-1 for disabling by default.
Michael
On 3/25/20 11:33 AM, David Capwell wrote:
we should probably just look into further Circle config
+1
On 4/10/20 6:02 PM, Mick Semb Wever wrote:
Proposing the test build of Cassandra 4.0-alpha4 for release.
sha1: d00c004cc10986fc41c2070f9c5d0007e03a45c3
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha4-tentative
Maven Artifacts:
https://repository.ap
I updated the severity and complexity of this ticket. It is not a
trivial fix, but I agree that as time goes on, this is becoming higher
priority to focus some effort on it.
(fyi, I'm not volunteering, is way beyond my means :) )
Kind regards,
Michael
On 6/10/20 11:55 PM, manish khand
non-binding +1
--
Michael
On 04/27/2015 09:46 AM, Jake Luciani wrote:
I propose the following artifacts for release as 2.1.5.
sha1: 3c0a337ebc90b0d99349d0aa152c92b5b3494d8c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.5-tentative
Artifacts:
https
Last I checked — and I could be wrong — we’ve never had to think about what to
number a Cassandra version due to a ticket that could “impact” our users so
dramatically due to the scope of the changes from a single ticket. Food for
thought.
love,
kjellman
> On May 11, 2015, at 2:20 PM, Alex Pop
So #cassandra party in LA? Drinks on you? 😅 Sweet!
Sent from my iPhone
> On May 25, 2015, at 2:34 AM, graham sanderson wrote:
>
> Hey Benedict;
>
> I screwed up on email after a bachelor party, and sent something to external
> cassandra-users not internal users (drunken drivel)
>
> I never s
solved since 2.0.3. There will
never be a 2.0.3.1, so the test issues you may find on the 2.0.3 tag
will remain.
--
Kind regards,
Michael
+1 non-binding
On 06/05/2015 10:27 AM, Jake Luciani wrote:
I propose the following artifacts for release as 2.2.0-rc1.
sha1: b0ae285bdc7377a64ed92f01c67ff46b40ecaac0
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.0-rc1-tentative
Artifacts:
https://reposit
+1 non-binding
On 06/19/2015 07:56 AM, Jake Luciani wrote:
I propose the following artifacts for release as 2.0.16.
sha1: 23e66a9d1c50e4331e8c1d212c2eeb940c5471fa
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.16-tentative
Artifacts:
https://repository.ap
+1 non-binding
On 06/19/2015 07:59 AM, Jake Luciani wrote:
I propose the following artifacts for release as 2.1.7.
sha1: 718c144324d170535d4f1a1e79dd9869cce19ed1
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.7-tentative
Artifacts:
https://repository.apac
Michael would like to recall message [VOTE].. :)
On 06/22/2015 10:12 AM, Michael Shuler wrote:
+1 non-binding
+1 non-binding
On 07/06/2015 01:47 PM, Jake Luciani wrote:
I propose the following artifacts for release as 2.2.0-rc2.
sha1: ebc50d783505854f04f183297ad3009b9095b07e
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.0-rc2-tentative
Artifacts:
https://reposit
+1 non-binding
On 07/06/2015 12:04 PM, Jake Luciani wrote:
I propose the following artifacts for release as 2.1.8.
sha1: db39257c34152f6ccf8d53784cea580dbfe1edad
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.8-tentative
Artifacts:
https://repository.apac
When we set up autojobs for the dev branches, I did some digging around
the jenkins / githubPR integration, similar to what spark is doing. I'd
be completely on board with working through that setup, if it helps this
workflow.
Michael
On 07/08/2015 03:02 PM, Carl Yeksigian wrote:
Spar
+1 (non-binding)
On 07/31/2015 08:42 AM, Jake Luciani wrote:
I propose the following artifacts for release as 3.0.0-alpha1.
sha1: b090ed6938c0fad792e51757384bd5ac7f35a301
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-alpha1-tentative
Artifacts:
https:/
rarily, so commits will not trigger jobs, at the moment.
Workaround - trigger manually via irc:
/msg cassci !build
The I/O looks a lot better on the new server, double the ram, and double
the cores :)
Thanks for your patience while we work this annoyance out!
--
Kind regards,
Michael
your patience!
--
Kind regards,
Michael
y evaluate the true state of a Cassandra branch or
release. There may be other side effects - feel free to chime in.
I'm on a "disconnected" holiday until Monday Aug 24, so I won't have a
chance to check in until then - the Test Eng team can field questions or
clarifications, if needed.
--
Warm regards,
Michael
+1 non-binding
Commit that CR to cassandra-2.0 branch HEAD, leaving the tag where it is
and I can build DSC with it included :)
--
Michael
On 09/17/2015 08:48 AM, Jake Luciani wrote:
I'm not inclined to re-roll for a missing CR but if others feel strongly
about it I will do it.
On Wed
non-binding +1
On 09/18/2015 07:47 AM, Jake Luciani wrote:
I propose the following artifacts for release as 2.0.17.
sha1: c4de752758c3cf7f5de5a92e4ede30e430a36255
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.17-tentative
Artifacts:
https://repository.ap
non-binding +1
On 09/19/2015 01:42 PM, Jake Luciani wrote:
I propose the following artifacts for release as 3.0.0-rc1.
sha1: c95a7098cf77b5b8e96feb7c39aca8fec3a02f9c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-rc1-tentative
Artifacts:
https://reposit
non-binding +1
--
Michael
On 11/06/2015 03:34 PM, Jake Luciani wrote:
I propose the following artifacts for release as 3.0.0.
sha1: 96f407bce56b98cd824d18e32ee012dbb99a0286
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-tentative
Artifacts:
https
Hi,
Please add me to wiki.
Wiki Username: MichaelEdge
.1
*Steps to reproduce*
git clone git://git.apache.org/cassandra.git cassandra
cd cassandra
ant
The ant build is successful. Then I do the following from the 'cassandra'
directory where the repo was cloned:
[michael@localhost cassandra]$ ./bin/nodetool -h 127.0.0.1 -
x27; version (the
> latest development branch that is not yet released.)
> Use branch like cassandra-2.1 that matches your Cassandra version.
>
> On Sat, Nov 14, 2015 at 9:04 PM, Michael Edge
> wrote:
> > Hi,
> >
> > I want to start working on Cassandra-10660 b
Hi All,
I'm trying to assign
https://issues.apache.org/jira/browse/CASSANDRA-10719?filter=12334050 to
myself but it seems I'm unable to. Is someone able to grant me contributor
permissions or do you have another preferred way of assigning issues?
Cheers,
Michael
hat should also be updated?
Regards,
Michael
d prefer a
knowledgeable volunteer to review them to ensure they are accurate.
Let me know if you're interested and I'll send you a copy.
https://wiki.apache.org/cassandra/ArchitectureOverview
Cheers,
Michael
On 11/25/2015 07:36 PM, Michael Edge wrote:
> I'd like to update the read/write path description on the wiki (see link
> below) by adding a couple of UML sequence diagrams I drew a while ago. I
> think they are much better than long textual descriptions for describing
> the order
Write path docs updated on Wiki - please review diagram/text and let me
have your comments (or update text in place).
https://wiki.apache.org/cassandra/WritePathForUsers
Cheers,
Michael
On 26 November 2015 at 11:25, Michael Shuler wrote:
> On 11/25/2015 07:36 PM, Michael Edge wrote:
>
perty
> in cassandra.yaml."
>
> -- Jack Krupansky
>
> On Mon, Nov 30, 2015 at 2:24 AM, Michael Edge
> wrote:
>
> > Write path docs updated on Wiki - please review diagram/text and let me
> > have your comments (or update text in place).
> >
> > h
Read Path ready for review:
https://wiki.apache.org/cassandra/ReadPathForUsers
On 1 December 2015 at 10:30, Michael Edge wrote:
> Thanks for the feedback guys. I've made the updates.
>
> On 1 December 2015 at 00:56, Jack Krupansky
> wrote:
>
>> Great stuff!
>>
> I just remembered... the new Materialized View support in 3.0 - writes to
> the materialized views get triggered when a write occurs to the base table.
> That needs to be in the write path flow/description as well.
>
> -- Jack Krupansky
>
> On Mon, Nov 30, 2015 at 9:30 PM, Michael
ot sure of the precise details there either (like, which consistency those
> backfill writes use.) And that backfilling process has to occur on each
> node of the cluster (but not each replica.) Again, Carl, Jake, et al need
> to review precise details.
>
> -- Jack Krupansky
>
> O
Correct, this is an open source project.
If you want a Enterprise support story Datastax has an Enterprise option for
you.
> On Jan 16, 2016, at 11:19 AM, Anuj Wadehra wrote:
>
> Hi Jonathan
>
> It would be really nice if you could share your thoughts on the four points
> raised regarding
Move to Wiki?
Sent from my iPhone
> On Feb 9, 2016, at 5:59 AM, Aleksey Yeschenko wrote:
>
> Hello everyone,
>
> I’ve compiled a short guide for contributors (who aren’t committers yet)
> about how to properly contribute Cassandra patches:
>
> https://docs.google.com/document/d/1d_AzYQo74de9
repositories and is documented in the DSE docs.
http://docs.datastax.com/en/datastax_enterprise/4.8/datastax_enterprise/install/installPrevious.html
--
Kind regards,
Michael
On 04/07/2016 07:34 AM, Ken Schell wrote:
> Jeff,
>
> When you get in this morning can you come by and see me. I
n?
Short answer: it works properly for your application and your
dev/test/staging evaluations show no regression. This is true for any
version upgrade.
--
Kind regards,
Michael
ourself to only the features present in 3.0.x.
>
> Either way, make sure to properly test whatever release you go for in staging
> first, as Michael says, and you’ll be alright.
>
> --
> AY
>
> On 11 April 2016 at 18:42:31, Anuj Wadehra (anujw_2...@yahoo.co.in.invali
.8. Thanks in advance!
Sincerely,
Michael Fong
ation task for /192.168.88.34
DEBUG [OptionalTasks:1] 2016-04-19 11:19:18,337 MigrationManager.java (line
127) submitting migration task for /192.168.88.34
.
Has anyone experienced this scenario? Thanks in advanced!
Sincerely,
Michael Fong
From: Michael Fong [mailto:michael.f...@ruckuswireless
My vote is to start with BigTableScanner (SSTableScanner).. 5 iterators that
all do something different with each other depending on how used with zero
comments -- in a critical code path. What could go wrong!
> On May 5, 2016, at 11:26 AM, Dave Brosius wrote:
>
> A less controversial tact wou
but need experts help on this.
I don't know if anyone has seen this before, or if there is anything wrong with
our migration flow though..
Thanks in advance.
Best regards,
Michael Fong
From: Michael Fong [mailto:michael.f...@ruckuswireless.com]
Sent: Thursday, April 21, 2016
I'd recommend you create a JIRA! That way you can get some traction on the
issue. Obviously an OOM is never correct, even if your process is wrong in some
way!
Best,
kjellman
Sent from my iPhone
> On May 8, 2016, at 8:48 PM, Michael Fong
> wrote:
>
> Hi, all,
>
&g
Hi,
Thanks for your recommendation.
I also opened a ticket to keep track @
https://issues.apache.org/jira/browse/CASSANDRA-11748
Hope this could brought someone's attention to take a look. Thanks.
Sincerely,
Michael Fong
-Original Message-
From: Michael Kjellman [mailto:m
storm begins.
Also, thanks for your tip on sharing the SOP on stopping an ode, here is what
we have for our stop procedure:
Disable thrift
Disable Binary
Wait 10s
Disable gossip
Drain
Kill
Any thought on this to be further improved?
Thanks!
Sincerely,
Michael Fong
From: Alain RODRIGUEZ
No need to argue your point to me anymore. I've already tuned you out.
These are good people who I consider my friends and insulting people just shows
your arguments really have no merit.
Good luck with your new driver contribution! I look forward to reviewing the
code.
Sent from my iPhone
http://cassandra.apache.org/doc/cql3/CQL.html
On Jun 6, 2016, at 4:42 PM, Mattmann, Chris A (3980)
mailto:chris.a.mattm...@jpl.nasa.gov>> wrote:
Hi,
So, the core documentation for a key part of Cassandra is hosted
at DataStax?
Cheers,
Chris
I the first person to ask that, and why didn’t
a PMC member point that out right away and why did it take me asking
to point to the Apache docs.
This is what I am talking about in terms of the Apache community..
On 6/6/16, 4:47 PM, "Michael Kjellman"
mailto:mkjell.
,
Michael Fong
Bhuvan,
You didn't disrespect anyone, so please don't apologize! Appreciate your
positive and helpful comment for the OP :)
best,
kjellman
> On Jun 13, 2016, at 8:50 AM, Bhuvan Rawal wrote:
>
> Hi Matt,
>
> I suggested the resources keeping in mind the ease with which one can
> learn. My id
Seems like Apache Jira is 100% down, again, for like the 500th time in the last
2 months. Just me or everyone?
have the same experience?
>>>
>>> Best Regards
>>>
>>> On Tue, Jun 14, 2016 at 4:19 AM, Brandon Williams
>>> wrote:
>>>
>>>> Everyone.
>>>>
>>>> On Mon, Jun 13, 2016 at 3:18 PM, Michael Kjellman <
>>>> mkjell...@internalcircle.com> wrote:
>>>>
>>>>> Seems like Apache Jira is 100% down, again, for like the 500th time in
>>>> the
>>>>> last 2 months. Just me or everyone?
>
This was forwarded to me yesterday... a helpful first step
https://github.com/apache/cassandra/blob/cassandra-3.0.0/guide_8099.md
> On Jun 15, 2016, at 9:54 AM, Jonathan Haddad wrote:
>
> Maybe some brave soul will document the 3.0 on disk format as part of
> https://issues.apache.org/jira/brow
101 - 200 of 644 matches
Mail list logo
