[ 
https://issues.apache.org/jira/browse/SOLR-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488139#comment-17488139
 ] 

Jan Høydahl commented on SOLR-15950:
------------------------------------

The PR is ready. What will happen now is that if you try to use the cat 
function without creating the userfiles folder and adding some files there, 
you'll get the IllegalStateException which has been in that code path always, 
but has never been triggered before due to creation of the folder on startup.

Eric, I have never used "cat" feature, please give your thoughts on this. Does 
it even make sense to call the cat() function without first putting some files 
in userfiels? What would happen in 8.1 if used on an empty folder? Does that 
even make sense?

Since the userfiles behaviour is potentially breaking change I lean towards 9.0 
for this, but if we go the route of auto-creating userfiles on first use of 
cat() function, then it could go in 9.x since users won't need to change 
anything.

> Create SOLR_HOME/filestore lazily on first use
> ----------------------------------------------
>
>                 Key: SOLR-15950
>                 URL: https://issues.apache.org/jira/browse/SOLR-15950
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>            Priority: Major
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> Starting Solr in cloud mode with an empty SOLR_HOME (See SOLR_9575) creates 
> two empty folders in SOLR_HOME: {{filestore}} and {{{}userfiles{}}}.
> The filestore should be lazily initialized on first actual use, such as for 
> PackageManagerCLI to add some packages.
> The 'userfiles' I don't even know what is for.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to