1. 04 Jun, 2020 4 commits
  2. 03 Jun, 2020 2 commits
    • polandll's avatar
      Improving Cassandra configuration docs · 57a63f85
      polandll authored
      * Update copyright date to 2020
      * Add glossary
      * Rearranged rackdc for better flow
      * Add topologies properties file
      * Add commitlog_archiving file
      * Add logback.xml info
      * jvm.options files
      * Removed invalid reference to wiki from configuration file
      Patch by Lorina Poland; Reviewed by Jon Haddad for CASSANDRA-15822
    • Stefan Miklosovic's avatar
      Add fqltool and auditlogviewer to rpm and deb packages · ecf2c9cc
      Stefan Miklosovic authored
       patch by Stefan Miklosovic; reviewed by Mick Semb Wever for CASSANDRA-14712
  3. 02 Jun, 2020 1 commit
    • Jon Meredith's avatar
      Include DROPPED_COLUMNS in schema digest computation. · c230ec9e
      Jon Meredith authored
      CASSANDRA-11050 introduced dropped columns but excluded it from schema digest computations, with
      a comment to include the table in the next major release - 4.0.
      The patch now includes DROPPED_COLUMNS in the schema digest computation.
      Patch by Jon Meredith; reviewed by Aleksey Yeschenko for CASSANDRA-15843
  4. 29 May, 2020 3 commits
  5. 28 May, 2020 1 commit
  6. 27 May, 2020 4 commits
    • Sylvain Lebresne's avatar
    • Sylvain Lebresne's avatar
    • Sylvain Lebresne's avatar
      Fix LegacyLayout handling of non-selected collection tombstones · c8a28346
      Sylvain Lebresne authored
      If a collection tombstone is not included by a query, it can be ignored,
      but it currently made `LegacyLayout.CellGrouper#addCollectionTombstone`
      return `false`, which made it stop the current row, which is incorrect
      (this can potentially lead to a duplicate row). This patch changes it
      to return `true`.
      Patch by Sylvain Lebresne; reviewed by Marcus Eriksson & Aleksey
      Yeschenko for CASSANDRA-15805
    • Sylvain Lebresne's avatar
      Fix legacy handling of RangeTombstone with collection ones · 8358e198
      Sylvain Lebresne authored
      When a multi-row range tombstone interacts with a a collection tombstone
      within one of a covered row, the resulting range tombstone in the legacy
      format will start in the middle of the row and extend past said row and
      it needs special handling.
      Before this commit, the code deserializing that RT was making it
      artificially start at the end of the row (in which the collection
      tombstone is), but that means that when `LegacyLayout.CellGrouper`
      encountered it, it decided the row was finished, even if it was not,
      leading to potential row duplication.
      The patch solves this by:
      1. making that problematic tombstone start at the beginning of the row
      instead of its end (to avoid code deciding the row is over).
      2. modify `UnfilteredDeserializer` to 'split' that range tombstone into
      a row tombstone for the row it covers, which is handled as a normal row
      tombstone, and push the rest of the range tombstone (that starts after
      the row and extends to the original end of the RT) to be handled after
      that row is fully "grouped".
      The patch also removes the possibility of getting an empty row from
      `LegacyLayout#getNextRow` to avoid theoretical problems with that.
      Patch by Sylvain Lebresne; reviewed by Marcus Eriksson & Aleksey
      Yeschenko for CASSANDRA-15805
  7. 26 May, 2020 3 commits
  8. 25 May, 2020 3 commits
  9. 21 May, 2020 1 commit
  10. 20 May, 2020 13 commits
  11. 19 May, 2020 1 commit
  12. 15 May, 2020 1 commit
  13. 14 May, 2020 1 commit
  14. 13 May, 2020 2 commits
    • Bereng's avatar
      Fix unguarded casts to NetworkTopologyStrategy · a209e78d
      Bereng authored
      patch by  Berenguer Blasi; reviewed by Benjamin Lerer for CASSANDRA-15791
    • Jon Meredith's avatar
      Update port when reconnecting to pre-4.0 SSL storage · 678ca3fc
      Jon Meredith authored
      On a failed outbound connection to a node with pending data, recheck
      the messaging version before reattempting the connection.
      Prior to this change, if the endpoint version was incorrectly set
      to 4.0 when the node was running 3.0 with an SSL storage port
      the connection would continuously try to reconnect on the wrong port.
      The patch also improves some of the log messages to include the
      actual port being connected to as well as the canonical endpoint for
      the node.
      Patch by Jon Meredith & Andy Tolbert; reviewed by Aleksey Yeschenko for
      Co-authored-by: default avatarJon Meredith <jmeredithco@gmail.com>
      Co-authored-by: default avatarAndy Tolbert <andy_tolbert@apple.com>