> Since the filter is user defined, based on the fact that the user
> *knows* the blog needs to be indexed only when [businessrule],
> it's not hard to adapt the code using an
>
> if [businessrule] {
> fulltextSession#index( e );
> }
> else {
> log.discardBlogDRAFTFromIndex( e );
> }
Not hard,
On May 11, 2012, at 20:22, Emmanuel Bernard wrote:
> The reason I did map manual indexing to apply default is that I sided with
> Sanne s reasoning and I went on the side of caution with the API. I'd love to
> get more practical feedback before deciding to either:
>
> - stay as it is
> - m
On 10 mai 2012, at 08:49, Guillaume Smet wrote:
> Hi Search team,
>
> I have this question for a long time but, this time, having 30 (and
> growing) indexed entities inheriting from an abstract class, I thought
> I might as well ask about it...
>
> Is there any reason why we can't set the @Inde
On Sat, May 12, 2012 at 10:51 AM, Emmanuel Bernard
wrote:
> That would go counter to the JPA design I think and to be honest, I like the
> idea of being able to not index a given branch of a class hierarchy.
> But more importantly, you would require Hibernate Search to scan for all
> subclasses
>> Scratch your own :) itch https://hibernate.onjira.com/browse/HSEARCH-703
>> This is an issue that has been opened for a while but not addressed by like
>> of motivated contributors. The solution is fairly simple at first sight.
>
> Fair enough. I'll give it a try in the next few days.
Now th
On 11 mai 2012, at 00:11, Andrej Golovnin wrote:
> After updating JBoss 7 to use the Hibernate Validator 4.3.0 and
> adding
> to our persistence.xml file I was able to reduce memory consumption
> of SerializableValidatorFactory from ca. 90MB to ca. 256KB. :-)
> What I was not able to do, is to a
On 12 mai 2012, at 12:28, Hardy Ferentschik wrote:
>
>>> Scratch your own :) itch https://hibernate.onjira.com/browse/HSEARCH-703
>>> This is an issue that has been opened for a while but not addressed by like
>>> of motivated contributors. The solution is fairly simple at first sight.
>>
>> F
On 12 mai 2012, at 11:12, Guillaume Smet wrote:
>> That would go counter to the JPA design I think and to be honest, I like the
>> idea of being able to not index a given branch of a class hierarchy.
>> But more importantly, you would require Hibernate Search to scan for all
>> subclasses in th
Hi Scott,
> It sounds like adding value="NONE"/>, is responsible for the memory savings, more than using
> Hibernate Validator 4.3.0. If not, it would be helpful for us to know that.
>
> I wouldn't expect much more savings than that (with validation mode set to
> NONE, we won't pass a validat
Hi Hardy,
> Right, in this case validation mode NONE is the determining factor. I would
> think you get the same result w/ Validator 4.2.0.
Nope, it was the Validator 4.3.0.
> application or as part of the container startup?
> And what exactly do you mean w/ Hibernate Validator gets loaded? D
Hi Emmanuel,
> Andrej, I wonder if you could share with us these memory dumps privately so
> we could also analyze them.
I'm sorry but this is not possible. But I will give my best to find the root
cause
of this problem.
Here are my findings so far:
- In the memory dump with Hibernate 4 there
11 matches
Mail list logo