[
https://issues.apache.org/jira/browse/NIFI-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18040907#comment-18040907
]
Daniel Stieglitz commented on NIFI-15261:
-----------------------------------------
[~exceptionfactory] I noticed ConfluentSchemaRegistry uses its own defined
MultipleURLValidator class to validate many specified urls. I was wondering
though is this class necessary if there is already the
org.apache.nifi.processor.util.StandardValidators.URI_LIST_VALIDATOR?
> Introduce URL/URI validation for properties representing a URL/URI
> ------------------------------------------------------------------
>
> Key: NIFI-15261
> URL: https://issues.apache.org/jira/browse/NIFI-15261
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Daniel Stieglitz
> Assignee: Daniel Stieglitz
> Priority: Minor
>
> Currently throughout the Apache NIFI code base there are property descriptors
> which represent URL/URI but do not use URL/URI validation. Depending on the
> property, they could use one of the following:
> * org.apache.nifi.processor.util.URLValidator
> * org.apache.nifi.processor.util.StandardValidators.URI_VALIDATOR
> * org.apache.nifi.processor.util.StandardValidators.URI_LIST_VALIDATOR.
> Some examples are detailed in the table below
> ||Class||Property||
> |RestLookupService|URL|
> |BitbucketFlowRegistryClient|BITBUCKET_API_URL|
> |AzureKeyVaultSecretsParameterProvider|KEY_VAULT_URI|
> |DeleteSQS|QUEUE_URL|
> |GetSQS|QUEUE_URL|
> |PutSQS|QUEUE_URL|
> |AbstractAzureLogAnalyticsReportingTask|LOG_ANALYTICS_URL_ENDPOINT_FORMAT|
> |AzureLogAnalyticsProvenanceReportingTask|INSTANCE_URL|
> |Neo4JCypherClientService|CONNECTION_URL|
> |StandardSnowflakeIngestManagerProviderService|HOST_URL|
> |AbstractMQTTProcessor|PROP_BROKER_URI|
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
