C0ntroller opened a new issue, #23363:
URL: https://github.com/apache/superset/issues/23363

   I currently try to query data from parquet files using Apache Drill and 
visualize them in Superset.
   Drill can access the original database and the parquet files in a S3-Store 
(which contain exports from the original DB)
   
   When using Drill CLI directly to query the original database (where the 
parquet files are exported from) or the parquet files, in both cases the 
resulting schema of the records is correct. 
   In the Database the column type is `NUMBER`, in Drill and parquet it's 
correctly converted to `DECIMAL`.
   
   When using the SQL Lab in Superset and running the same queries to Drill it 
**will** work when using the connection to the original database but when 
running a query against a parquet file it will incorrectly show the `DECIMAL` 
data type as `UserDefinedType`.
   
   #### How to reproduce the bug
   
   1. Prepare Apache Drill and a storage plugin to access parquet files in S3
   2. Prepare a parquet file with a `DECIMAL`-column (specifically 
`DECIMAL(38,0)`)
   3. Add Drill as data srouce to superset
   4. Go to SQL Lab in superset and show the schema for a "table" which is a 
parquet file
   5. See `UserDefinedType` as column type
   
   ### Expected results
   
   It should use `DECIMAL` as type
   
   ### Actual results
   
   `UserDefinedType` as column type
   
   ### Environment
   
   (please complete the following information):
   
   - MS Edge 110.0.1587.69
   - Using latest Superset docker container
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [x] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [x] I have reproduced the issue with at least the latest released version 
of superset.
   - [x] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to