[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-275?pag... ] Sanne Grinovero commented on HSEARCH-275: ----------------------------------------- it appears that to enable this FSDirectory variant a system propery has to be set (just as for MMapDirectory) which will change the behaviour of existing FSDirectoryProvider. Should we parse this property from the configuration and set it, or just document the system property to be set? (in the latter case, no change is needed to the code, besides docs) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-275?pag... ] Emmanuel Bernard updated HSEARCH-275: ------------------------------------- Fix Version/s: (was: 3.1.1) 3.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-275?pag... ] Sanne Grinovero commented on HSEARCH-275: ----------------------------------------- I can confirm it's mostly a documentation patch, setting the JVM environment properties is enough to enable them. Needs some performance tests? My laptop-local little index couldn't tell me the difference performance-wise between the three types. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-275?pag... ] Emmanuel Bernard updated HSEARCH-275: ------------------------------------- Fix Version/s: (was: 3.2.0.Beta3) 3.3.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-275?pag... ] Sanne Grinovero commented on HSEARCH-275: ----------------------------------------- NIOFSDirectory is being selected automatically on systems in which it should perform better, still there are cases in which this implementations is buggy (see Lucene mailing list). It should be nice to be able to really control which impl to use, overriding the automatic decisions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-275?pag... ] Hardy Ferentschik commented on HSEARCH-275: ------------------------------------------- It is not a pure documentation issue (at least not anymore). As of Lucene 3.0 {{FSDirectory.open}} will never return a {{MMapDirectory}}. You will have to instantiate this directory yourself. As mentioned before {{NIOFSDiretory}} is already the default on non Windows systems: {code:title=FSDirectory.java|borderStyle=solid} ... if (Constants.WINDOWS) { return new SimpleFSDirectory(path, lockFactory); } else { return new NIOFSDirectory(path, lockFactory); } ... {code} where {{Constants.WINDOWS}} is the system property _os.name_. I guess one can override the _os.name_ property on the command line when starting the JVM to get an {{NIOFSDirectory}} on Windows. However, this is really a hack and maybe other parts of the app depend on the property as well. The best solution is to either provide additional options in our configuration to be able to control which subclass of {{FSDirectory}} to instantiate or to just add {{NIOFSDirectoryProvider}} and {{MMapDirectoryProvider}} implementations. I prefer the latter since we have already so many configuration options and having explicit provider classes seems clearer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-275?pag... ] Hardy Ferentschik commented on HSEARCH-275: ------------------------------------------- Introducing new {{DirectoryProvider}} classes raises of course the question what to do with {{FSMasterDirectoryProvider}} and {{FSSlaveDirectoryProvider}}. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira