rote:
>>
>>
>>
>> On Mon, Oct 23, 2023 at 4:52 AM Mick Semb Wever wrote:
>>
>>
>> The TCM work (CEP-21) is in its review stage but being well past our
>> cut-off date¹ for merging, and now jeopardising 5.0 GA efforts, I would
>> like to propose the following.
>>
>>
>>
>> I think this presumes that 5.0 GA is date driven instead of feature
>> driven.
>>
>> I'm sure there's a conversation elsewhere, but why isn't this date
>> movable?
>>
>>
>>
--
Eric Evans
Staff SRE, Data Persistence
Wikimedia Foundation
viality would require
> way more work in terms of the implementation of JSON/YAML format output.
> Some commands are quite sophisticated and I do not want to be blocked to
> change a field in human-readable out because providing corresponding
> JSON/YAML format would be gigantic portion
roblems this
sort of thing can create, and show a bit of empathy before submitting a
change. For operators on the receiving end, it can be really frustrating,
especially when there is no normative change (i.e. it's in service of
aesthetics).
--
Eric Evans
Staff SRE, Data Persistence
Wikimedia Foundation
gnificant adoption in the user community,
> I would strongly advise against making breaking changes to the CLI output.
>
+1
--
Eric Evans
john.eric.ev...@gmail.com
thing in this situation is to
acknowledge that the console output is a contract, and act accordingly. In
this case: offer (and promote) those structured replacements (JSON, YAML),
document the intended instability, and follow through after a sufficient
window.
--
Eric Evans
john.eric.ev...@gmail.com
on't natively speak English might
struggle to keep pace in real time (to name just a few reasons). This is
probably why the ASF is so adamant about the use of email.
--
Eric Evans
eev...@apache.org
On Wed, Mar 9, 2022 at 12:39 PM Patrick McFadin wrote:
> I'm not sure if they can merge groups but from what I'm reading that
> wouldn't work either. What I'm seeing is a desire to not "promote vendors"
> which I believe is working against the project's self-interest. LinkedIn is
> the perfect pl
On Thu, Oct 14, 2021 at 11:32 AM bened...@apache.org
wrote:
> Hi everyone,
>
> I would like to start a vote on this CEP, split into three sub-decisions,
> as discussion has been circular for some time.
>
> 1. Do you support adopting this CEP?
> 2. Do you support the transaction semantics proposed
itbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.11.7-tentative
> [2]: NEWS.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/3.11.7-tentative
--
Eric Evans
eev...@apache.org
---
s in this thread as our
> initial roll call count for electorate numbers and low watermark
> calculation on subsequent votes.
>
> Thanks again everyone (and specifically Benedict and Jon) for the time and
> collaboration on this.
>
> ~Josh
--
Eric Evans
john.eric.ev...@gmail.
t; > last post-vote publish step.
> > > > >
> > > > > regards,
> > > > > Mick
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@cassand
each level mean in Cassandra terms. There was already some good
> > debate about configuration and common tasks like repair. Let’s get that
> > captured in the doc if we can. If you are one of the groups that already
> > have an operator, your experience here is invaluable. Please
ouple of hours downtime assuming all goes well,
> > including upgrading all
> > associated plugins, performing backups etc. But, this is the first time
> > I'm upgrading this setup so there may be the odd gotcha that surprise
te. When it passes,
someone with the rights is going to have to step forward to ensure
they are published, but surely we can manage that much.
Do you want to do the honors?
--
Eric Evans
john.eric.ev...@gmail.com
-
To unsub
eople have been tilting at this
particular windmill for a while, and it doesn't seem to help.
> On Tue, Mar 26, 2019 at 9:10 AM Eric Evans
> wrote:
>
> > On Tue, Mar 26, 2019 at 10:47 AM Russell Bradberry
> > wrote:
> > >
> > > Responses like this aren
here:
> http://cassandra.apache.org/community/
>
> -Russ
>
> On Tue, Mar 26, 2019 at 8:20 AM Eric Evans
> wrote:
>
> > How did you subscribe?
> >
> > On Tue, Mar 26, 2019 at 9:24 AM Sundaramoorthy, Natarajan
> > wrote:
> > >
> > >
message and delete this e-mail immediately.
--
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
vents those who are vested in one approach (or existing project) or
another from working on what they think best? I suspect developing
consensus here would be a lot easier if we were talking about
something a bit more concrete.
--
Eric Evans
john.eric.ev...@gmail.com
--
the daemon this is already true but I could see this
> > being
> > > > > less
> > > > > > > worrisome for some).
> > > > > > > * Releasing a separate artifact is somewhat easier from a
> > separate
> > > > > repo
solve this problem (and most places will already be
using them). I'm more interested in things like cluster status,
streaming, repair, etc. Something to automate/centralize
database-specific command and control, and improve visibil
> they wouldn't do if we go with option 1, but there is no historical
> evidence to support the notion that it is a safe bet. If this doesn't
> happen, which we *have* to consider, then the project will be in a *much*
> worst state than with option 1. We'll have taken forever
lly impacting our goals of "stable" ==
>> "exciting."
Unfortunately, when stability suffers things get "exciting" for all
sorts of unintended reasons. I'm personally not umm, excited, by that
prospect.
--
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
h mainly security updates) by
> using Centos.
Agreed. Someone said this elsewhere as well, that the community will
work this out.
Even if you are not running say Debian, or RedHat, those distributions
will be backporting critical fixes to their JVMs; This wo
th looking at anyway.
> On Wed, Mar 21, 2018 at 9:49 AM, Eric Evans wrote:
>> On Wed, Mar 21, 2018 at 8:04 AM, Stefan Podkowinski wrote:
>>
>>> There's also another option, which I just want to mention here for the
>>> sake of discussion.
>>>
>>
; >>>>>>>>>
> >>>>>>>>> We have a jira [5] where Robert Stupp did most of the work to get
> >>>> us
> >>>>> onto
> >>>>>>>>> Java 9 (thanks, Robert), but then the announcement of the JDK
> >>>> version
> >>>>>>>>> changes happened last fall after Robert had done much of the work
> >>>> on
> >>>>> the
> >>>>>>>>> ticket.
> >>>>>>>>>
> >>>>>>>>> Here's an initial proposal of how to move forward. I don't
> suspect
> >>>>> it's
> >>>>>>>>> complete, but a decent place to start a conversation.
> >>>>>>>>>
> >>>>>>>>> 1) receommend OracleJDK over OpenJDK. IIUC from [3], the OpenJDK
> >>>> will
> >>>>>>>>> release every six months, and the OracleJDK will release every
> >>>> three
> >>>>>>>> years.
> >>>>>>>>> Thus, the OracleJDK is the LTS version, and it just comes from a
> >>>>> snapshot
> >>>>>>>>> of one of those OpenJDK builds.
> >>>>>>>>>
> >>>>>>>>> 2) always release cassandra on a LTS version. I don't think we
> can
> >>>>>>>>> reasonably expect operators to update the JDK every six months,
> on
> >>>>> time.
> >>>>>>>>> Further, if there are breaking changes to the JDK, we don't want
> >>>> to
> >>>>> have
> >>>>>>>> to
> >>>>>>>>> update established c* versions due to those changes, every six
> >>>>> months.
> >>>>>>>>>
> >>>>>>>>> 3) keep trunk on the lasest jdk version, assumming we release a
> >>>> major
> >>>>>>>>> cassandra version close enough to a LTS release. Currently that
> >>>> seems
> >>>>>>>>> reasonable for cassandra 4.0 to be released with java 11 (18.9
> >>>> LTS)
> >>>>>>>>> support. Perhaps we can evaluate this over time.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Once we agree on a path forward, *it is impreative that we
> publish
> >>>>> the
> >>>>>>>>> decision to the docs* so we can point contributors 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://www.oracle.com/java/java9-screencasts.html?bcid=
> >>>>>>>> 5582439790001&playerType=single-social&size=events
> >>>>>>>>> [4]
> >>>>>>>>> http://blog.joda.org/2018/02/java-9-has-six-weeks-to-live.
> >>>>>>>> html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+
> >>>>>>>> StephenColebournesBlog+%28Stephen+Colebourne%27s+blog%29
> >>>>>>>>> [5] https://issues.apache.org/jira/browse/CASSANDRA-9608
> >>>>>>>>
> >>>>>>>>
> >>>> -
> >>>>>>>> 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
> >>>>>>
> >>>>>
> >>>>>
> -
> >>>>> 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
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>
--
Eric Evans
eev...@wikimedia.org
mple as it seems.
Speaking as someone who has personally been burned by this
(repeatedly, and it's on-going), please think very carefully before
making such changes. I hate to think about of all the hours I wasted
shaving this breed of yak.
> On Wed, Mar 21, 2018 at 9:06 AM kurt
on 13907 (
>> https://issues.apache.org/jira/browse/CASSANDRA-13907?focusedCommentId
>> =16211365&page=com.atlassian.jira.plugin.system.issuetabpanels:comment
>> -tabpanel#comment-16211365
>> <https://issues.apache.org/jira/browse/CASSANDRA-13907?focusedCommentI
&
ation 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 . . .
> > >
> > >
> > >
> > > Pleas
n 4.0 (
> > > https://issues.apache.org/jira/browse/CASSANDRA-13530 )
> > > - Michael Kjellman spent some time porting dtests from nose to pytest,
> > and
> > > from python 2.7 to python 3, removing dependencies on dead projects
> like
> > > pycassa and the old thrift-cql library. Still needs to be reviewed (
> > > https://issues.apache.org/jira/browse/CASSANDRA-14134 )
> > > - Robert Stupp spent some time porting to java9 - again, still need to
> be
> > > reviewed ( https://issues.apache.org/jira/browse/CASSANDRA-9608 )
> > >
> > > Overall, the state of the project appears to be strong. We're seeing
> > active
> > > contributions driven primarily by users (like you), the 8099/3.0 engine
> > is
> > > looking pretty good here in December, and the code base is stabilizing
> > > towards a product all of us should be happy to run in production.
> Despite
> > > some irrationally skeptical sky-is-falling threads near the end of
> 2016,
> > I
> > > feel confident in saying it was a pretty good year for Cassandra, and
> as
> > > the project continues to move forward, I'm looking forward to seeing
> 4.0
> > > launch in 2018 (hopefully with a real user conference!)
> > >
> > > - Jeff
> > >
> >
>
--
Eric Evans
john.eric.ev...@gmail.com
ressive disc usage?
What version are you upgrading from?
How many page faults are you seeing? If the number is high, you might
try adding "disk_access_mode: mmap_index_only" to cassandra.yaml
(there is no default entry in the file).
--
Eric Eva
x27;t
> know it was happening / don't have time to follow every conversation in the
> community.
[ ... ]
I've missed these; Thanks Jeff!
--
Eric Evans
john.eric.ev...@gmail.com
-
To unsubscribe, e-mail: dev-un
#x27;s bound to be a
slippery slope. I also think it's not uncommon for what appears to be
a trivial change for one person, to be very important to someone else.
I wonder if the length of the list for 4.0 doesn't have as much to do
with the delays in ge
plate it for
use with Puppet, Chef, etc. Once deployed, you would not edit this
file again.
cassandra-env.sh is configuration for Cassandra that lives above what
is reasonable to configure in the application. Heap size is a good
example of the sort handled here, something to be passed as an
argumen
On Mon, Jun 12, 2017 at 3:30 PM, Gary Dusbabek wrote:
> Date: One of 18, 19, or 22 September 2017.
Strawpoll: Which of these dates looks most attractive to folks
(Monday, Tuesday, or Friday)?
--
Eric Evans
john.eric.ev...@gmail.
f year.
We were thinking we'd put together some options for venue, and propose
some dates, and circle back to the list in search of consensus.
If this seems reasonable for now, then we'll get back to everyone with
more info in a weeks time.
, I missed that last two years, but was hoping to make it this
> year.
You are right, of course. I was (clumsily) trying to create a
distinction between this and a regular user conference.
--
Eric Evans
john.eric.ev...@gmail.com
On Wed, May 31, 2017 at 2:19 PM, Eric Evans wrote:
> Hi,
>
> Is anyone working on an NGCC event for this year? Given all of the
> recent changes, it seems like it could be really useful. If not, is
> there interest? When would be good, September? October? What about
> location
(centrally located), or San Francisco (San
Franciscoly located).
Thoughts?
--
Eric Evans
john.eric.ev...@gmail.com
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h
to this, but brilliant.
--
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 abuse though.
--
Eric Evans
john.eric.ev...@gmail.com
to unsubscribe (and maybe setting the reply-to to
{list}-unsubscribe@cassandra.a.o).
I'm fairly certain the list software doesn't come ready to do this
though; I imagine the response from INFRA will be something like
"patches welcome", so we should be ready to rollup our sleeves.
--
Eric Evans
john.eric.ev...@gmail.com
ere is 1:1 IMO, your 2 cents are worth the
same as any others! ;)
--
Eric Evans
john.eric.ev...@gmail.com
veryone can agree), then it seems like the next step is working on
> defining the proper interface.
+1
--
Eric Evans
john.eric.ev...@gmail.com
On Fri, Apr 7, 2017 at 10:35 PM, Jeff Jirsa wrote:
> First, check out this graph:
>
> http://i.imgur.com/cEx3jOo.png
Oh snap; That's awesome!
--
Eric Evans
john.eric.ev...@gmail.com
appened before); Some
here seem to be reacting out of concern to the very existence of the
email, which makes me think it's precisely the sort of thing that
shouldn't be kept hidden.
--
Eric Evans
john.eric.ev...@gmail.com
pushed back against
it in the Early Days, but we would be so much better off at this point
with Maven.
--
Eric Evans
john.eric.ev...@gmail.com
mpaction spikes that was seeing this specific issue
>> with four LCS-based tables:
>>
>> https://gist.github.com/zznate/d22812551fa7a527d4c0d931f107c950
>>
>> The significant part of this particular workload is a burst of heavy writes
>> from long-duration scheduled jobs.
>>
>
>
>
> --
> Dikang
--
Eric Evans
john.eric.ev...@gmail.com
On Wed, Nov 16, 2016 at 10:30 PM, Ben Bromhead wrote:
> Thanks Nate, this is great to see this get some visibility on a wider
> distribution list like dev!
Full ACK; Thanks for sending this to the list Nate!
--
Eric Evans
john.eric.ev...@gmail.com
of this if people think it’s a
>> > good idea.
>>
>> Also a good idea and much more accessible/easily fixable.
>>
>> We will gladly look at any doc updates for this, looping in the
>> broader community once published (this last part being key - I'm
>> afraid if we ask for help too early, we'll get tons of interest to
>> which we cannot reply and then be in even worse shape).
>>
>> -Nate
>>
--
Eric Evans
john.eric.ev...@gmail.com
age everyone to pause and review
> what they have just written with the Code of Conduct in mind before
> pressing send.
Thank you for this Mark.
And while we're at it, thank you for all of your input these past
weeks. It's been incredibly helpful and constructive.
--
Eric Evans
john.eric.ev...@gmail.com
On Fri, Nov 4, 2016 at 11:57 AM, Chris Mattmann wrote:
> Yet you act like it's volunteer time that's preventing moderating a message
> through in 12 hours.
Here it is again, 12 hours. If we have a 12 hour SLA on moderation,
then you can remove me as a moderator; I can'
On Fri, Nov 4, 2016 at 11:51 AM, Gary Dusbabek wrote:
> I'm beginning to wonder if I'm the only one with moderator privs. Any other
> committer/PMCs interested?
You are not.
> Sorry, it's a chore to begin with and I've been traveling this week.
No need to be sorry.
o bring her
> conversation to the list. 12 hours later it's still in moderation, and we are
> arguing whether to f'ing moderate it through. Wow. Great job.
Wait, what? As a moderator of this list (unpaid, volunteer), did I
miss the SLA I was being held to? Are you volunteering to moderate
this list?
--
Eric Evans
john.eric.ev...@gmail.com
he.org/thread.html/840fd900fb7f6568bfa008d122d4375b708c1f7f1b5929018118d5d5@%3Cdev.cassandra.apache.org%3E
>
> Note: It won't be immediate as there are some steps to follow [0] for
> accepting outside code contributions.
>
> The vote will be open for 72 hours.
+1
--
Eric Evans
john.eric.ev...@gmail.com
will
> be
> fairly rare, less than 1 per Y period on average). Further, it's supposed
> to
> be stable and fixes are supposed to be critical, so doing hot-fix releases
> probably makes the most sense (though it probably only work if we're
> indeed
> strict on what is considered critical).
This seems pretty close to what Mck suggested; I think this could work.
--
Eric Evans
john.eric.ev...@gmail.com
patch release as 'Beta'),
> - accept that every feature release isn't by default initially supported,
> and its branch might never be,
> - maintain 3 'GA' branches at any one time,
> - accept that it's not going to be the oldest GA branches that necessarily
> reach EOL first.
I like it.
--
Eric Evans
john.eric.ev...@gmail.com
On Thu, Sep 1, 2016 at 7:02 AM, Jason Brown wrote:
> have opened up CASSANDRA-12345...
Nice; What did you do, camp on the "create" button until after 12344
was submitted? :)
--
Eric Evans
john.eric.ev...@gmail.com
search/reply trap as well
No, if there were consensus that was worthwhile, I would have no objections.
--
Eric Evans
eev...@wikimedia.org
r to do it manually.
Cheers,
--
Eric Evans
john.eric.ev...@gmail.com
nything to add WRT
CASSANDRA-10993, but wanted to say that this is awesome. Thanks for
this Tyler!
--
Eric Evans
john.eric.ev...@gmail.com
gather, not everyone agrees so YMMV.
Cheers,
--
Eric Evans
john.eric.ev...@gmail.com
d
attributed it to email. Personally, I think that this is a) a
conversation worth having, and b) one that others have been reluctant
to engage in. My intention was to understand the reluctance, and if
possible, encourage you (and others) to try.
Cheers,
--
Eric Evans
john.eric.ev...@gmail.com
sponse.
I guess what I should have asked is, if not email, then how?
--
Eric Evans
john.eric.ev...@gmail.com
ood for the
project, full stop. No malice needs to be attributed, no effigies
burned, and it shouldn't be viewed as squaring up against those we
know and respect who are employed by Datastax.
--
Eric Evans
john.eric.ev...@gmail.com
champion regular doc contributors
for committership. Hopefully there are others willing to do the same!
--
Eric Evans
john.eric.ev...@gmail.com
ectations).
One thing is as certain now as it was then, to make such a thing work,
we'd need to be far more willing to pull the trigger on new committers
than we are now. Personally, I think we could benefit from that,
regardless of how you feel about in-tree drivers.
--
Eric Evans
john.eric.ev...@gmail.com
> <https://issues.apache.org/jira/browse/CASSANDRA-8700>.
I think this is fantastic; I was completely unaware of
https://issues.apache.org/jira/browse/CASSANDRA-8700, and had been
planning to suggest exactly this.
--
Eric Evans
john.eric.ev...@gmail.com
On Wed, May 4, 2016 at 12:14 PM, Jonathan Ellis wrote:
> On Wed, May 4, 2016 at 2:27 AM, Sylvain Lebresne
> wrote:
>
>> On Tue, May 3, 2016 at 6:57 PM, Eric Evans
>> wrote:
>>
>> > On Mon, May 2, 2016 at 11:26 AM, Sylvain Lebresne
>> > wrote:
&
th "Sets foo" can get pretty tiresome for
everyone, and doesn't add any value.
Otherwise I think this is perfectly reasonable; +1
--
Eric Evans
john.eric.ev...@gmail.com
org/~jake
>
> The vote will be open for 72 hours (longer if needed).
+1
--
Eric Evans
eev...@sym-link.com
[ Eric Evans ]
> [ Adam Israel ]
> > I recently filed a bug [1] about broken mirrors and debian repo for
> > Cassandra. The mirror issue has been resolved, but there is still an issue
> > with the Debian repo that is unresolved. The Infra team has blocked the
> >
is currently blocked
> 2) It’s unclear if the ASF or DataStax repo is authoritative
> 3) Upstream projects that depend on the ASF repo are currently broke.
Sorry, we'll get it sorted out. Thanks for the heads up!
--
Eric Evans
eev...@sym-link.com
[ Eric Evans ]
> Git: 2.1.0-rc4-tentative/d872e2c
> Gitweb:
> https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.0-rc4-tentative
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1021/org/apache/cassandra/apache-
longer as required).
Cheers,
[1] http://goo.gl/wcH7ma (CHANGES.txt)
[2] http://goo.gl/Ooros0 (NEWS.txt)
--
Eric Evans
eev...@sym-link.com
to propose
> that we only extend for
> just 24h more hours (provided we get enough +1 by then). Please do re-vote
> however.
+1
> On Wed, Mar 26, 2014 at 9:02 AM, Sylvain Lebresne wrote:
>
> > Alright, let's figure out what's going on there and we'll restart a
[ Eric Evans ]
>
> #6527[1] could cause data loss, so I propose the following artifacts for
> release as 2.0.4
>
> Git: 2.0.4-tentative/d56f8f2
> Gitweb:
> https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=d56f8f2
> Artifacts:
> https://re
)
[3]: http://goo.gl/At9VU3 (NEWS.txt)
[4]: http://goo.gl/36pfMG (JIRA release notes)
[5]: http://people.apache.org/~eevans (Debian package)
--
Eric Evans
eev...@sym-link.com
signature.asc
Description: Digital signature
you from working on this; Good luck
P.S. Please subscribe to the list (dev-subsrc...@cassandra.apache.org)
--
Eric Evans
eev...@sym-link.com
vailable here:
> http://people.apache.org/~slebresne/
>
> Since it is a re-roll, I propose an expediated vote so the vote will be
> open for 24 hours (but longer if needed).
+1
--
Eric Evans
eev...@sym-link.com
: http://goo.gl/R8BxIz (CHANGES.txt)
> [2]: http://goo.gl/gGCFnI (NEWS.txt)
--
Eric Evans
eev...@sym-link.com
kage are also available here:
> http://people.apache.org/~slebresne/
+1
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/nfCb5Y (CHANGES.txt)
> [2]: http://goo.gl/pxDqrc (NEWS.txt)
--
Eric Evans
eev...@sym-link.com
[ Eric Evans ]
> Git: 2.0.0-rc1-tentative / e8ae672
> Gitweb:
> https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=e8ae672
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-062/org/apache/cassandra/apache-cassandra/2.0.0-rc1/
>
tant consideration when
comparing the two, but luckily we don't have to have that argument; CQL is
actually faster.
--
Eric Evans
eev...@sym-link.com
RB5aW (CHANGES.txt)
[2]: http://goo.gl/h55Zsq (NEWS.txt)
--
Eric Evans
eev...@sym-link.com
[ Eric Evans ]
> Git SHA1: 0291d696018214000709025c0b806089c2f51e97
> Git HTTP:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.8-tentative
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-029/org/apache/c
://people.apache.org/~eevans/
Unless anyone objects, I suggest a 24-hour vote.
[1]: http://thread.gmane.org/gmane.comp.db.cassandra.devel/7904
[2]: https://issues.apache.org/jira/browse/CASSANDRA-5814
[3]: http://goo.gl/bQ3a4i (CHANGES.txt)
[4]: http://goo.gl/Zj1JFa (NEWS.txt)
--
Eric Evans
eev...@sym-link.com
call it
> 1.2.8. If memory serves, we've done this before, this way.
Yeah, that's how we've been doing it.
Since Sylvain is out, I'll put together some release artifacts and start
a new vote presently.
Cheers,
--
Eric Evans
eev...@sym-link.com
gt; The vote will be open for 72 hours (longer if needed).
+1
> [1]: http://goo.gl/LorY5 (CHANGES.txt)
> [2]: http://goo.gl/zEt5i (NEWS.txt)
--
Eric Evans
eev...@sym-link.com
[ Eric Evans ]
> I propose the following for release as 1.1.11
>
> SHA1: d939a0c958d36a3debfc63364a3fa569aa632c6e
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.1.11-tentative
> Artifacts:
> https://repository.apache.org
(CHANGES.txt)
[2]: http://goo.gl/O55QF (NEWS.txt)
[3]: http://goo.gl/KbiRm (Can't Hug Every Cat)
--
Eric Evans
eev...@sym-link.com
kage are also available here:
> http://people.apache.org/~slebresne/
>
> The vote will be open for 72 hours (longer if needed).
+1
--
Eric Evans
eev...@sym-link.com
the fat client work right
>> > now?"
>>
>> It's not often tested.
>>
>> > What does not work about it? I have a fat client app running same jvm as
>> c*
>> > it seems to work well.
>>
>> Good to know. :)
>>
>> -Brandon
>>
--
Eric Evans
Acunu | http://www.acunu.com | @acunu
gt;
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~slebresne/
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/dwPLz (CHANGES.txt)
> [2]: http://goo.gl/reKh5 (NEWS.txt)
--
Eric Evans
Acunu | http://www.acunu.com | @acunu
s alike, and
should be a great chance to share new ideas and learn about existing +
upcoming projects. To sign up to come to that, or learn more, it's
http://wiki.apache.org/apachecon/BarCampApachePortland
Hopefully see some of you in Portland in a few weeks!
---
y).
>>>>>
>>>>> Upgrading to Java7 lets us take advantage of new (two year old)
>>>>> features as well as simplifying interoperability with other
>>>>> dependencies, e.g., Jetty's BlockingArrayQueue requires java7.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> --
>>>>> Jonathan Ellis
>>>>> Project Chair, Apache Cassandra
>>>>> co-founder, http://www.datastax.com
>>>>> @spyced
>>>>>
>>>>>
>>>
>>>
--
Eric Evans
Acunu | http://www.acunu.com | @acunu
kathon; I was planning
to spend some time working on a C native driver.
If you haven't already, add 1 to the number of interested persons on
http://wiki.apache.org/apachecon/HackathonNA13.
See you there!
> On Wed, Dec 26, 2012 at 1:54 PM, Eric Evans wrote:
>
>> Hi,
>>
>
Hi,
ApacheCon NA is February 26-28 in Portland, with project hackathons
hosted on Monday the 25th.
How many are planning to attend ApacheCon this year? Is there any
interest in organizing a Cassandra hackathon?
http://wiki.apache.org/apachecon/HackathonNA13
Cheers,
--
Eric Evans
Acunu | http
ours (longer if needed).
>>
>> [1]: http://goo.gl/vkaZt (CHANGES.txt)
>> [2]: http://goo.gl/H3E61 (NEWS.txt)
--
Eric Evans
Acunu | http://www.acunu.com | @acunu
, you can supply a timestamp with CQL, same as you can
with Thrift. For example:
INSERT INTO somedb.sometable (id, given, surname) VALUES ('pgriffith',
'Peter', 'Griffith') USING TIMESTAMP 42;
--
Eric Evans
Acunu | http://www.acunu.com | @acunu
. This is broad enough that people
of all skill levels should be able to contribute.
So, is anyone interested?
[1]: 5–8 November, Sinsheim, Germany
[2]: Guy Fawkes Day!
[3]: http://wiki.apache.org/apachecon/HackathonEU12
--
Eric Evans
Acunu | http://www.acunu.com | @acunu
1 - 100 of 437 matches
Mail list logo
