You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/12/16 20:27:00 UTC
[jira] [Commented] (NIFI-6910) ReportLineageToAtlas Expose Atlas
Client Configurations
[ https://issues.apache.org/jira/browse/NIFI-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997616#comment-16997616 ]
ASF subversion and git services commented on NIFI-6910:
-------------------------------------------------------
Commit 67fca6832a528fc1bfe996f3d95a6ac250f6894c in nifi's branch refs/heads/master from Tamas Palfy
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=67fca68 ]
NIFI-6910 - ReportLineageToAtlas - Added processor properties for connect timeout and read timeout.
NIFI-6910 - ReportLineageToAtlas - Capitalized Atlas connect and read timeout property display names.
This closes #3936.
Signed-off-by: Peter Turcsanyi <tu...@apache.org>
> ReportLineageToAtlas Expose Atlas Client Configurations
> -------------------------------------------------------
>
> Key: NIFI-6910
> URL: https://issues.apache.org/jira/browse/NIFI-6910
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: David Mollitor
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In the {{ReportLineageToAtlas}} task expose the configurations for connections so that the user can change the timeout that the task may wait for a response from Atlas. I am currently barred from doing it manually because of some sort of NiFi validation check. I have to go in and modify the task's property file directly.
> {code:none}
> atlas.client.readTimeoutMSecs=60000
> atlas.client.connectTimeoutMSecs=60000
> {code}
> https://atlas.apache.org/2.0.0/Configuration.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)