October 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-707) Expose faceting via annotations

by Hardy Ferentschik (JIRA)

Expose faceting via annotations ------------------------------- Key: HSEARCH-707 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-707 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.4.0.Alpha1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.4.0.Beta1 -- 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
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-704) Loading objects leads to 1+n queries when JPA's @Id != @DocumentId property

by Emmanuel Bernard (JIRA)

Loading objects leads to 1+n queries when JPA's @Id != @DocumentId property --------------------------------------------------------------------------- Key: HSEARCH-704 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-704 Project: Hibernate Search Issue Type: Improvement Components: query Reporter: Emmanuel Bernard Fix For: 3.4.0 Today we load the objects once using a Criteria query. And to return the object by relevance, we call ObjectLoaderHelper.returnAlreadyLoadedObjectsInCorrectOrder which in the @DocumentId != @Id case, runs one criteria query per object again. That leads to 1+n queries which is not acceptable. To work around that we could (only in the @DocumentId != @Id) case: - run the first criteria query so that it returns a List of tuples { documentIdProperty, entity } - keep this List around - when loading entities ber relevant order, use this list to fetch the data from memory instead of this additional n Criteria queries) -- 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
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-950) Update documentation quick start to point to the latest lib versions (like Hibernate Core 4.0.0.Final

by Emmanuel Bernard (JIRA)

Update documentation quick start to point to the latest lib versions (like Hibernate Core 4.0.0.Final ----------------------------------------------------------------------------------------------------- Key: HSEARCH-950 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-950 Project: Hibernate Search Issue Type: Task Components: documentation Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik Fix For: 4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-942) Accept configuration properties starting with "org." as well

by Sanne Grinovero (JIRA)

Accept configuration properties starting with "org." as well ------------------------------------------------------------ Key: HSEARCH-942 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-942 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Priority: Minor Fix For: 4.1 All configuration properties need to be prefixed with "hibernate.search."; it happens that people mistakenly write "org.hibernate.search." . It would be easy to accept this variant too, and log a warning about it. Or log just a warning if the code gets tricky. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

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

14 years, 3 months

3
28
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-899) Check for illegal usage of @IndexedEmbedded

by Sanne Grinovero (JIRA)

Check for illegal usage of @IndexedEmbedded ------------------------------------------- Key: HSEARCH-899 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-899 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Priority: Minor Fix For: 4.1 Apparently some people tend to assume that in indexed embedded classes all normal fields should use the @IndexedEmbedded annotation instead of @Field/.. like in: {code} @IndexedEmbedded String countryName {code} Might be nice to check for such unexpected usage, as it's currently silently ignored. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-655) Implements the FuturTask.cancel function in the massindexer

by Grégory Oliver (JIRA)

Implements the FuturTask.cancel function in the massindexer ----------------------------------------------------------- Key: HSEARCH-655 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-655 Project: Hibernate Search Issue Type: Improvement Components: massindexer Affects Versions: 3.3.0.Final Reporter: Grégory Oliver I can't use the massindexer because each time I stop the massindexer by killing the process, it corrupt the lucene directory. -- 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
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-863) Use JBoss Logging to create i18n exceptions

by Emmanuel Bernard (JIRA)

Use JBoss Logging to create i18n exceptions ------------------------------------------- Key: HSEARCH-863 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-863 Project: Hibernate Search Issue Type: Improvement Components: analyzer, directory provider, engine, infinispan, integration, mapping, massindexer, optimizer, query, serialization Reporter: Emmanuel Bernard This is not top priority but new code should follow this and encountered code should be migrated. If someone is willing to take the codebase over and convert the better {code} @MessageLogger(projectCode = "HSEARCH") public interface Log extends BasicLogger { @Message( value="Unable to start serialization layer", id=82 ) SearchException unableToStartSerializationLayer(@Cause Throwable e); } {code} And in the code throwing the exception {code} throw log.unableToStartSerializationLayer( e ); {code} ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
9
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-812) Faceting: Possibiltiy to set behaviour (SHOULD/MUST) when selecting multiple facets should

by Elmer van Chastelet (JIRA)

Faceting: Possibiltiy to set behaviour (SHOULD/MUST) when selecting multiple facets should ------------------------------------------------------------------------------------------ Key: HSEARCH-812 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-812 Project: Hibernate Search Issue Type: Improvement Components: query Affects Versions: 3.4.0.Final Environment: - Reporter: Elmer van Chastelet Current implementation combines multiple facets from the same group by OR-ing them (SHOULD): {code} private Query createSelectionGroupQuery(FacetSelectionImpl selection) { BooleanQuery orQuery = new BooleanQuery(); for ( Facet facet : selection.getFacetList() ) { orQuery.add( facet.getFacetQuery(), BooleanClause.Occur.SHOULD ); } return orQuery; } {code} It might be useful to also allow AND-ing the facets. Some examples: When searching for publications, I want the publications where both 'Kim' and 'John' are author When searching for recipes, I want meals with both 'tomatoes' and 'eggs'. This is in case of fields that might have mutliple values, so its working is relying on [HSEARCH-726|https://hibernate.onjira.com/browse/HSEARCH-726]. I currently have adapted the code myself, to be able to set AND/OR as default facet combinator, but this is not using the Hibernate Search Query language contexts. This improvement should be easy to implement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

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

14 years, 3 months

3
10
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 October 2011