[jira] [Updated] (SOLR-17739) ConfigSet API should return error when forbidden file types are in the upload .zip file
[ https://issues.apache.org/jira/browse/SOLR-17739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SOLR-17739: -- Labels: newdev pull-request-available (was: newdev) > ConfigSet API should return error when forbidden file types are in the upload > .zip file > --- > > Key: SOLR-17739 > URL: https://issues.apache.org/jira/browse/SOLR-17739 > Project: Solr > Issue Type: Task > Components: configset-api >Reporter: Eric Pugh >Assignee: Eric Pugh >Priority: Minor > Labels: newdev, pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > The Forbidden Files configuration for ConfigSet > ([https://solr.apache.org/guide/solr/latest/configuration-guide/config-sets.html#forbidden-file-types)] > logs warnings that the files are being excluded, but an end user calling the > API wouldn't know that. > The API should instead raise an Exception, and NOT allow the ConfigSet to be > created. A warning in the logs of why the Exception was raised seems useful. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (SOLR-17739) ConfigSet API should return error when forbidden file types are in the upload .zip file
[ https://issues.apache.org/jira/browse/SOLR-17739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Pugh updated SOLR-17739: - Labels: newdev (was: ) > ConfigSet API should return error when forbidden file types are in the upload > .zip file > --- > > Key: SOLR-17739 > URL: https://issues.apache.org/jira/browse/SOLR-17739 > Project: Solr > Issue Type: Task > Components: configset-api >Reporter: Eric Pugh >Priority: Minor > Labels: newdev > > The Forbidden Files configuration for ConfigSet > ([https://solr.apache.org/guide/solr/latest/configuration-guide/config-sets.html#forbidden-file-types)] > logs warnings that the files are being excluded, but an end user calling the > API wouldn't know that. > The API should instead raise an Exception, and NOT allow the ConfigSet to be > created. A warning in the logs of why the Exception was raised seems useful. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
