[jira] [Commented] (AIRFLOW-3370) Enhance current ES handler with stdout capability and more output options

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811106#comment-16811106 ] 

ASF GitHub Bot commented on AIRFLOW-3370:
-----------------------------------------

andriisoldatenko commented on pull request #5048: [AIRFLOW-3370] Add stdout output options to Elasticsearch task log handler
URL: https://github.com/apache/airflow/pull/5048
 
 
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-XXX
     - In case you are fixing a typo in the documentation you can prepend your commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
     - In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)).
     - In case you are adding a dependency, check if the license complies with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI changes:
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use it.
     - All the public functions and the classes in the PR contain docstrings that explain what it does
     - If you implement backwards incompatible changes, please leave a note in the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so we can assign it to a appropriate release
   
   ### Code Quality
   
   - [ ] Passes `flake8`
   
 
----------------------------------------------------------------
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


> Enhance current ES handler with stdout capability and more output options
> -------------------------------------------------------------------------
>
>                 Key: AIRFLOW-3370
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3370
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: celery, logging, worker
>    Affects Versions: 1.10.0
>            Reporter: Robert Hwang
>            Assignee: Andrii Soldatenko
>            Priority: Major
>
> Currently, the ES handler in 1.10 can only search from ES, and it's not. Two possible enhancements are to allow the handler a "write to standard out" functionality, and make log messages more remote-storage friendly, with an optional JSON-formatted message, and the regular pretty-print log format as the default



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)