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
- map indexing and purge to the interceptor - I don't think we can safel
On 11 May 2012 17:15, Hardy Ferentschik wrote:
>
> On May 11, 2012, at 6:07 PM, Sanne Grinovero wrote:
>
>> I was expecting you to argue about it,
>
> :-)
>
>
>> and therefore I concede that
>> some docs clarification at least is strongly required,
>
> at the very least
no doubt
>
>> but I disag
On May 11, 2012, at 6:07 PM, Sanne Grinovero wrote:
> I was expecting you to argue about it,
:-)
> and therefore I concede that
> some docs clarification at least is strongly required,
at the very least
> but I disagree on the expectations:
>
> I see a fundamental difference in behaviour ex
I was expecting you to argue about it, and therefore I concede that
some docs clarification at least is strongly required, but I disagree
on the expectations:
I see a fundamental difference in behaviour expectations between
a) "sync up database and index"
b) "index Entries A and B now"
In the f
Really? I would argue differently.
Let's take the blog example where I only want to index blog entries which are
published. Adding the interceptor and relying on automatic indexing will not
index un-published entries. Great.
If I, however, want/ have to re-index my blog entries via the API the
On May 11, 2012, at 9:31 AM, Gunnar Morling wrote:
> > What do you think about pushing this to master. As we develop the missing
> > features we just
> > re-enable things.
>
> So far we've always developed new features on individual branches (within our
> forked repos) and had them pulled into
There, back and again ...
After fixing a bug in grid search here are some updated results on 2k calls
Degrees :
Mean time with Grid : 4.4897266425641025 ms. Average number of docs
fetched : 2506.96
Mean time with Grid + Distance filter : 6.4930799487179485 ms. Average
number of docs fetched : 4
Am 10.05.2012 15:01 schrieb "Hardy Ferentschik" :
>
>
> > nice post on the release, this should get started everyone with 4.3.
> > And we can finally focus on HV 5 :)
>
> thanks :-)
>
> >
> >>> I'm looking forward to implementing the new API, this should be
> >>> fun :) I feel that it should be pos
On May 11, 2012, at 1:09, Scott Marlow 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. :-)
>
> It sounds like adding value="
