May 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5817) Passing char[] or byte[] to equal function of CriteriaBuilder throws java.lang.ClassCastException.

by Vyacheslav Dimitrov (JIRA)

Passing char[] or byte[] to equal function of CriteriaBuilder throws java.lang.ClassCastException. -------------------------------------------------------------------------------------------------- Key: HHH-5817 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5817 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.6.0 Environment: Hibernate 3.6.0-Finale, derby db, mysql db, hsqldb Reporter: Vyacheslav Dimitrov Priority: Minor Attachments: hibernate_3_6_0.patch We have byte[] field in one of our entity and we want to make query like this. {code} byte[] var = ...; Predicate p = builder.equal(root.get("ourByteField"), var); criteria.where(p); {code} But this code throws exception: [java] Exception in thread "main" java.lang.ClassCastException: [B cannot be cast to [Ljava.lang.Object; [java] at org.hibernate.ejb.AbstractQueryImpl.registerParameterBinding(AbstractQueryImpl.java:349) [java] at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:364) [java] at org.hibernate.ejb.criteria.CriteriaQueryCompiler$1$1.bind(CriteriaQueryCompiler.java:194) [java] at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:247) [java] at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:441) [java] at ru.petrsu.nest.oqlite.test.TestParser.main(TestParser.java:92) [java] Java Result: 1 because class AbstractQueryImpl has code: {code} ... else if ( value.getClass().isArray() ) { final Object[] array = (Object[]) value; ... {code} We offer to change this "if" like this {code} ... else if ( value.getClass().isArray() && value.getClass().equals(Object[].class)) { final Object[] array = (Object[]) value; ... {code} Due to this new condition we get what we want and our criteria works fine. (At least ClassCastExceptio isn't occured). Patch is attached (Also I can do pull request, if needed). -- 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

4
13
0 / 0

[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

12 years, 9 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

12 years, 9 months

3
6
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, 9 months

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

12 years, 9 months

3
5
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, 9 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, 9 months

3
16
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-663) Support wildcard and jolly characters in Query DSL

by Sanne Grinovero (JIRA)

Support wildcard and jolly characters in Query DSL -------------------------------------------------- Key: HSEARCH-663 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-663 Project: Hibernate Search Issue Type: Improvement Components: query Reporter: Sanne Grinovero Fix For: 3.4.0 -- 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
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-713) Drill-down faceting query should not affect other facet counts

by Sanne Grinovero (JIRA)

Drill-down faceting query should not affect other facet counts -------------------------------------------------------------- Key: HSEARCH-713 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-713 Project: Hibernate Search Issue Type: Improvement Components: query Reporter: Sanne Grinovero Assignee: Hardy Ferentschik Fix For: 3.4.0 Using the "drill-down" function in faceting should - at least by default - behave like Amazon's faceting: it affects the filtering of the list shown as current results but should not affect the faceting count of other facets. (It will of course affect sub-facets, so people can navigate up/down the facet tree to narrow down the results and explore different branches, but the parent branch and it's peers shouldn't be affected. It's still possible to apply global filters which affect all facets (like a filter applied on root): example enable "only items with at least 4 star reviews" might affect all counters in the tree. But if I'm in the area "TVs", and then the options {"LED", "Plasma"} open up, when we select "LED" the counters for both "Plasma" and "LED" should not change -> just of course the main results list will show only LED televisions. For those people who think it should be possible to affect such a drill down feature as a filter, they can still apply the filter globally (on the root query). {quote}<emmanuel> but to move forward, let's start with what we have. It seems that such alternative are definitely going to be an option on the FacetedManager <emmanuel> facetedManager.countAs(AMAZON) :){quote} -- 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

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-634) Improve Query DSL to support multi terms search

by Emmanuel Bernard (JIRA)

Improve Query DSL to support multi terms search ----------------------------------------------- Key: HSEARCH-634 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-634 Project: Hibernate Search Issue Type: Improvement Components: query Affects Versions: 3.3.0.CR1 Reporter: Emmanuel Bernard Fix For: 3.4.0 {code}final Query luceneQuery = builder .bool() .should( builder .keyword() .onField( "title" ).boostedTo( 4f ) .andField( "description" ) .matching( "plants" ) .createQuery() ) .should( builder .keyword() .onField( "title" ).boostedTo( 4f ) .andField( "description" ) .matching( "hands" ) .createQuery() ) .createQuery();{code} is too verbose can could be done as {code}final Query luceneQuery = builder .keyword() .onField( "title" ).boostedTo( 4f ) .andField( "description" ) .matching( "plants", "hands" ) .createQuery();{code} -- 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

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2011