[Hibernate-JIRA] Created: (HSEARCH-842) File Leaks - FSMasterDirectoryProvider & Mass indexing
by Johnny B (JIRA)
File Leaks - FSMasterDirectoryProvider & Mass indexing
------------------------------------------------------
Key: HSEARCH-842
URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-842
Project: Hibernate Search
Issue Type: Bug
Components: directory provider
Affects Versions: 3.3.0.Final
Environment: Windows/linux Hibernate 3.6.5 , lucene 3.0.3
Reporter: Johnny B
Attachments: fileleaks.zip
Hi Guys,
As already discussed in forum
https://forum.hibernate.org/viewtopic.php?f=9&t=1011938&p=2447638
Basically i notice that the FSMasterDirectoryProvider never releases its file handles even after a full batch index has taken place.
Example
Test case 1
1. Fresh clean index
2. Batch index takes place, all file handles are closed at the end, nothing is open
3. You can batch index as many times as you want but at the end of each batch index no file handles are open.
Test case 2
1. Index exists already, start up application and FSMasterDirectoryProvider opens file handles to existing index
2. Batch index triggered for that index. At the end of the batch index, i notice that the same file file handles are still open as when the app started. This should not be because we have purged the index and carried out a full batch index for it. The index size has now doubled!!!
3. You can carry out as many batch indexes as you want but the very original file handles at start up are always kept open.
Test case is attached and forum description gives better insight as to how i carried out the tests
Cheers,
JB
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[Hibernate-JIRA] Created: (HHH-5775) Support session filters in DML statements
by Jason Clawson (JIRA)
Support session filters in DML statements
-----------------------------------------
Key: HHH-5775
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5775
Project: Hibernate Core
Issue Type: Improvement
Components: core, query-hql
Reporter: Jason Clawson
We are using filters to support multi-tenency, an approach alluded to in this recent blog post: http://in.relation.to/Bloggers/MultitenancyInHibernate. It works create for HQL selects but doesn't work for Updates / Deletes. Looking through the source code, this seems to have been a conscious choice as some comments indicate. If filters are meant to be used for multitenency, this seems to be the wrong choice. I would like to see session filters affect updates and deletes. This seems very logical because if I run the select: SELECT * FROM User which is affected by a filter and returns 2 users, and then execute DELETE FROM User which deletes all the users in the system--- thats not what I would expect to happen.
I believe this will require modifications to HqlSqlWalker and the ANTLR script sql-gen.g. I am looking into what other modifications are necessary, but I would appreciate it if the Hibernate folks could take a look since they would be most familiar with the code and the decisions behind it.
Thanks!
--
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
12 years, 10 months