October 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-119) Enable lucene similarity seach based on term frequency vector by QBE-like query

by Xin Wu (JIRA)

Enable lucene similarity seach based on term frequency vector by QBE-like query --------------------------------------------------------------------------------- Key: HSEARCH-119 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-119 Project: Hibernate Search Issue Type: New Feature Reporter: Xin Wu Scenario: Your bookstore application needs a function as follow: When a user see a list of books, there is a similar books button for each book. If user clicks this button of one book item, the similar books will be listed. The similarity is evaluated by all terms in summary of the book and similarity score is dirived from Lucene search similarity package which uses term frequency vectors in calculation. It will compare the target in all corresponding documents in the index and return the hits in order. Note: this funtion is not same as fuzzy query which still needs a definite query condition. In the contrast, similarity search only needs one or several fields (of object/document)to be specified and the rest will be automatically caculated by lucene. A QBE-like API should be used to make such query. You can specify the fields in such query. Please see discussion about this topic in the forum: http://forum.hibernate.org/viewtopic.php?t=979692 -- 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, 8 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-469) Filter caching using causes excessive memory use

by Dobes Vandermeer (JIRA)

Filter caching using causes excessive memory use ------------------------------------------------ Key: HSEARCH-469 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-469 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.1.1.GA Environment: hibernate-core-3.3.2.GA Reporter: Dobes Vandermeer The CachingWrapperFilter uses the reader instance (CacheableMultiReader) as a key for the caching. However, the reader instance keeps pointers to byte arrays in its "normsCache" and in the "normsCache" of its sub-readers; each array has one byte for each document in the index and in some cases there will be multiple of these arrays associated with differet fields. For an index with millions of records this can result in an apparent "leak" of hundreds of megabytes of memory as those readers are not re-used and the MRU cache used by default will keep up to 128 hard references to the readers by default. The search system must either re-use or delete the normsCache, OR the cache key for these filters should be tied to something else that doesn't keep references to potentially huge data arrays. Otherwise the scalability of the search subsystem is significantly impacted when using filters, as you must have enough heap to accommodate up to 128 times as many copies of the norms arrays. -- 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, 8 months

3
14
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-614) potential FileNotFoundException during slave synchronization with source

by Michael Mogley (JIRA)

potential FileNotFoundException during slave synchronization with source ------------------------------------------------------------------------ Key: HSEARCH-614 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-614 Project: Hibernate Search Issue Type: Bug Components: directory provider Affects Versions: 3.3.0.Beta2 Environment: Hibernate 3.6, Oracle 10g Reporter: Michael Mogley Priority: Minor The current file synchronization mechanism in the FSSlaveDirectoryProvider has the potential to throw a FileNotFoundException if the source file it's copying is deleted before the copy operation completes. https://forum.hibernate.org/viewtopic.php?f=9&t=1007801&p=2437680#p2437680 -- 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, 8 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-615) Support for queries limited in time: return the first nth elements within a given time

by Emmanuel Bernard (JIRA)

Support for queries limited in time: return the first nth elements within a given time -------------------------------------------------------------------------------------- Key: HSEARCH-615 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-615 Project: Hibernate Search Issue Type: New Feature Components: query Reporter: Emmanuel Bernard Fix For: 3.3.0.CR1 This was the scope of HSEARCH-374 which has been repurposed. -- 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, 8 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-434) Make use of NumericField

by Emmanuel Bernard (JIRA)

Make use of NumericField ------------------------- Key: HSEARCH-434 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-434 Project: Hibernate Search Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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, 8 months

4
39
0 / 0

[Hibernate-JIRA] Created: (EJB-435) @SqlResultSetMapping gives Invalid Column for columns not in select clause

by Rachit (JIRA)

@SqlResultSetMapping gives Invalid Column for columns not in select clause -------------------------------------------------------------------------- Key: EJB-435 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-435 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.GA Environment: DB: Oracle 10g, OS: Win XP, Hibernate 3 using JPA entitymanager Reporter: Rachit Hi, A very simple usage of SqlResultSetMapping. I want to retrieve only country Name using native query. I have specified one column country name to be fetched and mapped in Object. @SqlResultSetMapping(name = "CountryCountry", entities = { @EntityResult(entityClass = Country.class, fields = { @FieldResult(name = "countryName", column = "COUNTRY_NAME") }) public void testComplexer0NativeQuery() { em = emf.createEntityManager(); Query query = em.createNativeQuery( "select iso.COUNTRY_NAME from Country iso", "CountryCountry"); List list = query.getResultList(); System.out.println(list.size()); System.out.println(list.get(0).getClass()); } Running this I get "INFO: could not read column value from result set: ISO1_2_0_; Invalid column name" exception. The whole stack trace : javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:614) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at org.springframework.test.ConditionalTestCase.runBare(ConditionalTestCase.java:76) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.doList(Loader.java:2231) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125) at org.hibernate.loader.Loader.list(Loader.java:2120) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:312) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1722) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:165) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:175) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:67) ... 21 more Caused by: java.sql.SQLException: Invalid column name at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269) at oracle.jdbc.driver.OracleStatement.get_column_index(OracleStatement.java:6348) at oracle.jdbc.driver.OracleResultSetImpl.findColumn(OracleResultSetImpl.java:1557) at oracle.jdbc.driver.OracleResultSet.getString(OracleResultSet.java:1549) at org.hibernate.type.StringType.get(StringType.java:41) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:184) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:173) at org.hibernate.loader.Loader.getKeyFromResultSet(Loader.java:1121) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:588) at org.hibernate.loader.Loader.doQuery(Loader.java:724) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) ... 28 more Hibernate is trying to fetch all the columns present in entity to create the object. I am only interested in column/s I have specified in "@FieldResult". If I retrieve all fields in entity, It works fine though. Thanks and Regards. -- 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, 8 months

5
4
0 / 0

[Hibernate-JIRA] Created: (METAGEN-12) Investigate why it is not possible to use the Filer API to load non class resources like The API throws a FilerException with the message "Illegal name /META-INF". The call is processingEnv.getFiler().getResource((StandardLocation.CLAS /META-INF/orm.xml

by Hardy Ferentschik (JIRA)

Investigate why it is not possible to use the Filer API to load non class resources like The API throws a FilerException with the message "Illegal name /META-INF". The call is processingEnv.getFiler().getResource((StandardLocation.CLAS /META-INF/orm.xml --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: METAGEN-12 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-12 Project: Hibernate StaticMetamodel Generator Issue Type: Improvement Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik The API throws a FilerException with the message "Illegal name /META-INF". The call in question is: {code} processingEnv.getFiler().getResource((StandardLocation.CLASS_OUTPUT, "/META-INF", "orm.xml" ) {code} Currently we work around this by using {{Class.getResourceAsStream()}} -- 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, 8 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-610) AndDocIdSet makeDocIdSetOnAgreedBits() returns wrong values

by Christian Mader (JIRA)

AndDocIdSet makeDocIdSetOnAgreedBits() returns wrong values ----------------------------------------------------------- Key: HSEARCH-610 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-610 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.3.0.Beta1, 3.2.1 Reporter: Christian Mader Attachments: AndDocIdSetTest.java Depending on the DocIdSets list, AndDocIdSet fails to compute correct values in makeDocIdSetOnAgreedBits(). Please see the attached test cases, test_middle() fails and in my opinion it shouldn't. -- 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, 8 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5427) derby 10.6.1.0 native sequence support broken

by Max Giesbert (JIRA)

derby 10.6.1.0 native sequence support broken --------------------------------------------- Key: HHH-5427 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5427 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0.Beta1, 3.5.4, 3.5.3, 3.5.2 Environment: apache derby, hibernate 3.5.x/3.6 Reporter: Max Giesbert see also: https://forum.hibernate.org/viewtopic.php?f=1&t=1005637&view=previous Derby 10.6.1 officially supports sequences. (See JIRA-Task: https://issues.apache.org/jira/browse/DERBY-712, Docs: https://issues.apache.org/jira/browse/DERBY-4568). usage (e.g. @Id @GeneratedValue(strategy=GenerationType.SEQUENCE) ) produces: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.dao.InvalidDataAccessResourceUsageException: could not get next sequence value; nested exception is org.hibernate.exception.SQLGrammarException: could not get next sequence value org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:487) org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:430) javax.servlet.http.HttpServlet.service(HttpServlet.java:617) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) fix is: org.hibernate.dialect.DerbyDialect needs to override getSequenceNextValString as follows @Override public String getSequenceNextValString(String sequenceName) { return "values next value for " + sequenceName; } -- 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, 8 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5692) Invalid {h-schema} replacement in native sql queries

by Greg Maczuga (JIRA)

Invalid {h-schema} replacement in native sql queries ---------------------------------------------------- Key: HHH-5692 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5692 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.3 Reporter: Greg Maczuga Native-sql placeholders for default schema and catalog i.e. {h-schema} replacement implemented in HHH-2576 have bug. It doesn't replace {h-schema} in stored procedures calls due to embed brackets i.e. "{ ? = call {h-schema}manager.check(:userId)}" do NOT get replaced correctly. -- 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, 8 months

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