lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Rutherglen (JIRA)" <>
Subject [jira] [Commented] (SOLR-2563) Allow generic pluggable file system implementations
Date Wed, 01 Jun 2011 01:21:47 GMT


Jason Rutherglen commented on SOLR-2563:

I don't think CoreContainer is completely removed from the local file system.  Checkout persist,
persistFile, etc.  Those should either be turned off, or should write to the underlying generic
file system.

It looks like libs are hard coded in CoreContainer?

if (libDir != null) {
  File f = FileUtils.resolvePath(new File(dir), libDir); "loading shared library: "+f.getAbsolutePath() );
  libLoader = SolrResourceLoader.createClassLoader(f, null);

CoreDescriptor.getDataDir() is ambiguous.

QueryElevationComponent is hardcoded:

// check if using ZooKeeper
ZkController zkController = core.getCoreDescriptor().getCoreContainer().getZkController();
if(zkController != null) {


SolrIndexWriter hardcodes writing the infoStream to the local file system.

The benchmark code is as well however that's somewhat less of a priority.

> Allow generic pluggable file system implementations
> ---------------------------------------------------
>                 Key: SOLR-2563
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: update
>    Affects Versions: 4.0
>            Reporter: Jason Rutherglen
> For things like configuration files, they can be loaded from places other than the local
filesystem, such as Zookeeper or HDFS.  In this issue I will abstract that functionality out.

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message