March 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-633) Allow definition of annotations at package-level in package-info.java

by Michael Mogley (JIRA)

Allow definition of annotations at package-level in package-info.java --------------------------------------------------------------------- Key: HSEARCH-633 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-633 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.3.0.CR1 Environment: Hibernate 3.6, Oracle 10g Reporter: Michael Mogley Priority: Minor Currently, it is not possible to define package-level annotations, for example a set of analyzer definitions that are shared by all classes in a package. Having this feature would really aid in code organization, allowing global search-related annotations to be separate from model classes. The situation right now, where an AnalyzerDef annotation defined in one model class is also referencable from another model class, is not intuitive. Please see the thread below: https://forum.hibernate.org/viewtopic.php?f=9&t=1008145&p=2438323#p2438323 -- 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

13 years

4
5
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

13 years

3
8
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-668) Provide a setting to bring under the same transaction the DB operation and the Infinispan Lucene Directory

by Emmanuel Bernard (JIRA)

Provide a setting to bring under the same transaction the DB operation and the Infinispan Lucene Directory ---------------------------------------------------------------------------------------------------------- Key: HSEARCH-668 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-668 Project: Hibernate Search Issue Type: New Feature Reporter: Emmanuel Bernard Assignee: Sanne Grinovero As discussed on the call with Grant -- 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

13 years

3
9
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-697) Think about improving type mismatch detection between QueryBuilder output and targeted FullTextQuery

by Sanne Grinovero (JIRA)

Think about improving type mismatch detection between QueryBuilder output and targeted FullTextQuery ---------------------------------------------------------------------------------------------------- Key: HSEARCH-697 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-697 Project: Hibernate Search Issue Type: Bug Components: query Reporter: Sanne Grinovero Fix For: 3.4.0.Beta1 Use cases: 1)we ask for the target type when creating a QueryBuilder, then we ask again for the same information again at FullTextQuery creation - they must match. 2)it seems that when people get the match wrong, they receive cryptic error messages (see https://forum.hibernate.org/viewtopic.php?f=9&t=1009700 ) It would be nice if we could infer the target type from the builder, we'd likely have to introduce a new class hiding away org.apache.search.Query in something which knows a bit more about types. Or maybe introduce a new method in FullTextSession to create a Hibernate.Query directly from the builder, projecting on the known types. train of thoughts.. maybe this could lead to a typesafe API to define fulltext projections reusing JPA2 metamodel in case it's available. -- 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

13 years

3
5
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

13 years

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

13 years

2
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-692) FieldSelection should be allowed in more cases

by Sanne Grinovero (JIRA)

FieldSelection should be allowed in more cases ---------------------------------------------- Key: HSEARCH-692 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-692 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Fix For: 3.5 The allowFieldSelection is now turned off by the DocumentBuilder if the entity contains any field which is not two-way projectable. This results in having FieldSelectors being disabled, even if the only field being asked for as projection contains only two-way projectable fields. Also, the current code in org.hibernate.search.engine.DocumentBuilderIndexedEntity.checkAllowFieldSelection() is a mess; we should figure out from the bridges exactly which fields they are going to need to read: FieldSelector needs now to be disabled for bridges such as org.hibernate.search.test.id.PersonPKBridge. -- 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

13 years

1
2
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

13 years

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

13 years

3
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5308) hibernate cannot handle Inheritance, if the discriminatorColumn is part of a composite pk in a @MappedSupperclass

by AndyW (JIRA)

hibernate cannot handle Inheritance, if the discriminatorColumn is part of a composite pk in a @MappedSupperclass ----------------------------------------------------------------------------------------------------------------- Key: HHH-5308 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5308 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.2 Environment: Linux, Java 6 Reporter: AndyW Attachments: jpatest_hibernate_aktuell.zip Hi, i am having the following mapping structure @MappedSuperclass LadeeinheitEinausgaenge | @Entity | @Inheritance(strategy=InheritanceType.SINGLE_TABLE) | @DiscriminatorColumn(name = "LAEA_TYP") | @Table(name = "LADEEINHEIT_EINAUS") +- AbstractEinAusgang | | @DiscriminatorValue("AUSGANG") | | @Entity | +- LadeeinheitAusgaenge | | @DiscriminatorValue("EINGANG") | | @Entity | +- LadeeinheitEingaenge The composite pk is defined in the MappedSuperclass. The discriminator column is part of the composite pk. when i start my app, i am getting the following error: > Repeated column in mapping for entity: de.dbsystel.gate.integration.model.LadeeinheitAusgaenge column: LAEA_TYP (should be mapped with insert="false" update="false") the error message is kind of misleading, because the @DiscriminatorColumn annotation only defines which column to use for the mapping, i guess. however the actual mapping is defined in the MappedSuperclass. When moving the @DiscriminatorColumn to the mappedSuperclass, hibernate does not complain when starting, but then it creates tables, it create the default DiscriminatorColumn named DTYPE, which is not wanted, because i explicitly defined a discriminator column. If the discriminator column is defined in the mappedSuperclass then it will be ignore. if it is defined in my abstract base entity. then i get the error mentioned above. My Intention is to query the AbstractEinAusgang and get one of the two possible concrete classes, that are defined via the discriminator value. i have attached the testcase that shows the problem. cheers, andy -- 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

13 years

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2011