Jimmy-Newtron opened a new issue #13866: URL: https://github.com/apache/superset/issues/13866
I want to create a chart **Big Number with Trendline** that must use a custom datetime column (different from @timestamp) field from an opendistro dataset    Using the **timestamp** field it gets the error while with the **firstEventEpochSession** it works correctly  ### Expected results Chart is able to render the data ### Actual results & screenshots  #### How to reproduce the bug 1. Create a dataset from an opendistro index (with a custom datetime field) 2. Create a chart of type **Big Number with Trendline** 3. Select the custom datetime field into the time section 4. Run the query & see error ### Environment - helm chart (latest) - superset version: `superset version` ``` root@superset-67bcb48445-hgvw9:/app# superset version Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py] logging was configured successfully INFO:superset.utils.logging_configurator:logging was configured successfully -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Superset 0.999.0dev -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ``` - python version: `python --version` ``` root@superset-67bcb48445-hgvw9:/app# python Python 3.7.9 (default, Feb 9 2021, 08:33:04) [GCC 8.3.0] on linux ``` ### 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. ### Superset source code https://github.com/apache/superset/blob/9fa52b50edaa2e42b7d064139ddb41d329aa1344/superset/db_engine_specs/base.py#L502 https://github.com/apache/superset/blob/9fa52b50edaa2e42b7d064139ddb41d329aa1344/superset/db_engine_specs/elasticsearch.py#L67 -- 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: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
