josh-fell commented on issue #21348:
URL: https://github.com/apache/airflow/issues/21348#issuecomment-1031800294


   @potiuk Part of #21237 was adding 3 new lexers for the SQL rendering in the 
UI. For the providers that use the new lexers, the rendering won't be as 
readable as it could be because the configured lexer doesn't exist yet (i.e. 
the rendering becomes a Python type rendering). Do we want to wait on releasing 
#21237 at all until those lexers are available or not push the SQL 
`template_fields_renderers` change for those particular providers yet?
   
   For example, there is a new `postgresql` lexer and added to the 
`RedshiftSqlOperator` (among others). Without the new lexer in core Airflow, 
the rendering of the SQL statement looks like this:
   
![image](https://user-images.githubusercontent.com/48934154/152851870-c27d8adf-13e2-42fe-b6c2-45bce89f9818.png)
   
   Instead of:
   
![image](https://user-images.githubusercontent.com/48934154/152851919-0d56bbbf-2ff6-4cb8-86e8-be865deb2815.png)
   
   


-- 
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: commits-unsubscr...@airflow.apache.org

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


Reply via email to