What is the reason for Hibernate to consider a lazy association (proxy)
as part of the lazy property fetch group?
This has some side effects like initializing the lazy properties when a
many to one association is accessed.
___
hibernate-dev mailing
I confirm what I said. I added a testcase to HEM.
Here is the most accurate thing I can find from the spec
3.4.2 Version Attributes
[...]
The persistence provider's implementation of the merge operation must
examine the version attribute
when an entity is being merged and throw an
collection, and sends
that back to the user.
Seems counter-productive.
Thanks,
Josh.
Emmanuel Bernard wrote:
This is consistent with the way saveOrUpdate works
Josh Moore wrote:
Using Hibernate with non-updatable fields can leave entities in a
confused state.
Take an Image with a field
In xml to set up a filter on the target table of a many to many, you set
the filter element inside the many-to-many element
To support that in annotations, I could do
1.
@Filter (pointing to the association table or the target table if a
@OneToMany @JoinColumn)
@FilterManyToMany
:
On Sep 28, 2006, at 8:51 PM, Emmanuel Bernard wrote:
@Filter (pointing to the target table)
@FilterJoinTable (pointing to the association table)
I like 2. better, it is more consistent esp when you realize that
@OneToMany can use a join table just by changing an annotation.
2. would require a break
Hibernate Annotations and Hibernate entity manager 3.2.0.CR3 have been
released and are compatible with Hibernate Core 3.2.0.CR5.
We decided another CR was needed mainly for two fixes:
1) A fix for the JPA persist on flush event;
2) performance improvement in regards to flush processing.
This
Lucene, y a t il quelque chose de
prévu
?
-Message d'origine-
De : Emmanuel Bernard [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 13 octobre 2006 16:00
À : Richard Hallier
Objet : Re: Hibernate Lucene fields
je parlais des Bridges pour toutes les propriétés
Richard
Branch, you did good.
Thanks
Max Rydahl Andersen wrote:
Hi Emmanuel,
Is it the branch or trunk you wanted fixes/changes or do i just need to
apply this make stuff compile fix to both branches ?
/max
--- Forwarded message ---
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc:
yes, open a JIRA issue please
andresgr wrote:
Hi.
In Section 14.15. Tips Tricks:
You can count the number of query results without actually returning
them:
( (Integer) session.iterate(select count(*) from ).next()
).intValue()
I don't find any session.iterate() method... Maybe it
positive ratio, so jumping on JIRA is not a
good thing to do.
Emmanuel
andresgr wrote:
Done.
By the way, should i use JIRA directly to report issues? Or may i post
here a message to get something like yes, that's a bug. Open JIRA
issue. like in this case...
Regards
2006/10/31, Emmanuel Bernard
Hi all,
I have had time to work on Hibernate Lucene recently and finished the
work I wanted to do. This is a major rework and will bring both API and
index breaks, but for the good. This implements the core ideas that
were floating around for a while.
What's new
o Index querying
Keeping the
Hi again,
Here are some ideas I have in mind for Hibernate Lucene
o User feedback
First and most important, I need and will use user feedback on the
changes: Usability, Use case coverage, etc
I know our model work well for non complex querying requirement, I would
like to see it evolving to
No, no.
Please use the user forum: http://forum.hibernate.org
Reza Razavipour wrote:
To all,
total newbie to Hibernate. Does hibernate have any limitations running
against KDK 1.4 and JRE 1.4? If so, is there a version that does?
Thanks
Reza
I want to rename @Indexed to @FullText to mark a class as searchable
The name is more appropriate to the context and less generic
@Entity
@FullText(index=commerce)
public class Order {
Anybody against or with a better name?
___
hibernate-dev mailing
I don't mean HibernateExt/**/build.sh, I mean HibernateExt/build.sh
Christian Bauer wrote:
On Nov 8, 2006, at 4:49 PM, Emmanuel Bernard wrote:
Can we get rid of those files, people get confused and they are
outdated.
Not if the Ant clowns still bundle the plugin JARs in their
distribution
The spec and the TCK mandate the way I did it.
Woelke, Milan wrote:
Hi,
I was looking over the code of the ejb3 entitymanager (abstractentitymanager) and I was wondering about one thing:
Most of the methods defined by the entitymanager interface specification are implemented there with a try
I'm looking at ANN-422
In HA, the target is usually inferred from the API (generics), and can
be overridden in all associations through targetEntity (
@ManyToOne(targetEntity...) )
currently, you cannot override the target for a component, nor you can
override it for a map-key-many-to-many/
andresgr wrote:
Hi.
I can see in Hibernate 3.2 LockMode.NEVER is deprecated in favor of
LockMode.MANUAL.
Maybe this is a silly argument... but i think that FlushMode.NEVER has
some semantic benefits. I mean, if i'm reading code and see
session.setFlushMode(FlushMode.NEVER)
i think oh,
Recently I've been working on Hibernate Search clustering.
Hibernate Search will have the ability to work in a master / slave mode.
Every node has a local copy of the index and can read it (ie query it).
When an update is required (actually when a transaction scoped list of
updates are
Max Rydahl Andersen wrote:
Recently I've been working on Hibernate Search clustering.
Hibernate Search will have the ability to work in a master / slave mode.
Every node has a local copy of the index and can read it (ie query it).
When an update is required (actually when a transaction
Apparently, there is an hibernate-announce mailing list whose traffic is
approx 1 mail per month. I wasn't aware of it so I never pushed any
info, neither Max. As a matter of fact, only Steve uses it. Should we
keep it?
I'd rather see a script reusing the first post of every Announce we do
on
With the help of Paolo on commons-annotations refactoring, I came up
with a decent prototype, here is the structure
jpa-api
lib (empty)
compile depends on nothing
compiletest depends on nothing
commons-annotations
lib (empty)
compile depends on commons logging, log4j
compiletest
yes
round 10 lines of ant script in your build.xml file. here is my
comment on that
!-- To add a dependency:
defines the dependency.jar property that points to the expected
jar file
in init, add an available dependency.jar and populate
dependency.jar.available
create a target
It actually works perfectly with ant. IntelliJ works nice to with
cross module dependency. Doesn't eclipse support cross module
dependencies?
On 15 févr. 07, at 06:33, Max Rydahl Andersen wrote:
validator
lib (empty)
compile depends on jpa-api, commons-annotations, core
On 15 févr. 07, at 09:47, Max Rydahl Andersen wrote:
It actually works perfectly with ant.
Well sure - here you don't specify the project dependencies. You
specify the dependencies
for each compile.
IntelliJ works nice to with cross module dependency. Doesn't
eclipse support cross
I don't think it should be applied to all properties, but the one
referred are worth it.
On 26 févr. 07, at 18:21, Max Rydahl Andersen wrote:
Hi,
I've bumped into an issue with trying to override settings/
properties in tools too allow users to use
their existing config minus the appserver
Hibernate EntityManager 3.3.1.GA has been released. It fixes two
minor bugs introduced in 3.3.0.GA:
* [EJB-281] - Version 3.3.0 is not compatible with JBoss AS 4.0.5
* [EJB-282] - ORM.xml ignored when excludeUnlistedClass = true
in container mode (EJB 3.0, Spring)
This version is a
I have been adding new features on Hibernate Search recently (SVN)
Projection
The ability to project some fields the index only avoiding the
database roundtrip.
fullTextQuery.setProjection(id, summary, author.name).list();
will return a ListObject[] like the regular HQL projection
the
Projection
The ability to project some fields the index only avoiding the
database roundtrip.
fullTextQuery.setProjection(id, summary, author.name).list();
will return a ListObject[] like the regular HQL projection
the fieldbridge has to be two way (all built-in are) and the
projected fields
For Hibernate Search I came to a problem.
When a user choose field access.
When I access a previously uninitialized object, and even if I
initialize it (Hibernate.initialize()).
The field access End up returning null all the time because of the
way lazy loading is done. I worked around that
I know that Max :)
I do not expose it to the user, it's just how HSearch internally deal
with it during the transparent indexation process, so I do not break
the == operation from a user point of view. Note that we expose that
to the user anyway through load/initialize/get, I'm just begging
This is what I want to return one way or an other... or CGLIB should
fill up the superclass fields.
On 24 mai 07, at 01:02, Max Rydahl Andersen wrote:
afaik ( ( HibernateProxy ) value ).getHibernateLazyInitializer
().getImplementation() haven't changed almost since beginning of
times.
Aleksei Valikov took the responsibility for Hibernate EntityManager.
Open a JIRa issue, assign it to him and ask him if he is willing to.
On 25 mai 07, at 09:28, Steve Ebersole wrote:
Not I...
On Fri, 2007-05-25 at 10:46 +0100, Donnchadh Ó Donnabháin wrote:
On 5/18/07, Steve Ebersole [EMAIL
For Hibernate Search, I did introduce the IndexReaders caching.
My tests shows for:
- a search intensive application,
- low update ratio
- in-memory database
- filesystem based index
a speed increase of 25 to 30%.
It is not the default yet (use 'hibernate.search.reader.strategy
shared' to
JPA today mandates that clients access getters and setters.
On 28 mai 07, at 05:37, Max Rydahl Andersen wrote:
Field field = myClass.getField(myField);
Object value = field.get(proxy);
value is always null because CGLIB does not fill the superclass
fields.
well - it shouldn't and you
On 2 juin 07, at 08:25, Hardy Ferentschik wrote:
- Indexing process
What about exposing lucene indexing paramters like mergeFactor,
maxMergeDocs and minMergeDocs? You could allow the
user to add these parameters to the hibernate configuration file
and then pick them up within the
Thanks to both of you,
It's done for existing files.
If someone known how to tell IntelliJ to set a property on newly
added *.java or even better set that at the SVN server level, let me
know.
On 2 juin 07, at 13:21, John Griffin wrote:
Emmanuel,
Assuming that ‘list.txt’ is the file
I am not a big fan of the on-the-fly changes for merge factor and co
But I agree with John, there should be 2 sets of values, one for the
regular transactional indexing, and one for session.index() (we might
have to adjust the clustering message to pass the type of operation
along).
Hibernate Search 3.0.0 Beta3 has been released. It primarily fix a
severe bug introduced in beta2 (HSEARCH-66).
Besides bug fixes, this release brings some new features:
- Lucene index optimization (searchFactory.optimize())
- configurable batch size limit for indexing (drastically
Hi Hardy
I would recommend to get Hibernate3 from the branch_3_2 (ie ant),
HAN / HEM / HSearch being aligned with Hibernate Core 3.2
Check http://www.hibernate.org/30.html#A6 for some more info, I've
updated it slightly.
On 10 juin 07, at 17:40, [EMAIL PROTECTED] wrote:
Hi there,
I am
. Such a structure would be serializable.
Let's see how it goes.
On 11 juin 07, at 23:46, John Griffin wrote:
-Original Message-
From: Emmanuel Bernard [mailto:[EMAIL PROTECTED]
Sent: Monday, June 11, 2007 10:06 AM
To: John Griffin
Cc: hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev
Hum interesting,
Which test fails exactly?
I just jave to replace the getBody annotation?
On 12 juin 07, at 17:12, Hardy Ferentschik wrote:
Hi Emmanuel,
I was just looking at http://opensource.atlassian.com/projects/
hibernate/browse/HSEARCH-15. I attached a very simple addition to
PROTECTED]
When replying, please edit your Subject line so it is more specific
than Re: Contents of hibernate-dev digest...
Today's Topics:
1. Re: hsearch-6 serializable Hits object (Emmanuel Bernard)
2. Hibernate + Oracle RDB 7.1 (Rehnman Martin)
3. hibernate-hsqldb-testsuite build.57
This is correct, but Christian had a very interesting idea.
We could reuse the projection API to project the Lucene specific objects
fullTextQuery.setProjection(id, title, price,
FullTextQuery.DOCUMENT, FullTextQuery.SCORE).list();
Would return a list of
Object[] {
1, //the id
Au bonheur
I introduced the OptimizerStrategy concept: the current
implementation triggers optimize() every nth operations or mth
transactions. But it can be extended as needed.
I have also defined the road map for 3.0.0.beta4
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH?
When possible and easy I abstracted my work from the Lucene APIs. But
clearly there will be some work and coding to make it work on top of
anther search engine.
So out of the box, no, you can't use it with another search engine.
On Jun 26, 2007, at 07:23, Saphia Thach wrote:
Hi Guys,
The idea was that instead of loading objects one by one, you would
trigger the load of n object (preemptively)
So scrollableResults.get() would either:
- extract the n following docs and load the n following objects and
cache n-1 of them
- read the data from the already preemptively loaded
Hibernate Search has a new beta out and comes with a bunch of
interesting new features:
- Named filters: query result filter (transparently cacheable)
- Automatic index optimization
- Access to query metadata (Score, ...)
- Support for the Java Persistence API
- Index sharding (indexing an
I wil be performing the SVN migration tomorrow for those projects.
Please refrain from commiting code in them until it's finished
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
663 commits later the migration to the new structure is done. All
projects are top level:
core (Branch_3_2)
jpa-api
commons-annotations
annotations
entitymanager
validator
search
tags have been migrated and normalized (ie HibernateExt is out), I
had to keep Branch_3_2 as is because of the
I don't understand, do you mean a bundled hibernate-core jar? I'm
still depending on Hibernate core 3.2, not the latest maven work.
On Aug 11, 2007, at 04:46, Max Rydahl Andersen wrote:
Excellentand even more important; evil cyclic dependencies
are...well...evil! ;)
So the unit
You should not need to have access, I think.
Workers from the WorkerFactory take entity and work type. All of them
are stored by the BatchedQueueingProcessor
Then before tx commit, QueueingProcessor.prepareWorks prepare the
queue and create Lucene specific works (queue of LuceneWork).
after
On Aug 16, 2007, at 02:39, Hardy Ferentschik wrote:
Great work!
This was a big step forward in making the whole code base easier to
understand and maintain. It will also make a maven migration much
easier :)
That was the plan, part of it at least :)
I checked out Hibernare Search
I'm assuming you are looking fo the purge(Class) operation.
Feel free to add a work.getEntityClass() method that returns what you
want (ie does Hibernate..getClass( entity ) for regular works and
return the entityClass for a PURGE_ALL work type).
On Aug 17, 2007, at 20:38, John Griffin
Just a few reminders to make people's life easier.
When providing a patch, please refrain from applying style changes
(including imports), this is a hell of a pain to know what has
changed for real.
When committing a fix for a a given issue, do the same, refrain from
style fixes, also
Hibernate Search 3.0.0.CR1 is now out. This release is mainly the
last bits of new features and polishing before the final version. The
next cycle will be dedicated to bug fixes (of any bug that pops up),
as well as test suite and documentation improvements.
Thanks to Hardy for the new
Hibernate Search 3.0 went final this week end
The Hibernate Search team is pleased to announce version 3.0 final.
Hibernate Search provides full text search (google-like) capabilities
to Hibernate domain model objects. Based on Apache Lucene, Hibernate
Search focuses on ease of use and
AnnotationBinder is the class you're looking for.
@Column is used in several place, but it happens at runtime during
what is called the Annotationconfiguration.secondPassCompile() phase
(usually when you build the session factory).
On Nov 5, 2007, at 10:14, Julien Martin wrote:
Hello,
I
You need it for the post commit insert event.
But we could optimize that if there is no such event.
On Nov 9, 2007, at 21:21, Markus Heiden wrote:
After executing actions, the actions (e.g. EntityInsertAction) will
be moved from ActionQueue.inserts etc. to ActionQueue.executions to
stay
You're missing one part, how about custom event listeners. Hibernate
Search used to use those events and needed the entity instances for
example.
For the optimization, the JIRA issue has not been created AFAIK.
On Nov 11, 2007, at 17:00, Markus Heiden wrote:
Hi Emmanuel,
You need it for
:[EMAIL PROTECTED] On Behalf Of Emmanuel
Bernard
Sent: Sunday, November 11, 2007 5:29 PM
To: Markus Heiden
Cc: hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Memory consumption
You're missing one part, how about custom event listeners. Hibernate
Search used to use those events and needed
is it specific to a given index or should rather be global for all
indexes?
If the latter, I would remove .default which is really here for index
based properties.
On Dec 1, 2007, at 14:23, John Griffin wrote:
I’m starting work on 133. I believe the class that overrides
DefaultSimilarity
]
When replying, please edit your Subject line so it is more specific
than Re: Contents of hibernate-dev digest...
Today's Topics:
1. HSearch-133 (John Griffin)
2. Re: HSearch-133 (Emmanuel Bernard)
--
Message: 1
Date: Sat, 1
Would that help
http://opensource.atlassian.com/projects/hibernate/browse/HV-22
a. can you expand your idea?
b. not sure why this is a problem, because you are not validating
property 'name', you're validation 'name' and 'age' alltogether,
hence there is no property name
On Dec 6, 2007,
Probably the best strategy is to think about it when we work on the
fetch profile strategy.
On Dec 12, 2007, at 03:02, Bill Burke wrote:
I was looking at the XML mapping support for Hibernate recently and
have some questions/suggestions.
One thing that seriously annoyed me was that if
Big -1 on forcing the user to supply the same similarity, We need to
keep a similarity per entity in the SearchFactory so that the query
can then retrieve it.
The reason I chose IndexReader (and Multireader) was because Searcher
is a much weaker abstraction, so you cannot do all the things
While not strictly useful for the comment feature, I want to add a
@ColumnOrFormula annotation to be able to support mixing formula and
columns in a user type (and a FK definition). Let's say it's a
lightly correlated feature.
On Jan 27, 2008, at 19:17, Oliver B. Fischer wrote:
Hello,
)
or
@DocComment (
@Column = Login of the user.
)
be easier for end users to use and to understand. I would prefer an
comment-only annotation.
Best Regards
Oliver
Emmanuel Bernard schrieb:
While not strictly useful for the comment feature, I want to add a
@ColumnOrFormula annotation to be able
But I agree, I would have used this style otherwise.
On Jan 30, 2008, at 12:42, Emmanuel Bernard wrote:
Does not work well for properties with multiple columns and
entities with multiple tables
On Jan 30, 2008, at 09:14, Oliver B. Fischer wrote:
Hello Emmanuel,
wouldn't an annotation
easier. Note that a small unit test would be cool
too :))
On Feb 8, 2008, at 17:52, Oliver B. Fischer wrote:
Hello,
can you give me an more detailed example of the annotation you
imagine?
Bye,
Oliver
Emmanuel Bernard schrieb:
Does not work well for properties with multiple columns
The right place for those questions is http://forum.hibernate.org
To answer your question, you have different DBs, so different
SessionFactory configurations (using the same mapping I imagine).
You will just have to change the following property in each
hibernate.cfg.xml
to prevent possible index corruptions!
--
--
Best regards,
Aleksander M. Stensby
On Sun, 24 Feb 2008 22:10:34 +0100, Emmanuel Bernard
[EMAIL PROTECTED] wrote:
I think Hibernate Search should go for 3.1 from now one in trunk
On Feb 26, 2008, at 06:41, Nick Vincent wrote:
2) Explaining results
This uses the new DOCUMENT_ID projection introduced in 3.0.1 to
explain query results (we need this so the customer can understand
their search results in the backoffice interface). I added an explain
method to both
On Feb 27, 2008, at 08:40, Nick Vincent wrote:
Hi Emmanuel,
On 26/02/2008, Emmanuel Bernard [EMAIL PROTECTED] wrote:
On Feb 26, 2008, at 06:41, Nick Vincent wrote:
2) Explaining results
This uses the new DOCUMENT_ID projection introduced in 3.0.1 to
explain query results (we need
Nice work
Can you open a JIRA issue for each point (forget #6 though, too much
work) and explain the reason for the need briefly?
Emmanuel
On Feb 26, 2008, at 14:10, Ali H. Ibrahim wrote:
Hi,
I have been working on an extension to Hibernate called Autofetch.
I ran
into some pain points
that requires a
lot of work. I mistakenly marked one of the issues as major when I
meant minor, but it seems I don't have permission to fix that.
Regards,
Ali
Emmanuel Bernard wrote:
Nice work
Can you open a JIRA issue for each point (forget #6 though, too
much work) and explain
I think there are 2 separate problems here.
You want wildcard resolution. I am not entirely sure why. Is it
because your custom FieldBridge create a lot of fields in the document?
How are the fields indexed exactly? Using @Field/@FieldBridge or
@ClassBridge
Both support the use of
I am in the middle of a fix-athlon for Hibernate Annotations and
Hibernate EntityManager.
If you think there are bug fixes (not enhancements) that should be
part of the upcoming releases, let me know in the next 2 days.
especially if (in decreased priority):
- the bug is important
- there
On Mar 17, 2008, at 12:14, Max Bowsher wrote:
Steve Ebersole wrote:
JBoss as a whole is working with the Maven team (Jason) about
setting up synching of all the projects we write to the JBoss repo (http://repository.jboss.org/maven2/
) automatically. Personally, it is not worth my time,
On Mar 18, 2008, at 15:00, Max Bowsher wrote:
HAN 3.3.1.GA
HEM 3.3.2.GA
HCA 3.3.0.GA
please open a JIRA issue, I'll make it better for the next releases.
My main problem is that I use ivy for my dependency management, so
I can't really test the exclusive maven chain.
Thanks. Those TLAs
Hey
The more I think about the feature, the less I like it.
Here is what I have written in Hibernate Search in Action
Hibernate Search, by default, does not store null attributes into the
index. Lucene does not have the notion of null fields, the field is
simply not there. Hibernate Search
One JIRA / patch is good
Self-conflict is not always bad When fight begins within himself, a
man's worth something. - Sir Frederick Browning :)
On Apr 27, 2008, at 08:03, Sanne Grinovero wrote:
I would like to address A and B first; may I
open a single JIRA for both? both issues are
I have been working in the past two days to make the build system, and
the projects compatible with the migration to Core 3.3:
- Hibernate Commons Annotations
- Hibernate Annotations
- Hibernate Validator
- Hibernate Search
- Hibernate EntityManager
Sorry I forgot Hibernate Shards, but I
Hibernate Search 3.1 will arrive sooner than expected to align with
Hibernate Core 3.3
If you have some compatibility breaks in mind, speak up. Also we need
to focus on closing the features implying Core 3.3 first (I have the
close hooks of the SF in mind but there might be others). The
On May 2, 2008, at 03:33, Hardy Ferentschik wrote:
Hi there,
On Fri, 02 May 2008 01:53:02 +0200, Emmanuel Bernard [EMAIL PROTECTED]
wrote:
Hibernate Search 3.1 will arrive sooner than expected to align with
Hibernate Core 3.3
Great. Seems a lot of things are finally happening
On May 2, 2008, at 14:34, Chris Bredesen wrote:
Hardy Ferentschik wrote:
On Fri, 02 May 2008 15:23:49 +0200, Emmanuel Bernard [EMAIL PROTECTED]
wrote:
latest means you local version in the build terminology I set up
so you need to checkout commons-annotations / annotations
My understanding is that we need to implement a
shardedfulltextsessionimpl delegating to fts. It makes more sense to
for shards to wrap other projets. It probably needs some refactoring
to avoid duplication
On May 11, 2008, at 9:08, Sanne Grinovero
[EMAIL PROTECTED] wrote:
Hi all,
The sync process in on someone's todo list at JBoss. But todo lists
are long these days.
On May 14, 2008, at 12:49, Tomislav Stojcevich wrote:
The jboss maven repo is not currently being sync'd to the central repo
for the org/hibernate packages.
I need the latest entitytManager which is
This is unfortunate.
These glitches were expected, and we will fix them as they pop up.
Though as Hardy said, the new HSearch build system is independent of
Hibernate Core. All the needed libraries are downloaded in build/lib/
core and build/lib/test
IM me if you need more help.
AFAIK JBoss
Any reason why we target SLF4J 1.4.2 and not 1.5?
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
thread ;)
I have no issue with upgrading as long as no issues are created by
that.
On May 15, 2008, at 5:30 PM, Emmanuel Bernard wrote:
Any reason why we target SLF4J 1.4.2 and not 1.5?
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
On May 29, 2008, at 08:59, Sanne Grinovero wrote:
Hi, I'll cut away the questions I don't need to ask more about.
2008/5/29 Emmanuel Bernard [EMAIL PROTECTED]:
Hi Sanne
On May 28, 2008, at 14:01, Sanne Grinovero wrote:
[...]
1)is it ok in case of a code revision to have a commit of 100
On Jun 2, 2008, at 19:26, Manik Surtani wrote:
* How can the SearchFactoryImpl class /lazily /update the document
builder map in that same class? Would you suggest a subclass ?? In
JBC I don't know before-hand as to what types are going to be
indexed, so this will have to be done
When a non @Indexed entity is passed to session.index or
session.purge, we simply ignore it (even if the superclass is indexed).
Should we raise an exception instead?
http://forum.hibernate.org/viewtopic.php?p=2384774#2384774
___
hibernate-dev
On Jun 4, 2008, at 18:06, Sanne Grinovero wrote:
Hello,
I need some suggestion to name new parameters in H.Search;
I'm implementing the parameter for FSMasterDirectoryProvider and
FSSlaveDirectoryProvider to select an appropriate chunk size:
the amount of bytes to have java.nio attempt to
This sounds very promising.
I don't quite understand why you talk about loading lazy objects though?
On of the recommendations is to load the object and all it's related
objects before indexing. No lazy triggering should happen.
eg from User u left join fetch u.address a left join fetch
On Jun 7, 2008, at 20:14, Sanne Grinovero wrote:
thanks for your insights :-)
I'll try explain myself better inline:
2008/6/7 Emmanuel Bernard [EMAIL PROTECTED]:
This sounds very promising.
I don't quite understand why you talk about loading lazy objects
though?
On of the recommendations
On Jun 7, 2008, at 11:32, Sanne Grinovero wrote:
Hi all,
I've been thinking on some more design changes for Hibernate Search,
I hope to start a creative discussion.
A)FSMasterDirectoryProvider and Index Snapshots.
is currently making copies of it's changing index; Using Lucene's
On Jun 12, 2008, at 06:00, Sanne Grinovero wrote:
Does it somehow involve not having cluster changes (ie intra VM
policy rather than inter VM?)
I don't really understand what you're asking; I hope previous
example contains an answer; it just means you don't need
to lock the index to
in your solution or in mine?
Sanne
2008/6/14 Emmanuel Bernard [EMAIL PROTECTED]:
I played around the idea of not loading unnecessary fields when
loading a Lucene document.
It turns out this is not easily possible
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-213
I would
1 - 100 of 1482 matches
Mail list logo
