Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.0.1
    • None
    • None

    Description

      Implement HBase storage for Cassandra instead.

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

      Attachments

        Issue Links

          Activity

            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.

            psergei 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.

            Added support for 'varint' type.

            psergei Sergei Petrunia added a comment - Added support for 'varint' type.

            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.
            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.

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

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

            pushed in 10.0-base

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

            People

              psergei Sergei Petrunia
              psergei Sergei Petrunia
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.