Janusgraph how to deal with the global_offline misconfiguration


li...@...
 

when i tired to remove an index, I typed a wrong GLOBAL_OFFLINE setting in userConfig of the ManagementSystemwhich I mistake typed the "index.search.backend" with a directory string (/data/lucene) ......

when i try to open this janusgraph, it print out as below :

WARN  org.janusgraph.graphdb.configuration.GraphDatabaseConfiguration  - Local setting index.search.backend=lucene (Type: GLOBAL_OFFLINE) is overridden by globally managed value (/data/lucene).  Use the ManagementSystem interface instead of the local configuration to control this setting.

INFO  org.janusgraph.diskstorage.Backend  - Configuring index [search]

 I just wonder whether I could fix this problem without dropping table at the backend   ! 

many thx !


li...@...
 

I think i have fix this problem !
I just use a KCVS backend , and find out the source code of GraphDatabaseConfiguration ;
I tried and get the KCVSConfig use the code following :
PropertiesConfiguration configuration = new PropertiesConfiguration(GRAPH_PROPERTIES);

ReadConfiguration localConfig = new CommonsConfiguration(configuration);
BasicConfiguration localBasicConfiguration = new BasicConfiguration(ROOT_NS,localConfig, BasicConfiguration.Restriction.NONE);

KeyColumnValueStoreManager storeManager = Backend.getStorageManager(localBasicConfiguration);

KCVSConfiguration KCVSConfig =Backend.getStandaloneGlobalConfiguration(storeManager,localBasicConfiguration);


Just using the KCVSConfiguration to remove all the index configuration !




On Thursday, February 21, 2019 at 5:36:46 PM UTC+8, l...@... wrote:
when i tired to remove an index, I typed a wrong GLOBAL_OFFLINE setting in userConfig of the ManagementSystemwhich I mistake typed the "index.search.backend" with a directory string (/data/lucene) ......

when i try to open this janusgraph, it print out as below :

WARN  org.janusgraph.graphdb.configuration.GraphDatabaseConfiguration  - Local setting index.search.backend=lucene (Type: GLOBAL_OFFLINE) is overridden by globally managed value (/data/lucene).  Use the ManagementSystem interface instead of the local configuration to control this setting.

INFO  org.janusgraph.diskstorage.Backend  - Configuring index [search]

 I just wonder whether I could fix this problem without dropping table at the backend   ! 

many thx !


HadoopMarc <marc.d...@...>
 

Thanks for posting back, might be useful to someone someday.

Cheers,     Marc



Op vrijdag 22 februari 2019 09:06:20 UTC+1 schreef l...@...:

I think i have fix this problem !
I just use a KCVS backend , and find out the source code of GraphDatabaseConfiguration ;
I tried and get the KCVSConfig use the code following :
PropertiesConfiguration configuration = new PropertiesConfiguration(GRAPH_PROPERTIES);

ReadConfiguration localConfig = new CommonsConfiguration(configuration);
BasicConfiguration localBasicConfiguration = new BasicConfiguration(ROOT_NS,localConfig, BasicConfiguration.Restriction.NONE);

KeyColumnValueStoreManager storeManager = Backend.getStorageManager(localBasicConfiguration);

KCVSConfiguration KCVSConfig =Backend.getStandaloneGlobalConfiguration(storeManager,localBasicConfiguration);


Just using the KCVSConfiguration to remove all the index configuration !




On Thursday, February 21, 2019 at 5:36:46 PM UTC+8, l...@... wrote:
when i tired to remove an index, I typed a wrong GLOBAL_OFFLINE setting in userConfig of the ManagementSystemwhich I mistake typed the "index.search.backend" with a directory string (/data/lucene) ......

when i try to open this janusgraph, it print out as below :

WARN  org.janusgraph.graphdb.configuration.GraphDatabaseConfiguration  - Local setting index.search.backend=lucene (Type: GLOBAL_OFFLINE) is overridden by globally managed value (/data/lucene).  Use the ManagementSystem interface instead of the local configuration to control this setting.

INFO  org.janusgraph.diskstorage.Backend  - Configuring index [search]

 I just wonder whether I could fix this problem without dropping table at the backend   ! 

many thx !


Benoit George <benoit...@...>
 

Hi everyone,

Sorry to bring back this old topic. I also had this old problem and would want to report that this solution worked for me, thank you for posting it.

One little thing, since 0.3.x the access to a KCSVConfiguration instance changed and can now be accessed through 

KCVSConfigurationBuilder().buildStandaloneGlobalConfiguration(storeManager, localBasicConfiguration)

Cheers,

Benoit

On Friday, 22 February 2019 09:39:47 UTC+1, HadoopMarc wrote:
Thanks for posting back, might be useful to someone someday.

Cheers,     Marc



Op vrijdag 22 februari 2019 09:06:20 UTC+1 schreef l...@...:
I think i have fix this problem !
I just use a KCVS backend , and find out the source code of GraphDatabaseConfiguration ;
I tried and get the KCVSConfig use the code following :
PropertiesConfiguration configuration = new PropertiesConfiguration(GRAPH_PROPERTIES);

ReadConfiguration localConfig = new CommonsConfiguration(configuration);
BasicConfiguration localBasicConfiguration = new BasicConfiguration(ROOT_NS,localConfig, BasicConfiguration.Restriction.NONE);

KeyColumnValueStoreManager storeManager = Backend.getStorageManager(localBasicConfiguration);

KCVSConfiguration KCVSConfig =Backend.getStandaloneGlobalConfiguration(storeManager,localBasicConfiguration);


Just using the KCVSConfiguration to remove all the index configuration !




On Thursday, February 21, 2019 at 5:36:46 PM UTC+8, l...@... wrote:
when i tired to remove an index, I typed a wrong GLOBAL_OFFLINE setting in userConfig of the ManagementSystemwhich I mistake typed the "index.search.backend" with a directory string (/data/lucene) ......

when i try to open this janusgraph, it print out as below :

WARN  org.janusgraph.graphdb.configuration.GraphDatabaseConfiguration  - Local setting index.search.backend=lucene (Type: GLOBAL_OFFLINE) is overridden by globally managed value (/data/lucene).  Use the ManagementSystem interface instead of the local configuration to control this setting.

INFO  org.janusgraph.diskstorage.Backend  - Configuring index [search]

 I just wonder whether I could fix this problem without dropping table at the backend   ! 

many thx !