Hi Petar,
willing to experiment with it is awesome, but I'm skeptical on that project.
The benchmark I've found on the JCS site is not measuring what
matters; for example the put an get operations are sequential and not
multithreaded, so we have no clue about how it can handle contention
or even s
Hi all,
Hibernate Search version 5.0.0.Alpha6 is now available.
I'm skipping the blog post this time as the only significant change
for users is about fixing the Avro based serializer [HSEARCH-1637],
which we had recently broken during 5.0 related refactorings.
We also made it possible to seriali
Hello,
TL;DR: Need an opinion if to open a JIRA (since reproduction is very tricky)
I am using the @UnwrapValidatedValue with a custom Guava OptionalUnwrapper and
sometimes OptionalUnwrapper#getValidatedValueType() is called also for
non-Optional<> fields.
The bug reproduction is sporadic an
Thanks Guillaume!
your patch is merged, I'll look forward for more feedback from your team now :)
Sanne
On 20 August 2014 23:30, Guillaume Smet wrote:
> On Fri, Jul 25, 2014 at 9:59 PM, Guillaume Smet
> wrote:
>> Thanks for your feedback. I'll see what I can do next week about it.
>
> A little
Hi,
2014-08-21 12:38 GMT+02:00 Itai Frenkel :
> Hello,
>
> TL;DR: Need an opinion if to open a JIRA (since reproduction is very
> tricky)
>
>
> I am using the @UnwrapValidatedValue with a custom Guava OptionalUnwrapper
> and sometimes OptionalUnwrapper#getValidatedValueType() is called also for
>
I do like you do. But I can see why some fall back to the raw type as
it's less "annoying" when developing.
On Thu 2014-08-07 17:26, Gunnar Morling wrote:
> Hi,
>
> every now and then I run into usages of raw types in our code bases:
>
> * Class entityType (instead of Class)
> * Set querySpaces
I basically tl;dr; the whole thread for the obvious reason that it is
too long :)
But skimming through it made me think of the following.
Would it make sense to index Map.Entry with @IndexedEmbedded
or @FieldBridge on Map.Entry.getKey() / Map.Entry.getValue()?
At a conceptual level at least.
One m
First some context, we have issues open such as :
= HSEARCH-1656 - Recognize annotations from implemented interfaces
= HSEARCH-249 - Inheritance of annotations
= HSEARCH-1231 - Discuss if @Indexed annotation should not be
inherited by default
I've always felt it odd that we would ignore subty
Awesome write up. I will for sure steal a lot of it :)
A few random comments:
- once we are sufficiently happy, we probably should move this to the website
- you mention backward compatibility and leave aside source vs binary
backward compatibility. Do we want to dive on this subject? The later
The biggies that I think should be in 5.0 are:
- free form entity: it opens up a lot of interesting doors closed to us
at the moment
- bridges providing metadata feedback for better optimizations (like
which field they store stuff to)
Both have a risk of API breakage hence the idea of working
Agreed, but on free-form as soon as we're advanced enough to know the
API is solid it should not delay further.
Not saying we're there yet though, so we can decide on such matters
when we agree on its stability and risks.
Sanne
On 21 August 2014 15:42, Emmanuel Bernard wrote:
> The biggies that
On Thu, Aug 21, 2014 at 1:04 PM, Sanne Grinovero wrote:
> your patch is merged, I'll look forward for more feedback from your team now
> :)
Thanks. Too bad I missed the alpha6 train...
We'll try to move our apps to the next alpha (or beta) and see how it
goes (not a big fan of having snapshots
I am really really not in favor of handling annotations from interfaces.
As you hints, it creates a *massively complex* set of rules on
overridability and inconsistent usages.
We might be able to solve them but how many months of work for what
reward? I'd rather implement free-form entity and leave
On Thu 2014-08-21 15:46, Sanne Grinovero wrote:
> Agreed, but on free-form as soon as we're advanced enough to know the
> API is solid it should not delay further.
/me rolling on the floor
I want it NOW
___
hibernate-dev mailing list
hibernate-dev@li
Hi Marc,
the QueryTimeJoin is indeed very interesting but since the user needs
to mark the "join point" somehow I hope we'll be able to build it as a
new feature (probably with its own new annotation) in some 5.next ?
At this point you seem you have more experience with it, so please
correct me if
On 21 August 2014 16:03, Emmanuel Bernard wrote:
> I am really really not in favor of handling annotations from interfaces.
> As you hints, it creates a *massively complex* set of rules on
> overridability and inconsistent usages.
> We might be able to solve them but how many months of work for wh
On 21 August 2014 15:55, Guillaume Smet wrote:
> On Thu, Aug 21, 2014 at 1:04 PM, Sanne Grinovero wrote:
>> your patch is merged, I'll look forward for more feedback from your team now
>> :)
>
> Thanks. Too bad I missed the alpha6 train...
>
> We'll try to move our apps to the next alpha (or bet
On Aug 21, 2014 12:08 PM, "Sanne Grinovero" wrote:
> Hi Marc,
> the QueryTimeJoin is indeed very interesting but since the user needs
> to mark the "join point" somehow I hope we'll be able to build it as a
> new feature (probably with its own new annotation) in some 5.next ?
>
QueryTimeJoin does
On 21 Aug 2014, at 17:26, Sanne Grinovero wrote:
>> In short, not to annotations on interfaces.
>> Neutral on indexing subclasses with the understanding that we are doing
>> it as best effort but that will remain flaky. The ability to index the
>> @IndexedEmbedded actual type instead of the stat
Please apologize me to reply to this discussion although I am not a
hibernate-developer.
I created issue "HSEARCH-1656", because I have some entities at
different points in my entity hierarchy (thus with different
super-classes), but all those entities (and only those) should be
indexed by hiberna
Hi,
Just a heads up: I'm going to propose an internship this year (scholar
year more precisely) on Hibernate Search contribution.
I'm not sure I'll find the good intern for this but that's the plan.
The internship season usually starts in Feb/March in France so it's
for early next year.
The inte
21 matches
Mail list logo
