October 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-104) Make @DocumentId optional and rely on @Id

by Emmanuel Bernard (JIRA)

Make @DocumentId optional and rely on @Id ----------------------------------------- Key: HSEARCH-104 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-104 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Priority: Minor -- 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

16 years, 10 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-293) AddLuceneWork is not being removed from the queue when DeleteLuceneWork is added for the same entity

by Daniel Claesén (JIRA)

AddLuceneWork is not being removed from the queue when DeleteLuceneWork is added for the same entity ---------------------------------------------------------------------------------------------------- Key: HSEARCH-293 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-293 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.0.Beta2 Reporter: Daniel Claesén There's an issue in the addWorkToQueue function in the DocumentBuilder class. If the work type is delete and there is an AddLuceneWork for the same entity in the queue it is added to the toDelete list. But when looping through the toDelete list the items are not removed from the LuceneWork queue, only from the toDelete list. -- 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

16 years, 10 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-250) In ReaderStrategies, ensure that the reader is current AND that the directory returned by the DirectoryProvider are the same

by Emmanuel Bernard (JIRA)

In ReaderStrategies, ensure that the reader is current AND that the directory returned by the DirectoryProvider are the same ---------------------------------------------------------------------------------------------------------------------------- Key: HSEARCH-250 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-250 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.1.0.Beta1 Reporter: Emmanuel Bernard Priority: Critical Fix For: 3.1.0.Beta2 When using the cluster mode, s slave has an active copy (current) and a passive copy of a Directory. In ReaderStrategy, we ensure the IndexReader is current but we do not ensure the Directory is the active one. -- 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

16 years, 10 months

3
10
0 / 0

[Hibernate-JIRA] Created: (ANN-527) reference a target entity (in a collection) by entity name

by Armin Haaf (JIRA)

reference a target entity (in a collection) by entity name ---------------------------------------------------------- Key: ANN-527 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-527 Project: Hibernate Annotations Type: New Feature Components: binder Reporter: Armin Haaf It is only possible to reference a targetEntity by class. @ManyToMany(targetEntity = TestImpl.class) List<Test> myList; This makes it impossible to exchange TestImpl.class implemention by another implemention by the mappings definition. It would be helpful to reference a targetEntity by name. @ManyToMany(targetEntityName = "Test") This would help a lot to implement moduls and frameworks. Another way to support this would be to search for a implementation of the collection elements (which are typically Interfaces) in the mapped entities -- 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

16 years, 10 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-291) improve documentation about thread safety requirements of Bridges.

by Sanne Grinovero (JIRA)

improve documentation about thread safety requirements of Bridges. ------------------------------------------------------------------ Key: HSEARCH-291 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-291 Project: Hibernate Search Issue Type: Task Components: documentation Reporter: Sanne Grinovero Priority: Minor Fix For: 3.1.0.CR1 -- 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

16 years, 10 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-274) Use Lucene's new readonly IndexReader

by Sanne Grinovero (JIRA)

Use Lucene's new readonly IndexReader ------------------------------------- Key: HSEARCH-274 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-274 Project: Hibernate Search Issue Type: Improvement Components: directory provider, documentation Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.1.0.CR1 # LUCENE-1329: Add optional readOnly boolean when opening an IndexReader. A readOnly reader is not allowed to make changes (deletions, norms) to the index; in exchanged, the isDeleted method, often a bottleneck when searching with many threads, is not synchronized. The default for readOnly is still false, but in 3.0 the default will become true. (Jason Rutherglen via Mike McCandless) In addition we should wrap the returned IndexReader to contain needed information to close it without having to search it back in synchronized hashmaps. -- 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

16 years, 10 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-266) Do not switch to the current directory in FSSlaveDirectoryProvider if no file has bee copied

by Emmanuel Bernard (JIRA)

Do not switch to the current directory in FSSlaveDirectoryProvider if no file has bee copied -------------------------------------------------------------------------------------------- Key: HSEARCH-266 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-266 Project: Hibernate Search Issue Type: Improvement Components: directory provider Affects Versions: 3.1.0.Beta1 Reporter: Emmanuel Bernard This will allow IndexReaders to be reused longer. -- 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

16 years, 10 months

2
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-23) Should Validator<T> be thread-safe?

by Emmanuel Bernard (JIRA)

Should Validator<T> be thread-safe? ----------------------------------- Key: BVAL-23 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-23 Project: Bean Validation Issue Type: Task Components: spec-general Reporter: Emmanuel Bernard Pros Can be reused easily across the board without thinking about it No real need to keep shared state Cons Contention issues? put constraint on the implementation -- 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

16 years, 10 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2546) fetch="select" doesn't work when there are no mapped columns in joined except <key

by Derar Bakr (JIRA)

fetch="select" doesn't work when there are no mapped columns in joined except <key ---------------------------------------------------------------------------------- Key: HHH-2546 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2546 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: Windows XP Pro Reporter: Derar Bakr java.lang.StringIndexOutOfBoundsException: String index out of range: -2 at java.lang.String.substring(String.java:1768) at java.lang.String.substring(String.java:1735) at org.hibernate.persister.entity.AbstractEntityPersister.renderSelect(AbstractEntityPersister.java:2899) at org.hibernate.persister.entity.SingleTableEntityPersister.generateSequentialSelect(SingleTableEntityPersister.java:647) at org.hibernate.persister.entity.SingleTableEntityPersister.postInstantiate(SingleTableEntityPersister.java:696) .... Everything is very simple. There is stupid code in SelectFragment class, method toFragmentString, line 94. String that is being created there, contains list of fields, like a "f1, f2, f3, ..., fn". ", " is being added in every iteration, without check for it is first iteration. And in class AbstractEntityPersister., method renderSelect, line 2899, where that method is called, this first ", " is deleted using substring(2). So no check for empty string. I suggest to add check :))) I just create dynamic mappings programmatically, so create empty join subclass mappings - and in created table there are no fields by default except foreing key. -- 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

16 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3568) In the hibernate mapping of versions entities, mark them as not updateable

by Adam Warski (JIRA)

In the hibernate mapping of versions entities, mark them as not updateable -------------------------------------------------------------------------- Key: HHH-3568 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3568 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski Assignee: Adam Warski Fix For: 3.4 -- 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

16 years, 11 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2008