October 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4450) MapKey with key as entity not working

by shay (JIRA)

MapKey with key as entity not working -------------------------------------- Key: HHH-4450 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4450 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: hibernate annotations 3.4.0 , Hibernate-core 3.3.2 , Postgres 1.8.4 Reporter: shay Priority: Blocker Attachments: testbug.zip when using an entity as key , map is inaccessible(NullPointerException for items) . Its seems that when HashCode is called on the Key , the properties in key have not been populated, which prevents the map from loading properly Test case attached Thank you for your help Shay Matasaro -- 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, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5235) MultipleHiLoPerTableGenerator infers catalogs and schemas where none should be inferred

by Laird Nelson (JIRA)

MultipleHiLoPerTableGenerator infers catalogs and schemas where none should be inferred --------------------------------------------------------------------------------------- Key: HHH-5235 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5235 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2 Environment: Hibernate 3.5.2-Final, H2 database version 1.2.134 Reporter: Laird Nelson I have a @TableGenerator annotation and an associated @GeneratedValue like this: @Entity(name = "PostalAddress") @TableGenerator( name = "PostalAddressEntityIDGenerator", table = "JPAGenerators", pkColumnName = "generatorName", pkColumnValue = "PostalAddressEntityIDGenerator", valueColumnName = "generatorValue", allocationSize = 1 ) public class PostalAddressEntity { @GeneratedValue(strategy = GenerationType.TABLE, generator = "PostalAddressEntityIDGenerator") @Id private long id; /* etc. */ } At runtime, the following SQL shows up: select generatorValue from JPAGenerators.JPAGenerators.JPAGenerators where generatorName = 'PostalAddressEntityIDGenerator' for update Note the table name repeated three times as though it is both the catalog, the schema and the table name. It seems that the MultipleHiLoPerTableGenerator, when asked to build its SQL strings for various operations, is told that the schema, the catalog and the table name are all the same. I was expecting that the catalog would default to "", per the TableGenerator documentation, and that the schema would default to whatever was present in orm.xml's persistence-unit-defaults element. I can work around this by explicitly spelling out the schema name in my @TableGenerator annotation, but I don't want to put it there (can't, actually). I can also work around this in a JPA-compliant manner by defining my table generator in my orm.xml file, but I don't want to do that either. -- 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, 9 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-472) Runtime creation of new shards

by Dobes Vandermeer (JIRA)

Runtime creation of new shards ------------------------------ Key: HSEARCH-472 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-472 Project: Hibernate Search Issue Type: New Feature Components: query Affects Versions: 3.2.0.Beta1 Reporter: Dobes Vandermeer Priority: Minor Hibernate Search's shard support has added the ability to select a shard based on a parameter of the query; however, you must use a fixed number of shards. In order to best support our use case originally reported in http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-470 it would be necessary to add support for dynamically added shards at runtime. Also related: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-251 and http://www.opensubscriber.com/message/hibernate-dev@lists.jboss.org/97703... -- 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

3
28
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-521) Improve performance MassIndexer through Eager fetching

by Marc Schipperheyn (JIRA)

Improve performance MassIndexer through Eager fetching ------------------------------------------------------ Key: HSEARCH-521 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-521 Project: Hibernate Search Issue Type: Improvement Components: engine Affects Versions: 3.2.0.CR1 Reporter: Marc Schipperheyn Priority: Minor The MassIndexer fetches all of a certain entity from the database. It then proceeds to index it and the tree of IndexedEmbedded objects is traversed. In doing so, a lot of additional queries get executed. These queries are not really necessary, since we know beforehand that the data is needed for the indexing operation. So it would make sense to eagerly fetch all associations that are marked as indexEmbedded. This way MassIndexer would significantly speed up. -- 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

3
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-601) Allow MassIndexer to recover gracefully when individual objects won't index

by Ben Dotte (JIRA)

Allow MassIndexer to recover gracefully when individual objects won't index --------------------------------------------------------------------------- Key: HSEARCH-601 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-601 Project: Hibernate Search Issue Type: Improvement Components: massindexer Affects Versions: 3.2.0.Final Environment: Hibernate 3.5.3, SQL Server 2005 Reporter: Ben Dotte Some of our sites take hours to index, so it is critical that initial indexing complete even if some of the individual entities fail to index properly. Right now, it appears that the MassIndexer dies if any individual entity throws an exception during indexing, and does not complete indexing for that type. I have a workaround for now by overriding EntityConsumerLuceneworkProducer with my own index() method that catches and logs exceptions from docBuilder.createAddWork(): private void index( Object entity, Session session ) throws InterruptedException { Serializable id = session.getIdentifier( entity ); Class clazz = Hibernate.getClass( entity ); DocumentBuilderIndexedEntity docBuilder = documentBuilders.get( clazz ); TwoWayFieldBridge idBridge = docBuilder.getIdBridge(); String idInString = idBridge.objectToString( id ); //depending on the complexity of the object graph going to be indexed it's possible //that we hit the database several times during work construction. try { AddLuceneWork addWork = docBuilder.createAddWork( clazz, entity, id, idInString, true ); backend.enqueueAsyncWork( addWork ); } catch (Exception e) { log.error("Error indexing " + clazz + " id " + id, e); } } This has the added benefit that the object type and id that errored is logged, where that can be tough to track down otherwise. That may not be the best solution in general since it could hide exceptions from Hibernate Search itself. -- 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

3
16
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-349) Allow custom Loader in FullTextQueryImpl

by Julien Kronegg (JIRA)

Allow custom Loader in FullTextQueryImpl ---------------------------------------- Key: HSEARCH-349 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-349 Project: Hibernate Search Issue Type: New Feature Components: query Affects Versions: 3.1.0.GA Environment: Hibernate 3.3.1.GA, DB2 Reporter: Julien Kronegg Priority: Minor When doing an native SQL query containing join and other complicated stuff, one can get a List<MyObject> using the following code: List<MyObject> list = entityManager.createNativeQuery("SELECT ...", MyObject.class).getResultList(); The MyObject class is an JPA Entity, but is not connected to a database table: the MyObject instance is reconstructed automatically by mapping the ResultSet column names and the MyObject field names. This object list can be indexed using Hibernate Search (by adding @Indexed and @Field annotations to the MyObject entity). When doing an Hibernate Search query, the FullTextQueryImpl.list() method uses a Loader which try to load the MyObject entities from the database by a query such as "SELECT ... FROM MYOBJECT where id in (?,?,?,..)" (where the list of "?" is the list of identifiers returned by Lucene). Here, we have a problem: the MYOBJECT table does not exist and obviously an exception is raised. The desired result would be for example to look into the initial List<MyObject> "list" instead of asking to the database. This functionnality could be done very simply by adding a "Loader customLoader" field (with its public getter/setter) in the org.hibernate.search.query.FullTextQueryImpl class and by modifying the getLoader() method such as: private Loader getLoader(Session session, SessionFactoryImplementor sessionFactoryImplementor) { if (customLoader!=null) { customLoader.init(session, sessionFactoryImplementor); return customLoader; } ... } After this modification, the programmer can design its own Loader which implements whatever loading strategy. For the example above, the Loader.load(EntityInfo[]) method may looks for each EntityInfo.id in the initially obtained List<MyObject> "list". There is a workaround: copy the full source code of FullTextQueryImpl and add the described modifications. -- 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

3
8
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-431) More details in documentation about MassIndexer

by Sanne Grinovero (JIRA)

More details in documentation about MassIndexer ----------------------------------------------- Key: HSEARCH-431 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-431 Project: Hibernate Search Issue Type: Task Components: documentation Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0.Beta3 Add the new diagram Emmanuel has drawn with explanations about the different stages and pipelines of MassIndexer. -- 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

3
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-152) Consider using SnapshotDeletionPolicy for hot backup instead of the old locking scheme

by Emmanuel Bernard (JIRA)

Consider using SnapshotDeletionPolicy for hot backup instead of the old locking scheme -------------------------------------------------------------------------------------- Key: HSEARCH-152 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-152 Project: Hibernate Search Issue Type: New Feature Components: directory provider Reporter: Emmanuel Bernard Not sure it's really interesting in our environment though -- 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

2
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-376) Delegate search to remote nodes and aggregate

by Emmanuel Bernard (JIRA)

Delegate search to remote nodes and aggregate --------------------------------------------- Key: HSEARCH-376 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-376 Project: Hibernate Search Issue Type: New Feature Reporter: Emmanuel Bernard This would require to - discover the participating nodes - replace the IndexReaders with Searchable (for some valid reasons I chose not to initially) - use a ParallelMultiIndexSearcher - expose IndexSearcher remotely. will be be useful for infinispan -- 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

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-336) Create a DirectoryProvider for InstantiatedIndex

by Sanne Grinovero (JIRA)

Create a DirectoryProvider for InstantiatedIndex ------------------------------------------------ Key: HSEARCH-336 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-336 Project: Hibernate Search Issue Type: New Feature Components: directory provider Reporter: Sanne Grinovero Assignee: Sanne Grinovero have an option to copy startup data from at startup (like clone a FSDirectory) ? -- 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

3
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2010