March 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-427) Make the hibernate-search-artifact directory a proper maven module

by Hardy Ferentschik (JIRA)

Make the hibernate-search-artifact directory a proper maven module ------------------------------------------------------------------ Key: HSEARCH-427 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-427 Project: Hibernate Search Issue Type: Task Components: build Affects Versions: 3.2.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.2.0.Beta3 This requires to restructure the build to be a proper multi module build. This is also a first step into allowing other search related maven modules -- 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

14 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-352) Introduce a programmatic mapping API

by Emmanuel Bernard (JIRA)

Introduce a programmatic mapping API ------------------------------------ Key: HSEARCH-352 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-352 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Fix For: 3.2.0 Initial commit. A lot of work to do still. The core idea is here but we need to: - complete the API describing the mapping - complete its binding to annotations - support merge between the programmatic API and annotations PS: if we go all the way for that, we won't have people nagging for XML support anymore :) -- 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

14 years, 3 months

1
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-346) Broken check for tuple id in DocumentBuilderIndexedEntity

by Hardy Ferentschik (JIRA)

Broken check for tuple id in DocumentBuilderIndexedEntity --------------------------------------------------------- Key: HSEARCH-346 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-346 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.0.GA Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.1.1 Bug got introduced during refactoring of DocumentBuilder. Since we are not testing against SQLServer or any other db where the generated SQL could be a problem the error passed through. the fix is quite easy, but it is harder to write a unit test. Maybe we should try to get a proper Hudson setup instead running against multiple databases. -- 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

14 years, 3 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-393) unit test of the NotSharedReaderPerfTest hangs on with some database

by strong liu (JIRA)

unit test of the NotSharedReaderPerfTest hangs on with some database -------------------------------------------------------------------- Key: HSEARCH-393 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-393 Project: Hibernate Search Issue Type: Bug Environment: oracle, postqresql and sybase Reporter: strong liu Assignee: Emmanuel Bernard the unit test of NotSharedReaderPerfTest hangs on some of databases like oracle / sybase / postqresql, and I tried change the "ulimit -n" to 100000, but still hangs on. as discussed in the email, This doesn't sound like it is the same issue as http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-189. -- 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

14 years, 3 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-318) Extend IndexWriterSetting to include a flag indicating whether it makes sense to have different settings for batch and index

by Hardy Ferentschik (JIRA)

Extend IndexWriterSetting to include a flag indicating whether it makes sense to have different settings for batch and index ---------------------------------------------------------------------------------------------------------------------------- Key: HSEARCH-318 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-318 Project: Hibernate Search Issue Type: Bug Components: engine Reporter: Hardy Ferentschik Fix For: 3.1.1 Not sure whether IndexWriterSetting is the right place to do this, but I think it could work. This issue relates to HSEARCH-298. -- 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

14 years, 3 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-476) Eventlisteners triggering mutiple times and on null primary keys

by Sanne Grinovero (JIRA)

Eventlisteners triggering mutiple times and on null primary keys ---------------------------------------------------------------- Key: HSEARCH-476 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-476 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.2.0.Beta1, 3.1.1.GA, 3.1.0.GA, 3.1.0.CR1 Reporter: Sanne Grinovero Assignee: Emmanuel Bernard Priority: Critical When persisting a non-trivial (but also not overly complex) entity graph many events are fired more than once, and several times while the primary key is not yet assigned. This causes much trouble in the workQueue: it might contain duplicate work, work about entities with null PK, and possibly even in a work order which results in an inconsistent index. -- 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

14 years, 3 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4940) Document immutable/read-only entity and immutable collection functionality

by Gail Badner (JIRA)

Document immutable/read-only entity and immutable collection functionality -------------------------------------------------------------------------- Key: HHH-4940 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4940 Project: Hibernate Core Issue Type: Improvement Components: documentation Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.0-CR-2 Document immutable/read-only entity and immutable collection functionality. -- 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

14 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5058) Account for annotations, entitymanager and envers in release bundle

by Steve Ebersole (JIRA)

Account for annotations, entitymanager and envers in release bundle ------------------------------------------------------------------- Key: HHH-5058 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5058 Project: Hibernate Core Issue Type: Task Components: build Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0.Next Currently the maven assemblies are not accounting for annotations, entitymanager and envers modules. -- 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

14 years, 3 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5047) Remove column coordinates from areaspecs

by Gail Badner (JIRA)

Remove column coordinates from areaspecs ---------------------------------------- Key: HHH-5047 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5047 Project: Hibernate Core Issue Type: Task Components: documentation Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.0.Next Remove column coordinates from areaspecs. -- 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

14 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5054) Add boolean Session.isDirty(Object)

by Joachim Durchholz (JIRA)

Add boolean Session.isDirty(Object) ----------------------------------- Key: HHH-5054 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5054 Project: Hibernate Core Issue Type: New Feature Components: core Affects Versions: 3.3.2 Environment: Irrelevant Reporter: Joachim Durchholz Priority: Critical I need to check whether a given object is dirty. Use case: The application loads a large collection of objects, modifies a few of them, then loads the collection with another set of criteria, modifies another small subset, and so on; finally, it flushes everything to the database. The code that loads the objects is separate from the code that does the modification. I.e. the load code does not have the knowledge about what objects got dirtied. Passing that knowledge from the modification code to the loader would create unwanted coupling, it would replicate knowledge that's already present in Hibernate, and it would be prone to bugs as the modification code would need to know what objects are attached to a session, and collect them in a Set<Object> of dirty objects. With the proposed change, the loader can iterate over the objects in the collection, check their Session.isDirty(Object) status, and use Session.evict(Object) to reclaim the space used for clean objects. (Note that this is really about keeping cache size under control. A way to keep the first-level cache size under control would serve my use case just as well, but such an API does not seem to exist, and I'd expect that to be far higher-hanging fruit than adding Session.evict(Object).) -- 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

14 years, 3 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2010