1:54 p.m.
If you see potential optimizations, then open a JIRA subtsk under
"make use of all Lucene 3 capabilities" or something like that :)
I was just thinking that migrating to 2.9 and seeing the deprecation
warnings was easier than compilation failures with no @see references.
BTW, payload is stored in the index and queryable apparently, that
could be a nice trick to speed up HSearch object resolution.
Basically, if they offer a way to read payload from a result, we could
read the id and the classname just by reading the index and avoid
loading the document (which is in a different Lucene file and force us
to do an extra I/O today).
On 28 nov. 09, at 13:08, Sanne Grinovero wrote:
Hi Emmanuel,
migrating to 2.9 should be quite easy, I don't think there's a need to
open an issue for each change.
beta2 is good, we could even migrate to 3.0 in the same release.
I think I could move to 2.9 with a single patch having low impact, and
to 3.0 with another little patch.
Of course, I'm only thinking about making it compatible: really making
use of the new cool features is another story but this is another
issue right? like the new ranges optimizations for dates and numbers.
I've opened an "update to Lucene 3" issue for beta2: HSEARCH-424
Cheers,
Sanne
---------- Forwarded message ----------
From: Emmanuel Bernard (JIRA) <noreply(a)atlassian.com>
Date: 2009/11/27
Subject: [hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-420)
Hibernate Search does not work with Lucene 3.0.0
To: hibernate-issues(a)lists.jboss.org
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-420?pag...
]
Emmanuel Bernard commented on HSEARCH-420:
------------------------------------------
Let's migrate to 2.9, open issues for all the deprecations and then
move to lucene 3.
I think 3.2 beta2 is a good candidate for that. WDYT?
> Hibernate Search does not work with Lucene 3.0.0
> ------------------------------------------------
>
> Key: HSEARCH-420
> URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-420
> Project: Hibernate Search
> Issue Type: Bug
> Affects Versions: 3.1.1.GA
> Reporter: Mark Derricutt
>
> After updating my lucence dependency to the recently released 3.0.0
> I see the following stack trace:
> org.fest.reflect.exception.ReflectionError: Unable to invoke method
> 'bindEntityProvider' with arguments
> [smx3.schema.provider.SchemaEntityProvider@3747c1db]
> at org.fest.reflect.method.Invoker.invoke(Invoker.java:101)
> at
> smx3
> .testing
> .SessionFactoryBuilder
> .buildSessionFactory(SessionFactoryBuilder.java:61)
> at
> smx3
> .partyresource
> .service
> .AgreementServiceImplTest.setup(AgreementServiceImplTest.java:38)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun
> .reflect
> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun
> .reflect
> .DelegatingMethodAccessorImpl
> .invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.fest.reflect.method.Invoker.invoke(Invoker.java:99)
> ... 28 more
> Caused by: java.lang.NoSuchMethodError:
> org.apache.lucene.store.FSDirectory.getDirectory(Ljava/io/
> File;)Lorg/apache/lucene/store/FSDirectory;
> at
> org
> .hibernate
> .search
> .store
> .DirectoryProviderHelper.createFSIndex(DirectoryProviderHelper.java:
> 77)
> at
> org
> .hibernate
> .search
> .store.FSDirectoryProvider.initialize(FSDirectoryProvider.java:44)
> at
> org
> .hibernate
> .search
> .store
> .DirectoryProviderFactory
> .createDirectoryProvider(DirectoryProviderFactory.java:129)
> at
> org
> .hibernate
> .search
> .store
> .DirectoryProviderFactory
> .createDirectoryProviders(DirectoryProviderFactory.java:63)
> at
> org
> .hibernate
> .search
> .impl.SearchFactoryImpl.initDocumentBuilders(SearchFactoryImpl.java:
> 404)
> at
> org
> .hibernate
> .search.impl.SearchFactoryImpl.<init>(SearchFactoryImpl.java:119)
> at
> org
> .hibernate
> .search
> .event.ContextHolder.getOrBuildSearchFactory(ContextHolder.java:30)
> at
> org
> .hibernate
> .search
> .event
> .FullTextIndexEventListener
> .initialize(FullTextIndexEventListener.java:79)
> at org.hibernate.event.EventListeners
> $1.processListener(EventListeners.java:198)
> at
> org
> .hibernate
> .event.EventListeners.processListeners(EventListeners.java:181)
> at
> org
> .hibernate
> .event.EventListeners.initializeListeners(EventListeners.java:194)
> at
> org
> .hibernate
> .cfg.Configuration.getInitializedEventListeners(Configuration.java:
> 1352)
> at
> org
> .hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:
> 1341)
> at
> org
> .hibernate
> .cfg
> .AnnotationConfiguration
> .buildSessionFactory(AnnotationConfiguration.java:812)
> at
> smx3
> .entity
> .EntityActivatorImpl.bindSessionFactory(EntityActivatorImpl.java:197)
> at
> smx3
> .entity
> .EntityActivatorImpl.rebuildSessionFactory(EntityActivatorImpl.java:
> 106)
> at
> smx3
> .entity
> .EntityActivatorImpl
> .rebuildFromEntityProviders(EntityActivatorImpl.java:85)
> at
> smx3
> .entity
> .EntityActivatorImpl.bindEntityProvider(EntityActivatorImpl.java:68)
> It would seem that Lucene 3.0.0 has broken APIs with 2.9.0 which
> worked fine with Hibernate Search.
--
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
_______________________________________________
hibernate-issues mailing list
hibernate-issues(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-issues