Compass, Lucene and Grails Searchable Plugin
|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
 |
Compass, Lucene and Grails Searchable Plugin
by Mike Brevoort
::
Rate this Message:
|
|
|
Re: Compass, Lucene and Grails Searchable Plugin
by teck-terracotta
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Hi Mike, Let
me say up front that I don’t know anything about compass – I just
browsed some of their code (I looked at trunk of their svn repo). So if “org.compass.core.lucene.engine.store.RAMLuceneSearchEngineStore.ramIndexes”
is a root, then this lock snippet should get past that exception: <named-lock>
<method-expression>* org.compass.core.lucene.engine.store.RAMLuceneSearchEngineStore.*(..)</method-expression>
<lock-level>write</lock-level>
<lock-name>theLockName</lock-name>
</named-lock> That will apply the named lock to all
methods of that class. In reality, you only need to apply the lock to those
methods that read or write the shared object. It’s not obvious, but you’ll
also need to <include> that class
<include>
<class-expression>org.compass.core.lucene.engine.store.RAMLuceneSearchEngineStore</class-expression>
</include> All this said, this approach with named
locks is rather blunt, but it is useful for experimenting. Hope this helps -tim From:
tc-users-bounces@...
[mailto:tc-users-bounces@...] On Behalf Of Mike Brevoort Hi, .store.RAMLuceneSearchEngineStore and manages each subindex
RAMDirectory in a java.util.HashMap called ramIndexes. _______________________________________________ tc-users mailing list tc-users@... http://lists.terracotta.org/mailman/listinfo/tc-users |
|
|
Re: Compass, Lucene and Grails Searchable Plugin
by Mike Brevoort
::
Rate this Message:
|
|
|
Re: Compass, Lucene and Grails Searchable Plugin
by Mike Brevoort
::
Rate this Message:
|
|
|
Re: Compass, Lucene and Grails Searchable Plugin
by Orion Letizi
::
Rate this Message:
|
|
|
Re: Compass, Lucene and Grails Searchable Plugin
by Mike Brevoort
::
Rate this Message:
|
|
|
Re: Compass, Lucene and Grails Searchable Plugin
by njain
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Hi Mike, Before
an object can be shared by Terracotta, the ClassLoader that loaded object’s
class has to be known to Terracotta. For core java and supported frameworks/container
we take care of registering relevant classloaders with Terracotta. The
approach for Grails is 1) Identify the place where Grails classloader is created. 2) Register it with terracotta like this (this is to done where
ClassLoader is created) ((NamedClassLoader) loader).__tc_setClassLoaderName("Grail Classloader"); //should follow some naming convention for assigning the name ClassProcessorHelper.registerGlobalLoader((NamedClassLoader) loader);
Initially
try with direct code modification. If everything works well, we can convert
this info a config module that will inject the proper byte code at runtime so
as to avoid any code tweaking. Thanks, Nitin From:
tc-users-bounces@...
[mailto:tc-users-bounces@...] On Behalf Of Mike Brevoort Tim, On Jan 22, 2008 7:57 PM, Tim Eck <teck@...> wrote: Hi Mike,
Let me say up front that I don't know anything about compass – I just
browsed some of their code (I looked at trunk of their svn repo). So if
"org.compass.core.lucene.engine.store.RAMLuceneSearchEngineStore.ramIndexes"
is a root, then this lock snippet should get past that exception: <named-lock>
<method-expression>*
org.compass.core.lucene.engine.store.RAMLuceneSearchEngineStore.*(..)</method-expression>
<lock-level>write</lock-level>
<lock-name>theLockName</lock-name> </named-lock> That will apply the named lock to all methods of that class.
In reality, you only need to apply the lock to those methods that read or write
the shared object. It's not obvious, but you'll also need to <include>
that class <include> <class-expression>org.compass.core.lucene.engine.store.RAMLuceneSearchEngineStore</class-expression> </include> All this said, this approach with named locks is rather
blunt, but it is useful for experimenting. Hope this helps -tim From: tc-users-bounces@...
[mailto:tc-users-bounces@...]
On Behalf Of Mike Brevoort Hi, .store.RAMLuceneSearchEngineStore
and manages each subindex RAMDirectory in a java.util.HashMap called
ramIndexes.
_______________________________________________ tc-users mailing list tc-users@... http://lists.terracotta.org/mailman/listinfo/tc-users |
|
|
Re: Compass, Lucene and Grails Searchable Plugin
by teck-terracotta
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Everything Nitin mentions is spot on…just
a few more notes to add: The purpose of the classloader name is to
give loader instances a common identity across VMs. For every clustered object
in terracotta, we record the identity of the classloader that defined it’s
class. That identity is used to resolve a loader instance when the object is
referenced on another VM. The terracotta client that resides in each VM
maintains a map of loader name to loader instance (the registerGlobalLoader()
call lets you add entries to the map). The whole reason I’m detailing this
is that you might need to assign more meaningful/complex names to the grails
loader(s) than the static string in the example code below. If there is more
than one grails loader, then more than likely the name will need to be more specific. Other notes: -
There
are two terracotta types referenced in the example code – the fully
qualified names of those classes are com/tc/object/loaders/NamedClassLoader and
com/tc/object/bytecode/hook/impl/ClassProcessorHelper -
Both of
those types can be found in tc.jar (or for terracotta versions 2.5.1+, there is
a specific terracotta-api-xxx.jar that should be used) -
You do
not need to include any of these jars at runtime, they are only needed for
compilation. At runtime these types are present in the bootstrap classloader
(via the “dso-boot” jar) so including them in CLASSPATH or in web
app is not a good idea From:
tc-users-bounces@...
[mailto:tc-users-bounces@...] On Behalf Of Nitin Jain Hi Mike,
Before an object can be shared by Terracotta, the ClassLoader that loaded
object’s class has to be known to Terracotta. For core java and supported
frameworks/container we take care of registering relevant classloaders with
Terracotta.
The approach for Grails is 1) Identify the place where Grails classloader is created. 2) Register it with terracotta like this (this is to done where
ClassLoader is created) ((NamedClassLoader) loader).__tc_setClassLoaderName("Grail Classloader"); //should follow some naming convention for assigning the name ClassProcessorHelper.registerGlobalLoader((NamedClassLoader) loader);
Initially try with direct code modification. If everything works well, we can
convert this info a config module that will inject the proper byte code at
runtime so as to avoid any code tweaking. Thanks, Nitin From:
tc-users-bounces@...
[mailto:tc-users-bounces@...] On Behalf Of Mike Brevoort Tim, On Jan 22, 2008 7:57 PM, Tim Eck <teck@...> wrote: Hi Mike,
Let me say up front that I don't know anything about compass – I just browsed
some of their code (I looked at trunk of their svn repo). So if
"org.compass.core.lucene.engine.store.RAMLuceneSearchEngineStore.ramIndexes"
is a root, then this lock snippet should get past that exception: <named-lock>
<method-expression>*
org.compass.core.lucene.engine.store.RAMLuceneSearchEngineStore.*(..)</method-expression>
<lock-level>write</lock-level>
<lock-name>theLockName</lock-name> </named-lock> That will apply the named lock to all methods of that class.
In reality, you only need to apply the lock to those methods that read or write
the shared object. It's not obvious, but you'll also need to <include>
that class <include>
<class-expression>org.compass.core.lucene.engine.store.RAMLuceneSearchEngineStore</class-expression> </include> All this said, this approach with named locks is rather
blunt, but it is useful for experimenting. Hope this helps -tim From: tc-users-bounces@...
[mailto:tc-users-bounces@...]
On Behalf Of Mike Brevoort Hi, .store.RAMLuceneSearchEngineStore
and manages each subindex RAMDirectory in a java.util.HashMap called
ramIndexes.
_______________________________________________ tc-users mailing list tc-users@... http://lists.terracotta.org/mailman/listinfo/tc-users |
|
|
Re: Compass, Lucene and Grails Searchable Plugin
by Mike Brevoort
::
Rate this Message:
|
| Free embeddable forum powered by Nabble | Forum Help |
