[
https://issues.apache.org/jira/browse/NIFI-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Witt updated NIFI-645:
-----------------------------
Description:
The content viewer is now available in the build and it would be nice if it was
preconfigured to be used by default. If the user doesn't want it available
they can remove it (seems unlikely) or if they have an alternative they can
point to it.
The same is true of content archive. We should keep content around for a few
hours by default (or some number of some time unit) and for X% of space.
The core thing we're seeing is that users are wanting to use these features but
not realizing they're not on by default. At this point in their maturity they
should be on by default and only shut off when a user wants that.
Also have the component status repository update be every 30 seconds by default
and keep for 24 hours
was:
The content viewer is now available in the build and it would be nice if it was
preconfigured to be used by default. If the user doesn't want it available
they can remove it (seems unlikely) or if they have an alternative they can
point to it.
The same is true of content archive. We should keep content around for a few
hours by default (or some number of some time unit) and for X% of space.
The core thing we're seeing is that users are wanting to use these features but
not realizing they're not on by default. At this point in their maturity they
should be on by default and only shut off when a user wants that.
> Set content archive and content viewer on by default
> ----------------------------------------------------
>
> Key: NIFI-645
> URL: https://issues.apache.org/jira/browse/NIFI-645
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration
> Reporter: Joseph Witt
> Assignee: Joseph Witt
> Fix For: 0.2.0
>
>
> The content viewer is now available in the build and it would be nice if it
> was preconfigured to be used by default. If the user doesn't want it
> available they can remove it (seems unlikely) or if they have an alternative
> they can point to it.
> The same is true of content archive. We should keep content around for a few
> hours by default (or some number of some time unit) and for X% of space.
> The core thing we're seeing is that users are wanting to use these features
> but not realizing they're not on by default. At this point in their maturity
> they should be on by default and only shut off when a user wants that.
> Also have the component status repository update be every 30 seconds by
> default and keep for 24 hours
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
