[
https://issues.apache.org/jira/browse/NIFI-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802691#comment-15802691
]
ASF GitHub Bot commented on NIFI-957:
-------------------------------------
GitHub user pvillard31 opened a pull request:
https://github.com/apache/nifi/pull/1400
NIFI-957 Added the possibility to use DefaultSchedule annotation in r…
…eporting tasks
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [X] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [X] Is your initial contribution a single, squashed commit?
### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [X] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pvillard31/nifi NIFI-957
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1400.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1400
----
commit 5e86eaccfddf0fad412cde7b3bbc4318d42c1432
Author: Pierre Villard <[email protected]>
Date: 2017-01-05T22:14:37Z
NIFI-957 Added the possibility to use DefaultSchedule annotation in
reporting tasks
----
> Ability to provide default schedules per type
> ---------------------------------------------
>
> Key: NIFI-957
> URL: https://issues.apache.org/jira/browse/NIFI-957
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 0.3.0
> Reporter: Ali Bajwa
> Priority: Minor
>
> Per discussion with Bryan B as part of Ambari integration of Nifi: It would
> be nice for a reporting task, or any component really, to be able to provide
> a default schedule per type, instead of saying "all reporting tasks default
> to 5 mins".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
