[
https://issues.apache.org/jira/browse/NIFI-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-4003:
-----------------------------
Description: When we attempt to retrieve the latest schema version
information for a schema with the HortonworksSchemaRegistry controller service,
it caches the information for 1 minute. We should expose that cache duration as
a property so that a tradeoff can be made by the user about how long to go
without retrieving a new value vs. how long to support a local version when
unable to communicate with the remote server. (was: When we attempt to
retrieve the latest schema version information for a schema with the
HortonworksSchemaRegistry controller service, it caches the information for 1
minute. After that minute is up, though, if we are unable to communicate with
the HortonworksSchemaRegistry, an Exception is thrown. If we already have a
value cached, though, we should use that instead of throwing a
SchemaNotFoundException)
> Controller Service for HortonworksSchemaRegistry should expose Cache Duration
> as a property
> -------------------------------------------------------------------------------------------
>
> Key: NIFI-4003
> URL: https://issues.apache.org/jira/browse/NIFI-4003
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
>
> When we attempt to retrieve the latest schema version information for a
> schema with the HortonworksSchemaRegistry controller service, it caches the
> information for 1 minute. We should expose that cache duration as a property
> so that a tradeoff can be made by the user about how long to go without
> retrieving a new value vs. how long to support a local version when unable to
> communicate with the remote server.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
