Bug #2035
Spaces permitted in filename and causes errors. Two or more spaces causes a 404.
Start date:
08/29/2017
Due date:
% Done:
100%
Description
While users probably should never use spaces (_ and - are more enjoyable), Core Splunk does not permit spaces in filenames. The lookup editor DOES allow spaces. While we are working to train users, our huge user-base and sometimes a high turnover causes ongoing issues with Files Not Found, etc. Splunk 6.6.2 required lookups with spaces to not only be quoted but must usually pipe into NOOP and disable auto optimization. Otherwise, Lookups are not found in search, either. Spaces in filenames also adds additional challenges when working from CLI.
History
#1
Updated by Luke Murphey about 7 years ago
- Target version set to 2.7.1
#2
Updated by Luke Murphey about 7 years ago
Good catch. This is to be fixed in the next release.
#3
Updated by Luke Murphey almost 7 years ago
- Status changed from New to Closed
#4
Updated by Luke Murphey almost 7 years ago
- % Done changed from 0 to 100