Details

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

      Description

      Implement LevelDB Storage Engine MS2 as described here: https://kb.askmonty.org/en/leveldb-storage-engine-ms2/

        Gliffy Diagrams

          Attachments

            Issue Links

            1.
            LevelDB: Assertion `thd->is_error() || kill_errno' fails in ha_rows filesort Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 2 hours
             
            2.
            LevelDB: Server crashes in inline_mysql_mutex_lock on SELECT .. FOR UPDATE Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 3 hours
             
            3.
            LevelDB: Assertion `pack_info != __null' fails in LDBSE_KEYDEF::unpack_record Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 7 hours, 30 minutes
             
            4.
            LevelDB: Index-only scan by a field with utf8_bin collation returns garbage symbols Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 4 hours, 30 minutes
             
            5.
            LevelDB: Assertion `((keypart_map + 1) & keypart_map) == 0' fails in calculate_key_len Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 45 minutes
             
            6.
            LevelDB (and MyISAM): Wrong result (missing rows) with range access, prefix key on a char column Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 2 hours, 30 minutes
             
            7.
            LevelDB: Server crashes in LDBSE_KEYDEF::setup on dropping the primary key column Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 1 hour
             
            8.
            LevelDB: Server crashes in get_constant_key_infix on EXPLAIN with a select subquery Technical task Closed Sergei Petrunia  
             
            9.
            LevelDB: Valgrind "blocks still reachable" warnings on plugin initialization Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 1 hour
             
            10.
            LevelDB: Valgrind "blocks are definitely lost" warnings on creating a table Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 30 minutes
             
            11.
            LevelDB: Wrong result (missing rows) with ORDER BY DESC LIMIT after seemingly unrelated DDL/DML Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 2 hours, 30 minutes
             
            12.
            LevelDB: Valgrind "Use of uninitialised value" warnings on inserting value into varchar field Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 15 minutes
             
            13.
            LevelDB: Inconsistent results comparing a char field with an int field Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 15 minutes
             
            14. LevelDB (actually optimizer): Wrong result (duplicate rows) with FROM subquery, range access Technical task Stalled Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 3 hours
             
            15.
            LevelDB: Valgrind warnings 'Use of uninitialised value' on inserting into a varchar column Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 2 hours, 30 minutes
             
            16.
            LevelDB: Auto-increment value is not initialized correctly on non-empty tables Technical task Closed Sergei Petrunia  
             
            17.
            LevelDB: Statements suspected to be unsafe cannot be executed when binary log is ON Technical task Closed Sergei Petrunia  
             
            18.
            LevelDB: Valgrind warnings 'Invalid read' on delete in transactional context Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 2 days, 2 hours
             
            19.
            LevelDB: Wrong result of DELETE .. ORDER BY .. LIMIT: rows that should be deleted remain in the table Technical task Closed Sergei Petrunia

            100%

            Original Estimate - Not Specified Original Estimate - Not Specified
            Time Spent - 4 hours
             

              Activity

              Hide
              psergey Sergei Petrunia added a comment -

              An interesting problem: SQL layer calls ha_leveldb::index_flags() before the table is open. This means, index_flags() is called before we know datatypes of columns and can tell whether we support index_only for an index.

              Show
              psergey Sergei Petrunia added a comment - An interesting problem: SQL layer calls ha_leveldb::index_flags() before the table is open. This means, index_flags() is called before we know datatypes of columns and can tell whether we support index_only for an index.

                People

                • Assignee:
                  psergey Sergei Petrunia
                  Reporter:
                  psergey Sergei Petrunia
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 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 - 3 weeks, 3 hours, 15 minutes
                    3w 3h 15m