[
https://issues.apache.org/jira/browse/AIRFLOW-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919039#comment-16919039
]
ASF subversion and git services commented on AIRFLOW-5139:
----------------------------------------------------------
Commit 3d50699f7b8965073c417973cd0b7db8cb001523 in airflow's branch
refs/heads/v1-10-test from Daniel Imberman
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=3d50699 ]
[AIRFLOW-5139] Allow custom ES configs (#5760)
* AIRFLOW-5139 Allow custom ES configs
While attempting to create a self-signed TLS connection between airflow
and ES, we discovered that airflow does now allow users to modify the
SSL state of the elasticsearchtaskhandler. This commit will allow users
to define ES settings in the airflow.cfg
(cherry picked from commit e5726c761d08bfddb6bb8acf3ecc381220eea140)
> ElasticSearchTaskRunner does not allow for custom ES configurations
> -------------------------------------------------------------------
>
> Key: AIRFLOW-5139
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5139
> Project: Apache Airflow
> Issue Type: Task
> Components: logging
> Affects Versions: 1.10.4
> Reporter: Daniel Imberman
> Assignee: Daniel Imberman
> Priority: Major
> Fix For: 1.10.5
>
>
> In [the ES
> task-handler|[https://github.com/apache/airflow/blob/master/airflow/utils/log/es_task_handler.py#L70]],
> the "ElasticSearch" object only takes in "host" as an argument. This means
> that users do not have the option to turn on ssl, assign certs, or perform
> any other of the necessary actions to match their ES environment.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
