You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2020/10/02 01:11:48 UTC

[GitHub] [incubator-superset] DRavikanth edited a comment on issue #11138: Presto Timestamp types are being identified as UNKNOWN datatype

DRavikanth edited a comment on issue #11138:
URL: https://github.com/apache/incubator-superset/issues/11138#issuecomment-702475356


   So, to whoever is running into this problem, the issue should have happened post-Presto 338 release where the timestamp is a parametric timestamp type (timestamp with different precision).  
   
   https://github.com/prestosql/presto/pull/4349
   
   This is what I did to resolve the problem. Updated my database connection and specific extra field with the following:
   ```
   {
     "metadata_params": {},
     "engine_params": {
       "connect_args": {
         "protocol": "https",
         "session_props": {
             "omit_datetime_type_precision": true
         }
       }
     },
     "metadata_cache_timeout": {},
     "schemas_allowed_for_csv_upload": []
   }
   ```
   
   Make a note of the  "omit_datetime_type_precision": true property. Refer: https://prestosql.io/docs/current/release/release-338.html
   
   This works fine now after I added the flag. I will leave it to Superset developers if they want to add a fix for it.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org