Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: 10.0.1
    • Component/s: None
    • Labels:
      None

      Description

      Implement HBase storage for Cassandra instead.

      See http://kb.askmonty.org/en/cassandra-storage-engine/ for user-level description

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

              Hide
              psergey Sergei Petrunia added a comment -

              Thanks for the note. I guess the protocol has been pushed fairly recently? IIRC when I checked for it, there was only a Jira entry.
              I think, I won't be able to implement the protocol before my nearest delivery, we'll consider implementing it for the milestone after that.

              Show
              psergey Sergei Petrunia added a comment - Thanks for the note. I guess the protocol has been pushed fairly recently? IIRC when I checked for it, there was only a Jira entry. I think, I won't be able to implement the protocol before my nearest delivery, we'll consider implementing it for the milestone after that.
              Hide
              psergey Sergei Petrunia added a comment -

              Added support for 'varint' type.

              Show
              psergey Sergei Petrunia added a comment - Added support for 'varint' type.
              Hide
              jbellis Jonathan Ellis added a comment -

              Saw that you announced a preview release. Congrats!

              Wanted to make sure you guys were aware of a couple changes we're making:

              1. Cassandra is moving away from "dynamic columns" per se. Although supporting that is nice for legacy purposes, in CQL3 (opt-in in C* 1.1, default in C* 1.2, although fallback to CQL2 is still available) columns must be defined before use.
              2. Cassandra is adding collections (maps, lists, and sets) to CQL3 in 1.2. (This is available in our recent beta1 release.) Not sure how you'd want to expose that, tbh... I don't think dynamic columns is necessarily a good fit for Maps for instance since you can have key conflicts.
              Show
              jbellis Jonathan Ellis added a comment - Saw that you announced a preview release. Congrats! Wanted to make sure you guys were aware of a couple changes we're making: Cassandra is moving away from "dynamic columns" per se. Although supporting that is nice for legacy purposes, in CQL3 (opt-in in C* 1.1, default in C* 1.2, although fallback to CQL2 is still available) columns must be defined before use. Cassandra is adding collections (maps, lists, and sets) to CQL3 in 1.2. (This is available in our recent beta1 release.) Not sure how you'd want to expose that, tbh... I don't think dynamic columns is necessarily a good fit for Maps for instance since you can have key conflicts.
              Hide
              sanja Oleksandr Byelkin added a comment -

              JFYI Our dynamic columns collect not only Cassandra dynamic columns but all not mentioned in MariaDB descriptions columns.

              Show
              sanja Oleksandr Byelkin added a comment - JFYI Our dynamic columns collect not only Cassandra dynamic columns but all not mentioned in MariaDB descriptions columns.
              Hide
              serg Sergei Golubchik added a comment -

              pushed in 10.0-base

              Show
              serg Sergei Golubchik added a comment - pushed in 10.0-base

                People

                • Assignee:
                  psergey Sergei Petrunia
                  Reporter:
                  psergey Sergei Petrunia
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  8 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 2 weeks, 1 day, 7 hours, 45 minutes
                    2w 1d 7h 45m