You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Uwe Schindler (JIRA)" <ji...@apache.org> on 2019/01/28 12:43:00 UTC

[jira] [Commented] (SOLR-13173) Remove RAMDirectoryFactory after RAMDirectory removal?

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

Uwe Schindler commented on SOLR-13173:
--------------------------------------

I'd keep the class and deprecate it in 8.x. Let it just delegate to the new ByteBuffersDirectoryFactory. In master we can delay removal a bit.

> Remove RAMDirectoryFactory after RAMDirectory removal?
> ------------------------------------------------------
>
>                 Key: SOLR-13173
>                 URL: https://issues.apache.org/jira/browse/SOLR-13173
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Dawid Weiss
>            Assignee: Dawid Weiss
>            Priority: Minor
>
> This is a spinoff from LUCENE-8474. RAMDirectory is now officially gone from Lucene, replaced by a different memory-backed (byte buffers) implementation. Should we rename RAMDirectoryFactory in Solr or just change the implementation, leaving the name as is and looking at it as an implementation detail?
> RAMDirectoryFactory is used in a lot of places, so it a compatibility-breaking change (that doesn't add any value). I'm keen on leaving it as is, but looking for feedback from those more familiar with Solr deployments.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org