+1
—
Robert Stupp
@snazy
> On 2. Sep 2020, at 10:38, Sylvain Lebresne wrote:
>
> +1
> --
> Sylvain
>
>
> On Wed, Sep 2, 2020 at 10:21 AM Sam Tunnicliffe wrote:
>
>> +1
>>
>>> On 2 Sep 2020, at 09:03, Benjamin Lerer
>> wrote:
>>
+1 (nb)
—
Robert Stupp
@snazy
> On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang
> wrote:
>
> +1 (nb)
>
> On Thu, 16 Jul 2020 at 01:28, Brandon Williams wrote:
>
>> +1 (binding)
>>
>> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever wrote:
>>
Yea, ZGC is kinda tricky in 11.
—
Robert Stupp
@snazy
> On 14. Jul 2020, at 15:02, Jeff Jirsa wrote:
>
> Zgc
>
>> On Jul 14, 2020, at 2:26 AM, Robert Stupp wrote:
>>
>>
>>> On 14. Jul 2020, at 07:33, Jeff Jirsa wrote:
>>>
>>&g
been removed). It is not that much work, it just
needs to be done.
—
Robert Stupp
@snazy
> On 13. Jul 2020, at 20:42, Jon Haddad wrote:
>
> Support for Java 11 was added a long time ago, and it's been about 2 years
> since it was released (Sept 2018). Had we released Cassandra
> On 14. Jul 2020, at 07:33, Jeff Jirsa wrote:
>
> Perhaps the most notable parts of jdk11 (for cassandra) aren’t even prod
> ready in jdk11 , so what’s the motivation and what does the project gain from
> revisiting the experimental designation on jdk11?
Can you elaborate on what’s not even
Build tools are like religions, that's why. Or maybe cults. Or all
Stockholm Syndrome creators? :)
Robert Stupp has been noodling around with a gradle based build env for C*
that'll live alongside ant. Not sure what the status is on that atm through.
On Sun, May 31, 2020 at 3:16 PM A
I can help
--
Robert Stupp
@snazy
> Am 07.05.2020 um 20:29 schrieb Mick Semb Wever :
>
> The Cassandra release process has had some improvements to better in
> line with the ASF guidelines: sha256 & sha512 checksums, staged
> artefacts in svnpubsub, dep and rpm repositories
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 dependencies used by
UDFs/UDAs, I think we should refactor the UDF code parts and remove the
depende
licated in the code
base with this prototype - once in the “current” source tree and once for UDFs.
However, unifying the code paths is not trivial, since the UDF sandbox
prohibits the use of internal classes (direct and likely indirect dependencies).
Robert
—
Robert Stupp
@snazy
right Java version - and
not let the package manger just pull the newest available.
The version-string from adoptopenjdk for example is one of these “minor
issues"...
—
Robert Stupp
@snazy
> On 28. May 2018, at 15:46, Stefan Podkowinski wrote:
>
> The main issue that I see, for s
s 1+3: Raise the minimum supported
version of 8 for C* 4.0 to something more recent than 8u40, which is
quite from the stone-age. It could be 8u171 or whatever will be recent
in autumn.
Robert
--
Robert Stupp
@snazy
-
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,
ularly useful, imo), [4] and many other postings on the internet for
discussion/commentary.
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 wo
>>>>>> For all those people who use MAX TTL=20 years for
>> inserting/updating
>>>>>> data in production, https://issues.apache.org/
>>>> jira/browse/CASSANDRA-14092
>>>>>> can silently cause irrecoverable Data Loss. This seems like a certain
>>>> TOP
>>>>>> MOST BLOCKER to me. I think the category of the JIRA must be raised
>> to
>>>>>> BLOCKER from Major. Unfortunately, the JIRA is still "Unassigned"
>> and no
>>>>>> one seems to be actively working on it. Just like any other critical
>>>>>> vulnerability, this vulnerability demands immediate attention from
>> some
>>>>>> very experienced folks to bring out an Urgent Fast Track Patch for
>> all
>>>>>> currently Supported Cassandra versions 2.1,2.2 and 3.x. As per my
>>>>>> understanding of the JIRA comments, the changes may not be that
>> trivial
>>>> for
>>>>>> older releases. So, community support on the patch is very much
>>>> appreciated.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Anuj
>>>>>>>>
>>>>>>>>
>> -
>>>>>>>> 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
>>
>>
—
Robert Stupp
@snazy
non-binding +1, too.
—
Robert Stupp
@snazy
> On 29. Mar 2017, at 15:21, Jason Brown wrote:
>
> Hey all,
>
> Following up my thread from a week or two ago (
> https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apa
signal-noise-ratio - you can filter/watch
individual JIRAs. But for mailing lists it’s always all or nothing.
—
Robert Stupp
@snazy
> On 16 Aug 2016, at 06:19, Ken Hancock wrote:
>
> On Mon, Aug 15, 2016 at 3:57 PM, Dave Lester wrote:
>
>> Interesting, thanks for pointing ou
+1
—
Robert Stupp
@snazy
> On 21 Jul 2016, at 07:48, Michael Shuler wrote:
>
> I propose the following artifacts for release as 3.8.
>
> sha1: c3ded0551f538f7845602b27d53240cd8129265c
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=re
There’s also:
CASSANDRA-10520 Compressed writer and reader should support non-compressed data
(changes sstable format)
CASSANDRA-10383 Disable auto snapshot on selected tables (changes schema)
—
Robert Stupp
@snazy
> On 21 Jul 2016, at 00:59, Jason Brown wrote:
>
> CASSANDRA-8
clarifications on #cassandra-dev IRC
Robert
—
Robert Stupp
@snazy
> On 12 Jul 2016, at 19:42, Pedro Gordo wrote:
>
> Hi all
>
> I'm finishing an MSc in which my final project is to implement a new
> compaction strategy in Cassandra. I've discussed the main points of the
>
+1 (non-binding)
—
Robert Stupp
@snazy
> On Jun 1, 2016, at 19:30, Jake Luciani wrote:
>
> I propose the following artifacts for release as 3.6.
>
> sha1: 8d22d9fd1842c59ea65a3793aceb5a78c5852351
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=sho
+1
--
Robert Stupp
@snazy
--
Robert Stupp
@snazy
> Am 08.01.2016 um 22:12 schrieb Jake Luciani :
>
> I propose the following artifacts for release as 3.2.
>
> sha1: 3c6dfa4aa0b9ffb0a48a02b949bff2a8406764e6
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a
+1
--
Robert Stupp
@snazy
--
Robert Stupp
@snazy
> Am 28.12.2015 um 15:26 schrieb Jonathan Ellis :
>
> Thrift has been officially frozen for almost two years and unofficially for
> longer. [1] Meanwhile, maintaining Thrift support through changes like
> 8099 has been a substan
package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/0vghCL (CHANGES.txt)
> [2]: http://goo.gl/xAElQy (NEWS.txt)
—
Robert Stupp
@snazy
signature.asc
Description: Message signed with OpenPGP using GPGMail
package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 48 hours (longer if needed).
>
> [1]: http://goo.gl/aOEO0x (CHANGES.txt)
> [2]: http://goo.gl/Im3ydD (NEWS.txt)
—
Robert Stupp
@snazy
signature.asc
Description: Message signed with OpenPGP using GPGMail
+1
--
Robert Stupp
@snazy
--
Robert Stupp
@snazy
> Am 19.09.2015 um 22:42 schrieb Jake Luciani :
>
> I propose the following artifacts for release as 3.0.0-rc1.
>
> sha1: c95a7098cf77b5b8e96feb7c39aca8fec3a02f9c
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassa
package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/3ifmBZ (CHANGES.txt)
> [2]: http://goo.gl/7rQrRR (NEWS.txt)
—
Robert Stupp
@snazy
so available here:
>
> http://people.apache.org/~jake
>
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]:
> http://goo.gl/3ifmBZ
> (CHANGES.txt)
> [2]:
> http://goo.gl/7rQrRR (NEWS.txt)
—
Robert Stupp
@snazy
, when reviewer
and/or assignee are not set.
—
Robert Stupp
@snazy
48 hours (longer if needed).
>>
>> [1]: http://goo.gl/fyezu5 (CHANGES.txt)
>> [2]: http://goo.gl/iVuCQU (NEWS.txt)
>>
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder, http://www.datastax.com
> @spyced
—
Robert Stupp
@snazy
t be equal - no special “this” or special “that”.
—
Robert Stupp
@snazy
, data will reside on same nodes so that queries and
> application of data can be done locally.
>
> ### What happens next ###
> Assuming I get any feedback I'll post more detailed descriptions of two
> approaches.
>
> I would love to hear your feedback on whole subject. Just to begin
> discussion and pick your interest.
>
> What you think about having more heavy transactions?
> Does this experiment has sense at all?
>
> regards
> --
> Marek Lewandowski
—
Robert Stupp
@snazy
er if needed).
>
> [1]: http://goo.gl/oowQCQ (CHANGES.txt)
> [2]: http://goo.gl/s0RHg4 (NEWS.txt)
—
Robert Stupp
@snazy
package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/3FbKhG (CHANGES.txt)
> [2]: http://goo.gl/sMGs53 (NEWS.txt)
—
Robert Stupp
@snazy
e approach Benedict's been taking lately
>>>>>> w/putting comments inline on a branch for the initial author to
>> inspect
>>>>>> as
>>>>>> that provides immediate locality for a reviewer to write down their
>>>>>> thoughts and the same for the initial developer to ingest them. One
>>>>>> downside to that approach is that the extra barrier to entry makes it
>>>>>> more
>>>>>> of a 1-on-1 conversation rather than an open discussion via JIRA
>>>>>> comments.
>>>>>> Also, if one deletes branches from github we then lose our discussion
>>>>>> history on the review process which is a big problem for digging into
>>> why
>>>>>> certain decisions were made or revised during the process.
>>>>>>
>>>>>> On the competing side, monster comments like this
>>>>>> <
>>>>>>
>>>>>>
>>>
>> https://issues.apache.org/jira/browse/CASSANDRA-6477?focusedCommentId=14617221&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14617221
>>
>>>>>>
>>>>>>>
>>>>>>> (which
>>>>>> is one of multiple to come) are burdensome to create and map into a
>>> JIRA
>>>>>> comment and, in my experience, also a burden to map back into the
>>>>>> code-base
>>>>>> as a developer. Details are lost in translation; I'm comfortable
>>> labeling
>>>>>> this a sub-optimal method of communication.
>>>>>>
>>>>>> So what to do?
>>>>>>
>>>>>> --
>>>>>> Joshua McKenzie
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
—
Robert Stupp
@snazy
as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> Since this is beta, the vote will be open for 24 hours.
>
> [1]: http://goo.gl/YsRffc (CHANGES.txt)
> [2]: http://goo.gl/jFb87y (NEWS.txt)
—
Robert Stupp
@snazy
2.0.x when 2.2
>> comes
>>> out is reasonable, especially considering that 2.2 is realistically a
>> month
>>> or two away even if we can get a beta out this week.
>>>
>>> 2) 3.0.x LTS branch stays, as planned, and helps us stabilise the new
>>>> storage engine
>>>>
>>>
>>> Yes.
>>>
>>>
>>>> 3) in a few months after 2.2 gets released, we EOL 2.1. Users upgrade
>> to
>>>> 2.2, get the same stability as with 2.1.7, plus a few new features
>>>>
>>>
>>> If push comes to shove I'm okay being ambiguous here, but can we just say
>>> "when 3.0 is released we EOL 2.1?"
>>>
>>> P.S. The area I'm most concerned about introducing destabilizing changes
>> in
>>> 2.2 is commitlog; I will follow up to make sure we have a solid QA plan
>>> there.
>>>
>>> --
>>> Jonathan Ellis
>>> Project Chair, Apache Cassandra
>>> co-founder, http://www.datastax.com
>>> @spyced
>>>
>>
>>
>>
>> --
>> Jonathan Ellis
>> Project Chair, Apache Cassandra
>> co-founder, http://www.datastax.com
>> @spyced
>>
—
Robert Stupp
@snazy
ly not the best investment we could make for our
>>>> users
>>>> since 2.2 and 3.0 are relatively close in functionality. I see a
>> couple
>>>> other options without jumping to 3 concurrent stabilization series:*
>>>>
>>>>
>>>>
>>>> * - Extend 2.1.x series and 2.2.x until 4.0, but skip 3.0.x
>> stabilization
>>>> series in favor of tick-tock 3.x- Extend 2.1.x series until 4.0, but
>> stop
>>>> 2.2.x when 3.0 ships in favor of developing 3.0.x insteadThoughts?*
>>>>
>>>> --
>>>> Jonathan Ellis
>>>> Project Chair, Apache Cassandra
>>>> co-founder, http://www.datastax.com
>>>> @spyced
>>
>
>
>
> --
> Thanks,
> Phil Yang
—
Robert Stupp
@snazy
gt;
>>>>>> Current structure has a very big disadvantage - ONE source root for
>>>>>> multiple artifacts published in maven repositories and copying
>> classes
>>>> to
>>>>>> jar AFTER they are compiled. Obviously ant copy task doesn’t follow
>>>> import
>>>>>> statements and does not include dependant classes. For example just
>> by
>>>>>> making test relocations and extraction of clientutil jar on master
>>>> branch
>>>>>> into separate source root I have found a bug where ListSerializer
>>>> depends
>>>>>> on org.apache.cassandra.transpor package. More over clientutil
>>>>>> (MapSerializer) does depends on org.apache.cassandra.db.marshal
>>> package
>>>>>> leading to the fact that it can not be used without cassandra-all
>>>> present
>>>>>> at classpath.
>>>>>> Luckily for cassandra CQL as a new interface reduces thrift and
>>>> clientutil
>>>>>> usage reducing amount of issues reported around these, however this
>>> just
>>>>>> hides a real problem in previous paragraph. I have found a handy
>> tool
>>>> and
>>>>>> made a graph of circular dependencies in cassandra-all.jar. Graph of
>>>>>> results can found here: http://grab.by/FRnO <http://grab.by/FRnO> <
>>>> http://grab.by/FRnO <http://grab.by/FRnO>>. As you
>>>>>> can see this graph has multiple levels and solving it is not a
>> simple
>>>> task.
>>>>>> I am afraid a current way of building and packaging cassandra can
>>> create
>>>>>> huge hiccups when it will come to code rafactorings cause entire
>>>> cassandra
>>>>>> will become a house of cards.
>>>>>> Restructuring project into smaller pieces is also beneficiary for
>>>>>> community since solving bugs in smaller units is definitelly easier.
>>>>>>
>>>>>> At the end of this mail I would like to propose moving Cassandra
>> build
>>>>>> system forward, regardless of tool which will be choosen for it.
>>>> Personally
>>>>>> I can volunteer in maven related changes to extract
>> cassandra-thrift,
>>>>>> cassandra-clientutil and cassandra-all to make regular maven build.
>> It
>>>>>> might be seen as a switch from one big XML into couple smaller. :-)
>>> All
>>>>>> this depends on Cassandra developers decission to devide source
>> roots
>>> or
>>>>>> not.
>>>>>>
>>>>>> Kind regards,
>>>>>> Łukasz Dywicki
>>>>>> —
>>>>>> l...@code-house.org
>>>>>> Twitter: ldywicki
>>>>>> Blog: http://dywicki.pl
>>>>>> Code-House - http://code-house.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Tyler Hobbs
>>>>> DataStax <http://datastax.com/ <http://datastax.com/>>
>>>>
>>>>
>>>
>>
—
Robert Stupp
@snazy
> This won’t be an entirely smooth transition. In particular, you will have
> noticed that 3.1 will get more than a month’s worth of new features while
> we stabilize 3.0 as the last of the old way of doing things, so some
> patience is in order as we try this out. By 3.4 and 3.6 later this year we
> should have a good idea if this is working, and we can make adjustments as
> warranted.
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder, http://www.datastax.com
> @spyced
—
Robert Stupp
@snazy
Try to clear the data + commitlog directory.
At least the primary key for system.schema_functions table has changed in an
incompatible way.
> Am 18.11.2014 um 21:43 schrieb Rajanarayanan Thottuvaikkatumana
> :
>
> I have taken the latest code from trunk, compiled (I have some changes in
> som
Hi,
Since there were some IRC posts regarding "realclean" when dependencies change,
I thought about replacing ant with something else.
It's not just because of that particular realclean but also on dependencies
that don't get actually updated or even out-of-date IDE project files
(.classpath) c
I've informed the docs people yesturday
--
Sent from my iPhone
> Am 24.07.2014 um 18:28 schrieb "Kristine Hahn (JIRA)" :
>
> Kristine Hahn created CASSANDRA-7611:
>
>
>Summary: incomplete CREATE/DROP USER help and tab completion
>
42 matches
Mail list logo
