Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-794

query cache not work with all engine with columnstore

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.0.9
    • 1.0.10, 1.1.0
    • MariaDB Server
    • None
    • Docker container with Columnstore 1.09
    • 2017-14

    Description

      Query cache not work with columnstore regardless the engine.

      CREATE TABLE `qtest` (
      	`id` INT NULL
      )
      COLLATE='utf8_unicode_ci'
      ENGINE= InnoDB
      ;
       
       
      SET GLOBAL query_cache_size = 1000000;
       
      SET GLOBAL query_cache_type = 1;
       
       
      INSERT INTO `qtest` (`id`) VALUES ('1'),('1'),('2'),('3');
       
       
      select * from `qtest` where `id` = 2;
       
       
      
      

      No query in the query cache

      show global status like 'qca%';
       
      Variable_name;Value
      Qcache_free_blocks;1
      Qcache_free_memory;982184
      Qcache_hits;0
      Qcache_inserts;0
      Qcache_lowmem_prunes;0
      Qcache_not_cached;0
      Qcache_queries_in_cache;0
      Qcache_total_blocks;1
      

      But query cache is active.

      show global variables like 'q%';
       
      Variable_name;Value
      query_alloc_block_size;16384
      query_cache_limit;1048576
      query_cache_min_res_unit;4096
      query_cache_size;999424
      query_cache_strip_comments;OFF
      query_cache_type;ON
      query_cache_wlock_invalidate;OFF
      query_prealloc_size;24576
      

      Attachments

        Activity

          People

            dleeyh Daniel Lee (Inactive)
            Richard Richard Stracke
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.