[jira] [Updated] (CASSANDRA-19251) [Analytics] Speed up integration tests
[ https://issues.apache.org/jira/browse/CASSANDRA-19251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Guerrero updated CASSANDRA-19251: --- Reviewers: Yifan Cai Status: Review In Progress (was: Patch Available) > [Analytics] Speed up integration tests > -- > > Key: CASSANDRA-19251 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19251 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Time Spent: 0.5h > Remaining Estimate: 0h > > We can speed up the integration tests by reusing the in-jvm dtest cluster in > a test class when possible. The proposal has the following pros and cons. > Pros: > # Ability to iterate faster by running tests faster > # Reduce the resources needed to run tests > # Reduce flakiness due to resource allocation issues > # Remove necessity to spin up a new process for bulk writes > # Adds the ability to use parameterized tests (for example different CLs for > the same test) > Cons: > # Potentially having to add new test classes > # No longer be able to use the {{CassandraIntegrationTest}} annotation > # Can only test a single Cassandra version at a time > In terms of resources, the proposed approach brings huge improvements by > reducing the current runtime of about 1 hour down to 20 minutes. > Additionally, we reduce the resource requirements for the integration tests, > and add the ability to iterate faster. Reduces flakiness which helps surface > real issues in the tests. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19251) [Analytics] Speed up integration tests
[ https://issues.apache.org/jira/browse/CASSANDRA-19251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Guerrero updated CASSANDRA-19251: --- Status: Ready to Commit (was: Review In Progress) > [Analytics] Speed up integration tests > -- > > Key: CASSANDRA-19251 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19251 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Time Spent: 0.5h > Remaining Estimate: 0h > > We can speed up the integration tests by reusing the in-jvm dtest cluster in > a test class when possible. The proposal has the following pros and cons. > Pros: > # Ability to iterate faster by running tests faster > # Reduce the resources needed to run tests > # Reduce flakiness due to resource allocation issues > # Remove necessity to spin up a new process for bulk writes > # Adds the ability to use parameterized tests (for example different CLs for > the same test) > Cons: > # Potentially having to add new test classes > # No longer be able to use the {{CassandraIntegrationTest}} annotation > # Can only test a single Cassandra version at a time > In terms of resources, the proposed approach brings huge improvements by > reducing the current runtime of about 1 hour down to 20 minutes. > Additionally, we reduce the resource requirements for the integration tests, > and add the ability to iterate faster. Reduces flakiness which helps surface > real issues in the tests. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-website) branch asf-staging updated (24d17bb25 -> 5657619f2)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 24d17bb25 generate docs for 8ea493af new 5657619f2 generate docs for 8ea493af This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (24d17bb25) \ N -- N -- N refs/heads/asf-staging (5657619f2) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .../cassandra/tools/nodetool/resumehandoff.html| 3 ++- .../cassandra/tools/nodetool/resumehandoff.html| 3 ++- .../cassandra/tools/nodetool/resumehandoff.html| 3 ++- .../cassandra/tools/nodetool/resumehandoff.html| 3 ++- .../cassandra/tools/nodetool/resumehandoff.html| 3 ++- .../cassandra/tools/nodetool/resumehandoff.html| 3 ++- content/search-index.js| 2 +- site-ui/build/ui-bundle.zip| Bin 4883726 -> 4883726 bytes 8 files changed, 13 insertions(+), 7 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19256) [Analytics] Update Spark version to 3.3 and release to maven central
[ https://issues.apache.org/jira/browse/CASSANDRA-19256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-19256: - Summary: [Analytics] Update Spark version to 3.3 and release to maven central (was: Update Spark version to 3.3 and release to maven central) > [Analytics] Update Spark version to 3.3 and release to maven central > > > Key: CASSANDRA-19256 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19256 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Adrian Cole >Priority: Normal > > I was told this library will replace the datastax one, and be more performant > along the way. In order to use this to solve a goal, I need a release of > Spark 3.3 on Scala 2.13. Right now, it seems on 3.2 > https://github.com/search?q=repo%3Aapache%2Fcassandra-analytics+spark+language%3AGradle=code=Gradle > Also, the README should include how to get this library as I can't find > anything like it on Maven Central. Perhaps it isn't published, yet? > Once done, I can try replacing the datastax code in > https://github.com/openzipkin/zipkin-dependencies -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19256) Update Spark version to 3.3 and release to maven central
[ https://issues.apache.org/jira/browse/CASSANDRA-19256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-19256: --- Component/s: Analytics Library > Update Spark version to 3.3 and release to maven central > > > Key: CASSANDRA-19256 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19256 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Adrian Cole >Priority: Normal > > I was told this library will replace the datastax one, and be more performant > along the way. In order to use this to solve a goal, I need a release of > Spark 3.3 on Scala 2.13. Right now, it seems on 3.2 > https://github.com/search?q=repo%3Aapache%2Fcassandra-analytics+spark+language%3AGradle=code=Gradle > Also, the README should include how to get this library as I can't find > anything like it on Maven Central. Perhaps it isn't published, yet? > Once done, I can try replacing the datastax code in > https://github.com/openzipkin/zipkin-dependencies -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19256) Update Spark version to 3.3 and release to maven central
[ https://issues.apache.org/jira/browse/CASSANDRA-19256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805050#comment-17805050 ] Michael Semb Wever commented on CASSANDRA-19256: [~frankgh], putting this on your radar. > Update Spark version to 3.3 and release to maven central > > > Key: CASSANDRA-19256 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19256 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Adrian Cole >Priority: Normal > > I was told this library will replace the datastax one, and be more performant > along the way. In order to use this to solve a goal, I need a release of > Spark 3.3 on Scala 2.13. Right now, it seems on 3.2 > https://github.com/search?q=repo%3Aapache%2Fcassandra-analytics+spark+language%3AGradle=code=Gradle > Also, the README should include how to get this library as I can't find > anything like it on Maven Central. Perhaps it isn't published, yet? > Once done, I can try replacing the datastax code in > https://github.com/openzipkin/zipkin-dependencies -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org