[jira] [Created] (DRILL-2200) Obscure error message from kvgen when the field does not exist in a parquet file

["Rahul Challapalli (JIRA)" <ji...@apache.org>]

Rahul Challapalli created DRILL-2200:
----------------------------------------

             Summary: Obscure error message from kvgen when the field does not exist in a parquet file
                 Key: DRILL-2200
                 URL: https://issues.apache.org/jira/browse/DRILL-2200
             Project: Apache Drill
          Issue Type: Bug
          Components: Functions - Drill
            Reporter: Rahul Challapalli
            Assignee: Mehant Baid
            Priority: Minor


git.commit.id.abbrev=3d863b5

Json Data Set :
{code}
{
  "id":1,
  "map": {
      "map1":{"col1":1, "col2":2}
  }
}
{code}

Equivalent Parquet File is attached.

The below response properly indicates the reason for failure
{code}
select kvgen(t.map.abcd) from dfs.flatten_operators.`data.json` t;
Query failed: RemoteRpcException: Failure while running fragment., kvgen function only supports Simple maps as input [ 9b441359-9f04-4199-8cca-cdc23aaab517 on qa-node191.qa.lab:31010 ]
[ 9b441359-9f04-4199-8cca-cdc23aaab517 on qa-node191.qa.lab:31010 ]
{code}

However the same query on an equivalent parquet file returns an obscure error message
{code}
select kvgen(t.map.abcd) from `data.parquet` t;
Query failed: RemoteRpcException: Failure while running fragment., Unable to find holder type for minorType: LATE [ 9697f4aa-1e8d-4221-8e7f-4d374ffbd916 on qa-node191.qa.lab:31010 ]
[ 9697f4aa-1e8d-4221-8e7f-4d374ffbd916 on qa-node191.qa.lab:31010 ]
{code}

However if we apply kvgen on a first level non-existent field we get back a proper error message even for a parquet file
{code}
select kvgen(t.map1) from `data.parquet` t;
Query failed: RemoteRpcException: Failure while running fragment., kvgen function only supports Simple maps as input [ 1d1c4ca3-ceda-4320-8ff8-fe08afe32090 on qa-node191.qa.lab:31010 ]
[ 1d1c4ca3-ceda-4320-8ff8-fe08afe32090 on qa-node191.qa.lab:31010 ]
{code}



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