January 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-331) Verify sorting behaviour for DoubleBridge

by Sanne Grinovero (JIRA)

Verify sorting behaviour for DoubleBridge ----------------------------------------- Key: HSEARCH-331 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-331 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero -- 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

16 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-155) JMS implementation requires jndi - I want to use it in J2SE no web container/appserver

by Jason Eacott (JIRA)

JMS implementation requires jndi - I want to use it in J2SE no web container/appserver -------------------------------------------------------------------------------------- Key: HSEARCH-155 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-155 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.0.0.GA Environment: All Reporter: Jason Eacott the current JMS implementation requires jndi configuration, I would like to use hibernatesearch in a j2se project with the jms configuration. -- 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

16 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-211) SharedReaderProvider: should own lock when testing for index state

by Sanne Grinovero (JIRA)

SharedReaderProvider: should own lock when testing for index state ------------------------------------------------------------------ Key: HSEARCH-211 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-211 Project: Hibernate Search Issue Type: Bug Components: directory provider Reporter: Sanne Grinovero Developing a new IndexReader I made a stress-test to compare performance to base readers, but got this when measuring SharedReaderProvider: Exception in thread "pool-2-thread-13" org.apache.lucene.store.AlreadyClosedException: this IndexReader is closed at org.apache.lucene.index.IndexReader.ensureOpen(IndexReader.java:163) at org.apache.lucene.index.DirectoryIndexReader.isCurrent(DirectoryIndexReader.java:149) at org.hibernate.search.reader.SharedReaderProvider.openReader(SharedReaderProvider.java:83) at org.hibernate.search.query.FullTextQueryImpl.buildSearcher(FullTextQueryImpl.java:486) at org.hibernate.search.query.FullTextQueryImpl.getResultSize(FullTextQueryImpl.java:528) at org.hibernate.search.test.reader.performance.SearchActivity.doAction(SearchActivity.java:24) at org.hibernate.search.test.reader.performance.AbstractActivity.run(AbstractActivity.java:54) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) -- 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

16 years

2
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-305) Hibernate search doesn't work with criteria when it is not initialized laziily

by prabhu lal (JIRA)

Hibernate search doesn't work with criteria when it is not initialized laziily ------------------------------------------------------------------------------ Key: HSEARCH-305 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-305 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.0.1.GA Environment: MYSQL,HIBERNATE 3.0 , Flex with dpHibernate Reporter: prabhu lal Attachments: QueryLoader.java For the RIA applications complete object tree should be initialized(To achieve that there is work around available like dpHibernate). But hibernate search doesn't apply criteria to queried result because it returns the result on the basis of wether objectt is intialized by loading the criteria objects.Since there is no lazy intiaialization so all the objects are loaded andcomplete result will be return irrespctive of criteria. code snipet from Hibernate Search API(org.hibernate.search.engine.QueryLoader.java.): public List load(EntityInfo... entityInfos) { final int maxResults = entityInfos.length; if ( maxResults == 0 ) return EMPTY_LIST; if ( entityType == null ) throw new AssertionFailure( "EntityType not defined" ); if ( criteria == null ) criteria = session.createCriteria( entityType ); DocumentBuilder builder = searchFactoryImplementor.getDocumentBuilders().get( entityType ); String idName = builder.getIdentifierName(); int loop = maxResults / MAX_IN_CLAUSE; boolean exact = maxResults % MAX_IN_CLAUSE == 0; if ( !exact ) loop++; Disjunction disjunction = Restrictions.disjunction(); for (int index = 0; index < loop; index++) { int max = index * MAX_IN_CLAUSE + MAX_IN_CLAUSE <= maxResults ? index * MAX_IN_CLAUSE + MAX_IN_CLAUSE : maxResults; List ids = new ArrayList( max - index * MAX_IN_CLAUSE ); for (int entityInfoIndex = index * MAX_IN_CLAUSE; entityInfoIndex < max; entityInfoIndex++) { ids.add( entityInfos[entityInfoIndex].id ); } disjunction.add( Restrictions.in( idName, ids ) ); } criteria.add( disjunction ); criteria.list(); //load all objects //mandatory to keep the same ordering List result = new ArrayList( entityInfos.length ); for (EntityInfo entityInfo : entityInfos) { Object element = session.load( entityInfo.clazz, entityInfo.id ); if ( Hibernate.isInitialized( element ) ) { //This is true for all the objects,in case objects are eagrly intialized //all existing elements should have been loaded by the query, //the other ones are missing ones result.add( element ); } } return result; } -- 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

16 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-337) Search return the same row multiple times on Select

by Santhosh Kumaran (JIRA)

Search return the same row multiple times on Select --------------------------------------------------- Key: HSEARCH-337 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-337 Project: Hibernate Search Issue Type: Bug Environment: Hibernate Reporter: Santhosh Kumaran I have a table in the following pattern on MySQL 5.1 Table1 Key1 int Key2 int field1 tinyint field2 tinyint field3 tinyint I have the sql query like "SELECT {table1Entity.*} FROM TABLE1 table1 where Key1=?" This query will satify for 3 rows and has to get me the 3 filtered rows. and the code like this SQLQuery sqlQuery = session.createSQLQuery(query); sqlQuery.setInteger(0, 5001); sqlQuery = sqlQuery.addEntity("table1Entity", Table1Entity.class); List entityList = sqlQuery.list(); The list contain 3 entity objects, but 3 copies of the first row. ( not all 3 rows). First row coming 3 times instead of 2nd and 3rd row values. Please let me know, is it a bug or not? - SANSSAN -- 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

16 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-341) Support for fetch joins in Hibernate search queries

by Seema Richard (JIRA)

Support for fetch joins in Hibernate search queries --------------------------------------------------- Key: HSEARCH-341 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-341 Project: Hibernate Search Issue Type: New Feature Components: query Affects Versions: 3.1.0.GA Reporter: Seema Richard In Hibernate search, the related entities marked using @IndexedEmbedded are now getting lazy fetched which is causing unnecessary queries to be generated. It would be useful if fetch joins can be used for better performance. -- 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

16 years

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-350) @IndexedEmbedded appears to handle only declared type, not subtypes

by Taylor Mathewson (JIRA)

@IndexedEmbedded appears to handle only declared type, not subtypes ------------------------------------------------------------------- Key: HSEARCH-350 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-350 Project: Hibernate Search Issue Type: Improvement Components: mapping Reporter: Taylor Mathewson Given the following: @Indexed class A{ @IndexedEmbedded public B b; } class B{ ...//some indexed fields } public class C{ ...//some more indexed fields } The index for A will only contain the indexed fields in B, never the fields in C, even if the runtime type of A's b property is of class C. Thank you. -- 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

16 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-313) Provide a callback on indexing exception

by Emmanuel Bernard (JIRA)

Provide a callback on indexing exception ---------------------------------------- Key: HSEARCH-313 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-313 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard An application can pass a callback and be notified when an indexing operation fails. The data associated with the operation is passed as a parameter (eg list of lucene work). The application can do anything from here: - log failing ids - swallow - put that in a queue for retry etc -- 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

16 years

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-362) When using hibernate-search3.1.0 GA, Search throws AlreadyClosedException under certain circumstances

by S Ravi Bhaskar (JIRA)

When using hibernate-search3.1.0 GA, Search throws AlreadyClosedException under certain circumstances ----------------------------------------------------------------------------------------------------- Key: HSEARCH-362 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-362 Project: Hibernate Search Issue Type: Bug Components: directory provider Affects Versions: 3.1.0.GA Environment: Hibernate 3.2.6 GA, ant 1.7.1 Reporter: S Ravi Bhaskar The below code throws an AlreadyClosedException when trying to open the lucene index. Junit test to test it works from eclipse, fails in an ant build. I suspect it is trying to reuse a handle to the index. Please let me know if you need more information. I had to bump back my hibernate search version to 3.0.1 GA, and then it started working. I am getting by, but would ideally like to use 3.1.0 GA without this exception. I think it has something to do with Search.getFullTextEntityManager((getJpaPersistenceContext().getEntityManager())); VS Search.createFullTextEntityManager((getJpaPersistenceContext().getEntityManager())); in the older version. String query = "BlahBlahBlah"; org.apache.lucene.queryParser.QueryParser parser = new QueryParser("ItemTitle", new StandardAnalyzer() ); org.apache.lucene.search.Query luceneQuery; try { luceneQuery = parser.parse(query); } catch (ParseException e) { // TODO Auto-generated catch block logger.error(String.format("Error parsing search querystring ")); return null; } javax.persistence.Query fullTextQuery = createFullTextEntityManager().createFullTextQuery(luceneQuery, klass); List result = fullTextQuery.getResultList(); // return a list of managed where createFullTextEntityManager() is public FullTextEntityManager createFullTextEntityManager() { return Search.getFullTextEntityManager((getJpaPersistenceContext().getEntityManager())); } -- 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

16 years

3
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-421) Exceptions happening in backend are unnoticed

by Sanne Grinovero (JIRA)

Exceptions happening in backend are unnoticed --------------------------------------------- Key: HSEARCH-421 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-421 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.1.GA, 3.1.0.GA Reporter: Sanne Grinovero Fix For: 3.2.0.Beta2 Any exception happening in the backend is not noticed as it happens in a separate thread. -- 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

16 years

3
27
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 January 2010