September 2008 - hibernate-issues

[Hibernate-JIRA] Created: (HSEARCH-75) Use FieldSelector to filter returned Fields

by Emmanuel Bernard (JIRA)

Use FieldSelector to filter returned Fields ------------------------------------------- Key: HSEARCH-75 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-75 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Emmanuel Bernard Priority: Minor Might be useful for projections, but is most likely unnecessary. -- 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

17 years, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-175) USe domain specific annotations to plug custom bridges

by Emmanuel Bernard (JIRA)

USe domain specific annotations to plug custom bridges ------------------------------------------------------ Key: HSEARCH-175 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-175 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Fix For: 3.1.0 Use annotated annotations to declare bridges. Ie offer the same flexibility used by HSearch in @DateBridge -- 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

17 years, 6 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-219) Manual indexing strategy not implemented

by Fol De Rol (JIRA)

Manual indexing strategy not implemented ---------------------------------------- Key: HSEARCH-219 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-219 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.0.1.GA Reporter: Fol De Rol Priority: Blocker It looks impossible to implement fully manual strategy of indexing because of mandating event listeners to be registered. See org.hibernate.search.util.ContextHelper.java:25: //FIXME this sucks since we mandante the event listener use This causes a side effect to my application that stores an indication that the certain object is indexed in a child collection. So, when I complete manual indexing of an object, I add an element to this collection (actually, the cluster node identifier). This causes the Hibernate Search event listener to be triggered because the dependent collection has been modified which in its turn adds one more indexing job. Finally, I get an endless recursion. -- 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

17 years, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-238) DirectoryProviderFactory configuration problem

by Rafal Glowacz (JIRA)

DirectoryProviderFactory configuration problem ---------------------------------------------- Key: HSEARCH-238 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-238 Project: Hibernate Search Issue Type: Bug Reporter: Rafal Glowacz Because IdHashShardingStrategy fails after 1.7m ID is reached I decided to use my own version of strategy. I set up property common.hibernate.search.blogentry.sharding_strategy = com. ... .IdShardingStrategy and didn't work for me. As I checked problem exist in DirectoryProviderFactory and the way how properties are created ( new Properties( defaultProperties ) ). This constructor and the way how default properties are stored in this Object this both together doesn't work well. Problem exist: //define sharding strategy IndexShardingStrategy shardingStrategy; Properties shardingProperties = new Properties(); for (Map.Entry entry : indexProps[0].entrySet()) { if ( ( (String) entry.getKey() ).startsWith( SHARDING_STRATEGY ) ) { shardingProperties.put( entry.getKey(), entry.getValue() ); } } String shardingStrategyName = shardingProperties.getProperty( SHARDING_STRATEGY ); if ( shardingStrategyName == null) { if ( indexProps.length == 1 ) { shardingStrategy = new NotShardedStrategy(); } else { shardingStrategy = new IdHashShardingStrategy(); } } else { in this loop "for (Map.Entry entry : indexProps[0].entrySet()) {" this set is just empty so custom properties for sharding have been ignored. Workaround: Instead using new Properties(defaultProps) I'm using method: private static Properties createProperties(Properties indexSpecificDefaultProps) { Properties properties = new Properties(); properties.putAll(indexSpecificDefaultProps); return properties; } -- 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

17 years, 6 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-176) explicitly setting cfg property to lucene default

by Sanne Grinovero (JIRA)

explicitly setting cfg property to lucene default ------------------------------------------------- Key: HSEARCH-176 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-176 Project: Hibernate Search Issue Type: Improvement Components: directory provider, documentation Reporter: Sanne Grinovero Priority: Trivial As highlighted by previous patch for http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-153 , some configuration settings may be inherited, so it becomes difficult to explicitly set "default" settings on some settings as some values are "Integer.MAX_VALUE" or "null" but the cfg parser only accepts int values. Also if the users wants to explicitly set lucene defaults it needs to study the current lucene source code. I'm going to provide a patch to support besides current int values also "default" and "null" Strings, to explicitly configure H.Search to: "default" -> don't mess with the value "null" -> explicitly null the value Also someone may find it useful to represent "MAX_VALUE", what do you think about that, or other configurations that should be recognized? -- 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

17 years, 6 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-239) Search default properties are ignored when at least one shard property exist

by Rafal Glowacz (JIRA)

Search default properties are ignored when at least one shard property exist ---------------------------------------------------------------------------- Key: HSEARCH-239 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-239 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.0.0.GA Reporter: Rafal Glowacz I'm trying to use shared strategy for search. So my basic setup was: common.hibernate.search.default.indexBase = /lucene/index common.hibernate.search.default.optimizer.operation_limit.max = 1000 common.hibernate.search.default.optimizer.transaction_limit.max = 1000 common.hibernate.search.default.directory_provider = org.hibernate.search.store.FSDirectoryProvider common.hibernate.search.default.sharding_strategy = com.newbay.search.sharding.strategy.IdShardingStrategy common.hibernate.search.blogentry.sharding_strategy.nbr_of_shards = 5 But this won't work for me because when sharding configuration properties exist then those default ones are completely ignored - I can't understand that. To change this I changed ".default." to ".blogentry." and then I found the bug that the number of properties decides how many shards I want for current index. (nbrOfShards = nbrOfShards >= indexSpecificDefaultProps.size() ? nbrOfShards : indexSpecificDefaultProps.size();) So in this case I can't do anything. I'm looking for such config: common.hibernate.search.default.indexBase = /lucene/index common.hibernate.search.default.optimizer.operation_limit.max = 1000 common.hibernate.search.default.optimizer.transaction_limit.max = 1000 common.hibernate.search.default.directory_provider = org.hibernate.search.store.FSDirectoryProvider common.hibernate.search.default.sharding_strategy = com.newbay.search.sharding.strategy.IdShardingStrategy common.hibernate.search.website.sharding_strategy.nbr_of_shards = 2 common.hibernate.search.website.indexBase = /lucene/website common.hibernate.search.blogentry.sharding_strategy.nbr_of_shards = 5 common.hibernate.search.blogentry.indexBase = /lucene/blogentry But it doesn't work for now. My solution for this is to build properties in order: default, indexProps, shardProps //sharded nbrOfShards = nbrOfShards >= indexSpecificDefaultProps.size() ? nbrOfShards : indexSpecificDefaultProps.size(); ensureListSize(indexSpecificProps, nbrOfShards); for (int index = 0; index < nbrOfShards; index++) { Properties properties = new Properties(); properties.putAll(defaultProperties); properties.putAll(indexSpecificDefaultProps); if (indexSpecificProps.get(index) != null) { properties.putAll(indexSpecificProps.get(index)); } indexSpecificProps.set(index, properties); } return indexSpecificProps.toArray(new Properties[indexSpecificProps.size()]); -- 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

17 years, 6 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-263) Wrong analyzers used in IndexWriter

by Sanne Grinovero (JIRA)

Wrong analyzers used in IndexWriter ----------------------------------- Key: HSEARCH-263 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-263 Project: Hibernate Search Issue Type: Bug Components: analyzer Affects Versions: 3.1.0.Beta1 Reporter: Sanne Grinovero Priority: Critical when an IndexWriter is first opened during a transaction commit it is assigned the analyzer connected to the first entity written, if during the same transaction other entities are saved to the same index it will reuse the first one ( instead of the entity specified one). I have a testcase showing the problem ready for commit but need your opinion about how to solve it. I think the problem is that we register a ScopedAnalyzer for each DocumentBuilder, but there should be one per DirectoryProvider? In this case we should check at startup that no entities sharing an index define conflicting Analyzer rules. Another solution would be to let complete flexibility during analyzer definition, but reopen the IndexWriter when the entityType is different from the last one indexed. -- 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

17 years, 6 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-271) wrong Similarity used when sharing index among entities

by Sanne Grinovero (JIRA)

wrong Similarity used when sharing index among entities ------------------------------------------------------- Key: HSEARCH-271 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-271 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.0.Beta1 Reporter: Sanne Grinovero When the same IndexWriter is used during a transaction commit for two or more entities (sharing the same index) but having different Similarities, the Similarity used is the one from the first entity to be indexed. No warning is logged and it's hard to recognize without being a paranoid Similarity expert... If the two Entities share an object hierarchy, then Search correctly throws an exception during startup. Should we throw an exception also on index sharing or solve it to support different Similarities even on different obejcts being part of same tree? (to be consistent) -- 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

17 years, 6 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3343) Postgres Plus Dialect

by Jim Mlodgenski (JIRA)

Postgres Plus Dialect --------------------- Key: HHH-3343 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3343 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: Jim Mlodgenski Attachments: postgresplus.patch Postgres Plus Advanced Server is an extension to PostgreSQL with added Oracle compatibility. Attached is a patch that implements a Postgres Plus Dialect with the Oracle compatible functions supported in Advanced Server matching the existing registered functions in the Oracle Dialect. -- 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

17 years, 6 months

2
6
0 / 0

[Hibernate-JIRA] Created: (EJB-383) pom at both ibiblio and jboss maven repo declares package type as pom instead of jar

by Kevin Brockhoff (JIRA)

pom at both ibiblio and jboss maven repo declares package type as pom instead of jar ------------------------------------------------------------------------------------ Key: EJB-383 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-383 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.CR2, 3.4.0.CR1, 3.3.2.GA Reporter: Kevin Brockhoff deployed pom to central repositories declares packaging as pom instead of jar. Ivy dutifully follows the directions and downloads the pom and not the jar. ejb3-persistence has the same issue. -- 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

17 years, 6 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2008