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

ASF subversion and git services commented on NIFI-10471:
--------------------------------------------------------

Commit 04c0df172329c8a5dfc865c4a8cab866f18e91a9 in nifi's branch 
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=04c0df1723 ]

NIFI-10471 Documented and applied standard deprecation logging

- Updated Admin Guide with section on Logging Configuration and Deprecation 
Logging
- Updated Developer Guide with section on Deprecating Components and Features
- Added Deprecation Logging when adding components marked with 
DeprecationNotice to the Flow Configuration
- Added Deprecation Logging on deprecated methods in standard Controller 
Service implementations
- Removed integration tests for deprecated PersistentProvenanceRepository
- Updated logging and added documentation on minor upgrade steps
- Updated logging for HDFSNarProvider and RocksDB Repository

This closes #6390
Signed-off-by: Paul Grey <[email protected]>


> Document and Apply Deprecation Logging
> --------------------------------------
>
>                 Key: NIFI-10471
>                 URL: https://issues.apache.org/jira/browse/NIFI-10471
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework, Extensions
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>             Fix For: 1.18.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The recent introduction of the {{DeprecationLogger}} and 
> {{nifi-deprecation.log}} configuration provide the basis for applying 
> deprecation logging to number of components and features.
> The User Guide and should be updated with additional details describing how 
> to interpret deprecation logs, how to disable deprecation logging. The 
> Developer Guide should include a new section outlining recommendations on 
> where and how to apply deprecation logging.
> Additional targets for deprecation logging include Processors and Controller 
> Services that are already marked as deprecated. Public methods implementing 
> deprecated interfaces should be evaluated for deprecation logging. Not every 
> method marked as deprecated should be logged, as some operations may produce 
> duplicative logs, and other methods should be addressed through code changes 
> instead of logged warnings.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to