Re: Can we upgrade Guava to the same version as master on 3.11 branch?
So far no opinion for or against the guava upgrade. Would someone review my change if I create a PR for this? Jeff, thank you for checking. On Fri, Feb 28, 2020 at 12:21 PM Jeff Jirsa wrote: > > This isn't an opinion for or against upgrading guava, just a note that the > two classes mentioned in that vulnerability are not actually in the > codebase: > > jjirsa:cassandra jjirsa$ git checkout cassandra-3.11 > Checking out files: 100% (3212/3212), done.) > Switched to branch 'cassandra-3.11' > Your branch is up to date with 'origin/cassandra-3.11'. > jjirsa:cassandra jjirsa$ grep -r CompoundOrdering src/ > jjirsa:cassandra jjirsa$ grep -r AtomicDoubleArray src/ > jjirsa:cassandra jjirsa$ > > > > On Fri, Feb 28, 2020 at 7:33 AM Tomo Suzuki > wrote: > > > Hi Cassandra developers, > > > > Today I learned that Guava 18 has "severe" vulnerability [1,2]. As per > > code freezing, Cassandra 3.11 still accepts security related PRs. > > Will Cassandra team accept a pull request to upgrade Guava in 3.11 > > [3], if I create one? > > > > [1]: https://search.maven.org/artifact/com.google.guava/guava/18.0/bundle > > [2]: > > https://ossindex.sonatype.org/vuln/24585a7f-eb6b-4d8d-a2a9-a6f16cc7c1d0 > > [3]: https://issues.apache.org/jira/browse/CASSANDRA-15453 > > > > On Mon, Dec 16, 2019 at 12:45 PM Tomo Suzuki wrote: > > > > > > Russell, > > > > > > That's great to hear. Then I'll wait for Cassandra 4 release for now. > > > In the meantime, I found an outdated dependency in Cassandra. Ticketed > > > [1]. > > > > > > [1]: CASSANDRA-15455 Upgrade com.carrotsearch:hppc dependency > > > > > > > > > On Mon, Dec 16, 2019 at 12:08 AM Russell Spitzer > > > wrote: > > > > > > > > The hadoop formats should be compatible with any Cassandra version > > > > regardless of which Cassandra-all you include since they communicate > > with > > > > the driver under the hood and not Cassandra internal libraries. This > > means > > > > you should feel free to use Cassandra 4 in your integration without > > fear of > > > > losing backwards compatibility. In fact it should be able to speak to > > > > Cassandra 2.x as well. > > > > > > > > On Sun, Dec 15, 2019, 10:24 PM Tomo Suzuki > > > > > > wrote: > > > > > > > > > Hi Russell, > > > > > > > > > > Yes, Apache Beam uses hadoop format for Cassandra IO [1]. That test > > > > > (HadoopFormatIOCassandraTest) failed [2] when I tried to upgrade > > Guava > > > > > version. Added this information to the ticket. > > > > > > > > > > [1]: https://beam.apache.org/documentation/io/built-in/hadoop/ > > > > > [2]: > > > > > > > https://github.com/GoogleCloudPlatform/cloud-opensource-java/issues/1028#issuecomment-557680928 > > > > > > > > > > On Sun, Dec 15, 2019 at 10:36 PM Russell Spitzer > > > > > wrote: > > > > > > > > > > > > Why does the beam integration rely on Cassandra all, does it use > > the > > > > > hadoop > > > > > > formats? > > > > > > > > > > > > On Sun, Dec 15, 2019, 9:07 PM Tomo Suzuki > > > > > > > > wrote: > > > > > > > > > > > > > Hi Cassandra developers, > > > > > > > > > > > > > > I want to backport the Guava version upgrade (CASSANDRA-15248) > > into > > > > > > > 3.11 branch, so that cassandra-all:3.11.X works with higher > > version of > > > > > > > Guava. > > > > > > > I just created a ticket > > > > > > > https://issues.apache.org/jira/browse/CASSANDRA-15453 explaining > > > > > > > background. > > > > > > > > > > > > > > Before committing anything, I'd like to hear any opinion on the > > > > > > > backporting. What do you think? > > > > > > > > > > > > > > Regards, > > > > > > > Tomo > > > > > > > > > > > > > > > > - > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > > > > > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Regards, > > > > > Tomo > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > > > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > > > > > > > > > > > > > > > > > > -- > > > Regards, > > > Tomo > > > > > > > > -- > > Regards, > > Tomo > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > -- Regards, Tomo - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
another alpha?
Looking at CHANGES.txt, we've got 30+ changes since the last alpha. I think it's a good time to cut another alpha release. The biggest item here is Python 3 support for cqlsh. It would be good to get as much feedback as possible on this since it's such a critical tool. Here's what's changed: Include finalized pending sstables in preview repair (CASSANDRA-15553) Reverted to the original behavior of CLUSTERING ORDER on CREATE TABLE (CASSANDRA-15271) Correct inaccurate logging message (CASSANDRA-15549) Add documentation of dynamo (CASSANDRA-15486) Added documentation for Guarantees (CASSANDRA-15482) Added documentation for audit logging (CASSANDRA-15474) Unset GREP_OPTIONS (CASSANDRA-14487) Added streaming documentation (CASSANDRA-15477) Update to Python driver 3.21 for cqlsh (CASSANDRA-14872) Added bulk loading documentation (CASSANDRA-15480) Updated overview documentation (CASSANDRA-15483) Added CDC and speculative retry documentation to DDL section (CASSANDRA-15492) Fix missing Keyspaces in cqlsh describe output (CASSANDRA-15576) Fix multi DC nodetool status output (CASSANDRA-15305) Added documentation covering new Netty based internode messaging (CASSANDRA-15478) Add documentation of hints (CASSANDRA-15491) updateCoordinatorWriteLatencyTableMetric can produce misleading metrics (CASSANDRA-15569) Added documentation for read repair and an example of full repair (CASSANDRA-15485) Make cqlsh and cqlshlib Python 2 & 3 compatible (CASSANDRA-10190) Added documentation for Full Query Logging (CASSANDRA-15475) Added documentation for backups (CASSANDRA-15479) Documentation gives the wrong instruction to activate remote jmx (CASSANDRA-15535) Improve the description of nodetool listsnapshots command (CASSANDRA-14587) allow embedded cassandra launched from a one-jar or uno-jar (CASSANDRA-15494) Update hppc library to version 0.8.1 (CASSANDRA-12995) Limit the dependencies used by UDFs/UDAs (CASSANDRA-14737) Make native_transport_max_concurrent_requests_in_bytes updatable (CASSANDRA-15519) Cleanup and improvements to IndexInfo/ColumnIndex (CASSANDRA-15469) Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB & Bytes (CASSANDRA-15470) Merged from 3.0: Run evictFromMembership in GossipStage (CASSANDRA-15592) Merged from 2.2: Allow EXTRA_CLASSPATH to work on tar/source installations (CASSANDRA-15567) Thoughts? Jon
Re: another alpha?
The clash change is important to get out, but i'd like to see a few more 'moving parts' in place since most of these changes are docs. Thinking specifically of something like CASSANDRA-15564 (repair coordinator refactor). I'm -0 otherwise. On Tue, Mar 3, 2020 at 10:27 AM Jon Haddad wrote: > Looking at CHANGES.txt, we've got 30+ changes since the last alpha. I > think it's a good time to cut another alpha release. The biggest item here > is Python 3 support for cqlsh. It would be good to get as much feedback as > possible on this since it's such a critical tool. > > Here's what's changed: > > Include finalized pending sstables in preview repair (CASSANDRA-15553) > Reverted to the original behavior of CLUSTERING ORDER on CREATE TABLE > (CASSANDRA-15271) > Correct inaccurate logging message (CASSANDRA-15549) > Add documentation of dynamo (CASSANDRA-15486) > Added documentation for Guarantees (CASSANDRA-15482) > Added documentation for audit logging (CASSANDRA-15474) > Unset GREP_OPTIONS (CASSANDRA-14487) > Added streaming documentation (CASSANDRA-15477) > Update to Python driver 3.21 for cqlsh (CASSANDRA-14872) > Added bulk loading documentation (CASSANDRA-15480) > Updated overview documentation (CASSANDRA-15483) > Added CDC and speculative retry documentation to DDL section > (CASSANDRA-15492) > Fix missing Keyspaces in cqlsh describe output (CASSANDRA-15576) > Fix multi DC nodetool status output (CASSANDRA-15305) > Added documentation covering new Netty based internode messaging > (CASSANDRA-15478) > Add documentation of hints (CASSANDRA-15491) > updateCoordinatorWriteLatencyTableMetric can produce misleading metrics > (CASSANDRA-15569) > Added documentation for read repair and an example of full repair > (CASSANDRA-15485) > Make cqlsh and cqlshlib Python 2 & 3 compatible (CASSANDRA-10190) > Added documentation for Full Query Logging (CASSANDRA-15475) > Added documentation for backups (CASSANDRA-15479) > Documentation gives the wrong instruction to activate remote jmx > (CASSANDRA-15535) > Improve the description of nodetool listsnapshots command (CASSANDRA-14587) > allow embedded cassandra launched from a one-jar or uno-jar > (CASSANDRA-15494) > Update hppc library to version 0.8.1 (CASSANDRA-12995) > Limit the dependencies used by UDFs/UDAs (CASSANDRA-14737) > Make native_transport_max_concurrent_requests_in_bytes updatable > (CASSANDRA-15519) > Cleanup and improvements to IndexInfo/ColumnIndex (CASSANDRA-15469) > Potential Overflow in DatabaseDescriptor Functions That Convert Between > KB/MB & Bytes (CASSANDRA-15470) > Merged from 3.0: > Run evictFromMembership in GossipStage (CASSANDRA-15592) > Merged from 2.2: > Allow EXTRA_CLASSPATH to work on tar/source installations (CASSANDRA-15567) > > Thoughts? > Jon >
Re: another alpha?
+1 I think the cqlsh change itself is sufficient. However, if we're close to having 15564 done we can wait. Dinesh > On Mar 2, 2020, at 1:59 PM, Nate McCall wrote: > > The clash change is important to get out, but i'd like to see a few more > 'moving parts' in place since most of these changes are docs. Thinking > specifically of something like CASSANDRA-15564 (repair coordinator > refactor). > > I'm -0 otherwise. > > On Tue, Mar 3, 2020 at 10:27 AM Jon Haddad wrote: > >> Looking at CHANGES.txt, we've got 30+ changes since the last alpha. I >> think it's a good time to cut another alpha release. The biggest item here >> is Python 3 support for cqlsh. It would be good to get as much feedback as >> possible on this since it's such a critical tool. >> >> Here's what's changed: >> >> Include finalized pending sstables in preview repair (CASSANDRA-15553) >> Reverted to the original behavior of CLUSTERING ORDER on CREATE TABLE >> (CASSANDRA-15271) >> Correct inaccurate logging message (CASSANDRA-15549) >> Add documentation of dynamo (CASSANDRA-15486) >> Added documentation for Guarantees (CASSANDRA-15482) >> Added documentation for audit logging (CASSANDRA-15474) >> Unset GREP_OPTIONS (CASSANDRA-14487) >> Added streaming documentation (CASSANDRA-15477) >> Update to Python driver 3.21 for cqlsh (CASSANDRA-14872) >> Added bulk loading documentation (CASSANDRA-15480) >> Updated overview documentation (CASSANDRA-15483) >> Added CDC and speculative retry documentation to DDL section >> (CASSANDRA-15492) >> Fix missing Keyspaces in cqlsh describe output (CASSANDRA-15576) >> Fix multi DC nodetool status output (CASSANDRA-15305) >> Added documentation covering new Netty based internode messaging >> (CASSANDRA-15478) >> Add documentation of hints (CASSANDRA-15491) >> updateCoordinatorWriteLatencyTableMetric can produce misleading metrics >> (CASSANDRA-15569) >> Added documentation for read repair and an example of full repair >> (CASSANDRA-15485) >> Make cqlsh and cqlshlib Python 2 & 3 compatible (CASSANDRA-10190) >> Added documentation for Full Query Logging (CASSANDRA-15475) >> Added documentation for backups (CASSANDRA-15479) >> Documentation gives the wrong instruction to activate remote jmx >> (CASSANDRA-15535) >> Improve the description of nodetool listsnapshots command (CASSANDRA-14587) >> allow embedded cassandra launched from a one-jar or uno-jar >> (CASSANDRA-15494) >> Update hppc library to version 0.8.1 (CASSANDRA-12995) >> Limit the dependencies used by UDFs/UDAs (CASSANDRA-14737) >> Make native_transport_max_concurrent_requests_in_bytes updatable >> (CASSANDRA-15519) >> Cleanup and improvements to IndexInfo/ColumnIndex (CASSANDRA-15469) >> Potential Overflow in DatabaseDescriptor Functions That Convert Between >> KB/MB & Bytes (CASSANDRA-15470) >> Merged from 3.0: >> Run evictFromMembership in GossipStage (CASSANDRA-15592) >> Merged from 2.2: >> Allow EXTRA_CLASSPATH to work on tar/source installations (CASSANDRA-15567) >> >> Thoughts? >> Jon >> - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: another alpha?
Personally would prefer to wait on CASSANDRA-15358. In my testing alpha2+ fails with this frequently on deployed clusters (actively testing patch). > On Mar 2, 2020, at 2:25 PM, Dinesh Joshi wrote: > > +1 > > I think the cqlsh change itself is sufficient. However, if we're close to > having 15564 done we can wait. > > Dinesh > >> On Mar 2, 2020, at 1:59 PM, Nate McCall wrote: >> >> The clash change is important to get out, but i'd like to see a few more >> 'moving parts' in place since most of these changes are docs. Thinking >> specifically of something like CASSANDRA-15564 (repair coordinator >> refactor). >> >> I'm -0 otherwise. >> >> On Tue, Mar 3, 2020 at 10:27 AM Jon Haddad wrote: >> >>> Looking at CHANGES.txt, we've got 30+ changes since the last alpha. I >>> think it's a good time to cut another alpha release. The biggest item here >>> is Python 3 support for cqlsh. It would be good to get as much feedback as >>> possible on this since it's such a critical tool. >>> >>> Here's what's changed: >>> >>> Include finalized pending sstables in preview repair (CASSANDRA-15553) >>> Reverted to the original behavior of CLUSTERING ORDER on CREATE TABLE >>> (CASSANDRA-15271) >>> Correct inaccurate logging message (CASSANDRA-15549) >>> Add documentation of dynamo (CASSANDRA-15486) >>> Added documentation for Guarantees (CASSANDRA-15482) >>> Added documentation for audit logging (CASSANDRA-15474) >>> Unset GREP_OPTIONS (CASSANDRA-14487) >>> Added streaming documentation (CASSANDRA-15477) >>> Update to Python driver 3.21 for cqlsh (CASSANDRA-14872) >>> Added bulk loading documentation (CASSANDRA-15480) >>> Updated overview documentation (CASSANDRA-15483) >>> Added CDC and speculative retry documentation to DDL section >>> (CASSANDRA-15492) >>> Fix missing Keyspaces in cqlsh describe output (CASSANDRA-15576) >>> Fix multi DC nodetool status output (CASSANDRA-15305) >>> Added documentation covering new Netty based internode messaging >>> (CASSANDRA-15478) >>> Add documentation of hints (CASSANDRA-15491) >>> updateCoordinatorWriteLatencyTableMetric can produce misleading metrics >>> (CASSANDRA-15569) >>> Added documentation for read repair and an example of full repair >>> (CASSANDRA-15485) >>> Make cqlsh and cqlshlib Python 2 & 3 compatible (CASSANDRA-10190) >>> Added documentation for Full Query Logging (CASSANDRA-15475) >>> Added documentation for backups (CASSANDRA-15479) >>> Documentation gives the wrong instruction to activate remote jmx >>> (CASSANDRA-15535) >>> Improve the description of nodetool listsnapshots command (CASSANDRA-14587) >>> allow embedded cassandra launched from a one-jar or uno-jar >>> (CASSANDRA-15494) >>> Update hppc library to version 0.8.1 (CASSANDRA-12995) >>> Limit the dependencies used by UDFs/UDAs (CASSANDRA-14737) >>> Make native_transport_max_concurrent_requests_in_bytes updatable >>> (CASSANDRA-15519) >>> Cleanup and improvements to IndexInfo/ColumnIndex (CASSANDRA-15469) >>> Potential Overflow in DatabaseDescriptor Functions That Convert Between >>> KB/MB & Bytes (CASSANDRA-15470) >>> Merged from 3.0: >>> Run evictFromMembership in GossipStage (CASSANDRA-15592) >>> Merged from 2.2: >>> Allow EXTRA_CLASSPATH to work on tar/source installations (CASSANDRA-15567) >>> >>> Thoughts? >>> Jon >>> > > > - > 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
Re: another alpha?
On Tue, 3 Mar 2020, at 00:57, David Capwell wrote: > Personally would prefer to wait on CASSANDRA-15358. In my testing > alpha2+ fails with this frequently on deployed clusters (actively > testing patch). > >> On Mar 2, 2020, at 1:59 PM, Nate McCall wrote: > >> The clash change is important to get out, but i'd like to see a few more > >> 'moving parts' in place since most of these changes are docs. Thinking > >> specifically of something like CASSANDRA-15564 (repair coordinator > >> refactor). I'm happy to cut a release later this week or next, once these and others yet to be mentioned get merged. We need to do another round on the release process to wrap up CASSANDRA-14970. - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
