[jira] [Commented] (CASSANDRA-15402) Make incremental backup configurable per keyspace and table
[ https://issues.apache.org/jira/browse/CASSANDRA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378789#comment-17378789 ] Aleksei Zotov commented on CASSANDRA-15402: --- [~maxwellguo] Thanks for your interest to the project and providing the initial patch version! I briefly checked it and I believe you have not yet come up with another patch version with "configure the table backup under the schema". Moreover, the patch is quite outdated. Are you still interested (and have enough time) in continuing this work? If yes, I'd propose to make a kind of design review: you document the structural changes you're going to make, then community validates the design, and then you start working on the code. I feel such a brief design review would be helpful to come up with the best solution and let you minimize re-work on your side. If you have no time at the moment (which is totally fine!), let's remove assignee from the ticket, so someone else could potentially pick it up and move forward. Anyway, we need to change the status from "PATCH AVAILABLE" to smth else (IN PROGRESS or OPEN) because it assumes having the patch in the final stage. PS: I'm not a project committer, I'm just an enthusiast like you who is hanging around the project. I hope I was not rude and discouraging. It is always great to see people who are ready to dedicate their time to opensource projects. cc: [~blerer] > Make incremental backup configurable per keyspace and table > --- > > Key: CASSANDRA-15402 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15402 > Project: Cassandra > Issue Type: Improvement > Components: Local/Other, Tool/nodetool >Reporter: maxwellguo >Assignee: maxwellguo >Priority: Normal > Labels: pull-request-available > Fix For: 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > We know that when we do backup for cassandra, we can do full bakcup with > snapshot, when we need to backup incremental data , incremental_backup can do > some help . > For snapshot we can just make snapshot for some keyspace/table. but > incremental backup will do all data backup(make hard link for all sstable > that flush from memtable or streaming ). we also know that commitlog's replay > can do some keyspace /table 's filter. > So I think for incremental backup we also need some filter for it.After all > not all keyspace/table is so important to do backup. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16467) speculative retry should allow more friendly params, allowing upgrade from 2.x not to break
[ https://issues.apache.org/jira/browse/CASSANDRA-16467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378774#comment-17378774 ] Aleksei Zotov commented on CASSANDRA-16467: --- Just curious - why did you decide to not include "99p"? The changes look good to me. PS: I'm not a committer, just checking existing patches as per Benjamin's email seeking for reviewers. > speculative retry should allow more friendly params, allowing upgrade from > 2.x not to break > --- > > Key: CASSANDRA-16467 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16467 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > 2.x speculative retry params are case insensitive, while 3.0 and 3.11 have > added case sensitivity. As as result of this, one of our internal > applications suffered an issue during > C* upgrade from 2.x to 3.0. > This ticket is to propose making 3.0 and 3.11 speculative_retry params case > insensitive as well (essentially a slightly modified backport of > CASSANDRA-13876, but not to allow something like "99p" which 4.0 allows) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16188) Add more tests to cover Keyspace and Table metrics
[
https://issues.apache.org/jira/browse/CASSANDRA-16188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378768#comment-17378768
]
Aleksei Zotov commented on CASSANDRA-16188:
---
[~sumanth.pasupuleti]
I checked the changes, in general they look good to me. However, I have two
nits:
# I'd add a static import for {{Assert}}:
{code}
Assert.assertEquals(0, (long) keyspaceMetrics.memtableColumnsCount.getValue());
==>
assertEquals(0, (long) keyspaceMetrics.memtableColumnsCount.getValue());
{code}
I feel "Assert." prefix just pollutes code and makes reading harder.
# I'd use {{assertThat.isGreaterThan}} instead of a synthetic way to do the
same via {{assertTrue}}:
{code}
assertTrue(keyspaceMetrics.memtableColumnsCount.getValue() > 0);
==>
assertThat(keyspaceMetrics.memtableColumnsCount.getValue()).isGreaterThan(0)
{code}
I feel {{isGreaterThan}} looks clearer and more emphatic.
Anyway, both comment are purely stylistic, so it is up to you whether to
address them or not.
PS:
I'm not a project committer, just trying to help in reviewing changes as per
Benjamin's email.
> Add more tests to cover Keyspace and Table metrics
> ---
>
> Key: CASSANDRA-16188
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16188
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/java, Test/unit
>Reporter: Benjamin Lerer
>Assignee: Sumanth Pasupuleti
>Priority: Normal
> Fix For: 4.0.x
>
>
> Several Keyspace and Table related metrics are currently not tested.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14557) Consider adding default and required keyspace replication options
[
https://issues.apache.org/jira/browse/CASSANDRA-14557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378760#comment-17378760
]
Aleksei Zotov commented on CASSANDRA-14557:
---
[~sumanth.pasupuleti]
I put a couple of comments to
[https://github.com/sumanth-pasupuleti/cassandra/commit/f9fb9537e2c6a41b3df13c7c4af2d23b0912b18c].
Could you please check once you have some time.
> Consider adding default and required keyspace replication options
> -
>
> Key: CASSANDRA-14557
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14557
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
>Reporter: Sumanth Pasupuleti
>Assignee: Sumanth Pasupuleti
>Priority: Low
> Labels: 4.0-feature-freeze-review-requested
> Fix For: 4.x
>
> Attachments: 14557-4.0.txt, 14557-trunk.patch
>
>
> Ending up with a keyspace of RF=1 is unfortunately pretty easy in C* right
> now - the system_auth table for example is created with RF=1 (to take into
> account single node setups afaict from CASSANDRA-5112), and a user can
> further create a keyspace with RF=1 posing availability and streaming risks
> (e.g. rebuild).
> I propose we add two configuration options in cassandra.yaml:
> # {{default_keyspace_rf}} (default: 1) - If replication factors are not
> specified, use this number.
> # {{required_minimum_keyspace_rf}} (default: unset) - Prevent users from
> creating a keyspace with an RF less than what is configured
> These settings could further be re-used to:
> * Provide defaults for new keyspaces created with SimpleStrategy or
> NetworkTopologyStrategy (CASSANDRA-14303)
> * Make the automatic token [allocation
> algorithm|https://issues.apache.org/jira/browse/CASSANDRA-13701?focusedCommentId=16095662=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16095662]
> interface more intuitive allowing easy use of the new token allocation
> algorithm.
> At the end of the day, if someone really wants to allow RF=1, they simply
> don’t set the setting. For backwards compatibility the default remains 1 and
> C* would create with RF=1, and would default to current behavior of allowing
> any RF on keyspaces.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15438) MerkleTrees viriables renaming tree -> trees
[ https://issues.apache.org/jira/browse/CASSANDRA-15438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378708#comment-17378708 ] Aleksei Zotov commented on CASSANDRA-15438: --- Hi [~xiangwang]! Thanks for the interest to the project! I checked the patch and I totally support the idea of renaming. However, the project has a consensus to not touch the code unless it is a part of smth that inevitably requires a change (feature development, bug fixing, etc). In other words, it is pretty hard to get such a refactoring approved and merged. Even though it might sound weird and counter productive, there is a clear reason and background for that. Currently the project maintains branches for multiple versions. Some branches take fixes only while others new features and fixes. Obviously there are significant differences between old and new branches and sometimes it is extremely hard to propagate certain changes to old branches. Such refactoring changes increase the difference between branches which consequently increases merging complexity even more. That's why the project took the approach to make refactoring during feature development (like "if you touch some code, please, make it clean and clear; otherwise don't touch it"). Another reason why such changes are unlikely to get merged is a shortage of committers time - it is hard to get their attention to "zero business value" changes (despite they are still useful from technical perspective). I think you can see yourself that no-one paid attention to this ticket for more that 2 years. With that being said, I believe it makes sense to get this ticket closed without anything being merged. Alternative way would be to prepare a bunch of patches for multiple existing branches and try to convince the community to pick them up, however, I doubt it will work out unless you have an enormous aspiration. [~blerer] your input would be highly appreciated. PS: I'm not a project committer, I'm just an enthusiast like you who is hanging around the project. Some time ago I struggled with the same problem of being unable to merge my neat changes. However, after a few cycles of propagating changes to old branches I realized why the community took the path of minimizing "unnecessary" changes. I hope I was not rude and discouraging. It is always great to see people who are ready to dedicate their time to opensource projects. If you still have time and desire to contribute something, please, check this page: [https://cassandra.apache.org/doc/latest/development/patches.html#choosing-what-to-work-on]. And feel free to ping me on Jira or Slack for support. > MerkleTrees viriables renaming tree -> trees > > > Key: CASSANDRA-15438 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15438 > Project: Cassandra > Issue Type: Improvement >Reporter: xiangwang >Assignee: xiangwang >Priority: Normal > Attachments: 0001-Rename-MerkleTrees-tree-to-MerkleTrees-trees.patch > > > It's confusing that the virable tree is sometimes MerkleTrees instead of > MerkleTree. > I'd like to rename "MerkleTrees tree" to "MerkleTrees trees" to make the code > easier to read. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16557) (3.0,3.11) Migrate dependency handling from maven-ant-tasks to resolver-ant-tasks
[
https://issues.apache.org/jira/browse/CASSANDRA-16557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370223#comment-17370223
]
Michael Semb Wever edited comment on CASSANDRA-16557 at 7/11/21, 4:08 PM:
--
Patches
-
[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/16557/3.11]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/923/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/923/pipeline]
-
[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/16557/3.0]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/922/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/922/pipeline]
(back-ported commits kept individual for review readability)
…WIP…
was (Author: michaelsembwever):
Patches
-
[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/16557/3.11]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/921/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/921/pipeline]
-
[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/16557/3.0]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/920/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/920/pipeline]
(back-ported commits kept individual for review readability)
…WIP…
> (3.0,3.11) Migrate dependency handling from maven-ant-tasks to
> resolver-ant-tasks
> -
>
> Key: CASSANDRA-16557
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16557
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: High
> Fix For: 3.0.x, 3.11.x
>
>
> Backport CASSANDRA-16391 to 2.2, 3.0, and 3.11
> This ticket is on hold until the ASF legal clears up its policy, and the
> project confirms the approach it wants to take with {{lib/}} dependencies.
> See [~benedict] comment
> [here|https://issues.apache.org/jira/browse/CASSANDRA-16391?focusedCommentId=17313754=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17313754].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16557) (3.0,3.11) Migrate dependency handling from maven-ant-tasks to resolver-ant-tasks
[
https://issues.apache.org/jira/browse/CASSANDRA-16557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370223#comment-17370223
]
Michael Semb Wever edited comment on CASSANDRA-16557 at 7/11/21, 4:08 PM:
--
Patches
-
[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/16557/3.11]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/923/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/923/pipeline]
-
[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/16557/3.0]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/922/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/922/pipeline]
(back-ported commits kept individual for review readability, they will be
squashed)
was (Author: michaelsembwever):
Patches
-
[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/16557/3.11]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/923/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/923/pipeline]
-
[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/16557/3.0]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/922/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/922/pipeline]
(back-ported commits kept individual for review readability)
> (3.0,3.11) Migrate dependency handling from maven-ant-tasks to
> resolver-ant-tasks
> -
>
> Key: CASSANDRA-16557
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16557
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: High
> Fix For: 3.0.x, 3.11.x
>
>
> Backport CASSANDRA-16391 to 2.2, 3.0, and 3.11
> This ticket is on hold until the ASF legal clears up its policy, and the
> project confirms the approach it wants to take with {{lib/}} dependencies.
> See [~benedict] comment
> [here|https://issues.apache.org/jira/browse/CASSANDRA-16391?focusedCommentId=17313754=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17313754].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16557) (3.0,3.11) Migrate dependency handling from maven-ant-tasks to resolver-ant-tasks
[
https://issues.apache.org/jira/browse/CASSANDRA-16557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370223#comment-17370223
]
Michael Semb Wever edited comment on CASSANDRA-16557 at 7/11/21, 4:08 PM:
--
Patches
-
[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/16557/3.11]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/923/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/923/pipeline]
-
[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/16557/3.0]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/922/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/922/pipeline]
(back-ported commits kept individual for review readability)
was (Author: michaelsembwever):
Patches
-
[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/16557/3.11]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/923/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/923/pipeline]
-
[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/16557/3.0]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/922/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/922/pipeline]
(back-ported commits kept individual for review readability)
…WIP…
> (3.0,3.11) Migrate dependency handling from maven-ant-tasks to
> resolver-ant-tasks
> -
>
> Key: CASSANDRA-16557
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16557
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: High
> Fix For: 3.0.x, 3.11.x
>
>
> Backport CASSANDRA-16391 to 2.2, 3.0, and 3.11
> This ticket is on hold until the ASF legal clears up its policy, and the
> project confirms the approach it wants to take with {{lib/}} dependencies.
> See [~benedict] comment
> [here|https://issues.apache.org/jira/browse/CASSANDRA-16391?focusedCommentId=17313754=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17313754].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16557) (3.0,3.11) Migrate dependency handling from maven-ant-tasks to resolver-ant-tasks
[
https://issues.apache.org/jira/browse/CASSANDRA-16557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378688#comment-17378688
]
Michael Semb Wever commented on CASSANDRA-16557:
Because the ASF policy has been clarified as not strictly enforcing against
compiled code or dependencies in the source artefact, back-porting to 2.2 has
been dropped (as it is going into critical-fix only mode as soon as 4.0.0 is
released).
> (3.0,3.11) Migrate dependency handling from maven-ant-tasks to
> resolver-ant-tasks
> -
>
> Key: CASSANDRA-16557
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16557
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: High
> Fix For: 3.0.x, 3.11.x
>
>
> Backport CASSANDRA-16391 to 2.2, 3.0, and 3.11
> This ticket is on hold until the ASF legal clears up its policy, and the
> project confirms the approach it wants to take with {{lib/}} dependencies.
> See [~benedict] comment
> [here|https://issues.apache.org/jira/browse/CASSANDRA-16391?focusedCommentId=17313754=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17313754].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16557) (3.0,3.11) Migrate dependency handling from maven-ant-tasks to resolver-ant-tasks
[
https://issues.apache.org/jira/browse/CASSANDRA-16557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16557:
---
Summary: (3.0,3.11) Migrate dependency handling from maven-ant-tasks to
resolver-ant-tasks (was: (2.2,3.0,3.11) Migrate dependency handling from
maven-ant-tasks to resolver-ant-tasks)
> (3.0,3.11) Migrate dependency handling from maven-ant-tasks to
> resolver-ant-tasks
> -
>
> Key: CASSANDRA-16557
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16557
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: High
> Fix For: 2.2.x, 3.0.x, 3.11.x
>
>
> Backport CASSANDRA-16391 to 2.2, 3.0, and 3.11
> This ticket is on hold until the ASF legal clears up its policy, and the
> project confirms the approach it wants to take with {{lib/}} dependencies.
> See [~benedict] comment
> [here|https://issues.apache.org/jira/browse/CASSANDRA-16391?focusedCommentId=17313754=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17313754].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16557) (3.0,3.11) Migrate dependency handling from maven-ant-tasks to resolver-ant-tasks
[
https://issues.apache.org/jira/browse/CASSANDRA-16557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16557:
---
Fix Version/s: (was: 2.2.x)
> (3.0,3.11) Migrate dependency handling from maven-ant-tasks to
> resolver-ant-tasks
> -
>
> Key: CASSANDRA-16557
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16557
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: High
> Fix For: 3.0.x, 3.11.x
>
>
> Backport CASSANDRA-16391 to 2.2, 3.0, and 3.11
> This ticket is on hold until the ASF legal clears up its policy, and the
> project confirms the approach it wants to take with {{lib/}} dependencies.
> See [~benedict] comment
> [here|https://issues.apache.org/jira/browse/CASSANDRA-16391?focusedCommentId=17313754=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17313754].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16557) (2.2,3.0,3.11) Migrate dependency handling from maven-ant-tasks to resolver-ant-tasks
[
https://issues.apache.org/jira/browse/CASSANDRA-16557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370223#comment-17370223
]
Michael Semb Wever edited comment on CASSANDRA-16557 at 7/11/21, 9:03 AM:
--
Patches
-
[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/16557/3.11]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/921/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/921/pipeline]
-
[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/16557/3.0]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/920/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/920/pipeline]
(back-ported commits kept individual for review readability)
…WIP…
was (Author: michaelsembwever):
Patches
-
[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/16557/3.11]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/917/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/917/pipeline]
-
[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/16557/3.0]
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/919/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/919/pipeline]
(back-ported commits kept individual for review readability)
…WIP…
> (2.2,3.0,3.11) Migrate dependency handling from maven-ant-tasks to
> resolver-ant-tasks
> -
>
> Key: CASSANDRA-16557
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16557
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: High
> Fix For: 2.2.x, 3.0.x, 3.11.x
>
>
> Backport CASSANDRA-16391 to 2.2, 3.0, and 3.11
> This ticket is on hold until the ASF legal clears up its policy, and the
> project confirms the approach it wants to take with {{lib/}} dependencies.
> See [~benedict] comment
> [here|https://issues.apache.org/jira/browse/CASSANDRA-16391?focusedCommentId=17313754=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17313754].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
