You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Rahul Challapalli (JIRA)" <ji...@apache.org> on 2015/12/03 03:09:10 UTC

[jira] [Created] (DRILL-4154) Metadata Caching : Upgrading cache to v2 from v1 corrupts the cache in some scenarios

Rahul Challapalli created DRILL-4154:
----------------------------------------

             Summary: Metadata Caching : Upgrading cache to v2 from v1 corrupts the cache in some scenarios
                 Key: DRILL-4154
                 URL: https://issues.apache.org/jira/browse/DRILL-4154
             Project: Apache Drill
          Issue Type: Bug
            Reporter: Rahul Challapalli
            Priority: Critical


git.commit.id.abbrev=46c47a2

I copied the data along with the cache file onto maprfs. Now I ran the upgrade tool (https://github.com/parthchandra/drill-upgrade). Now I ran the metadata_caching suite from the functional tests (concurrency 10) without the datagen phase. I see 3 test failures and when I looked at the cache file it seems to be containing wrong information for the varchar column. 

Sample from the cache :
{code}
      {
        "name" : [ "varchar_col" ]
      }, {
        "name" : [ "float_col" ],
        "mxValue" : 68797.22,
        "nulls" : 0
      }
{code}

Now I followed the same steps and instead of running the suites I executed the "REFRESH TABLE METADATA" command or any query on that folder,  the cache file seems to be created properly

I attached the data and cache files required. Let me know if you need anything



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)