There is an additional complex choice to make.
Considering that Infinispan has this separate notion of Key vs Value, and
both have to contribute to building the final indexed Document, why is it
that we allow the decision of which index is being targeted to be made by
*the type of the value*?
I t
On 7 August 2014 22:37, Hardy Ferentschik wrote:
>
> On 7 Jan 2014, at 19:56, Sanne Grinovero wrote:
>
> > I was hoping to drop @ProvidedId today as the original "marker"
> > functionality is no longer needed: since we have
> >
> > org.hibernate.search.cfg.spi.SearchConfiguration.isIdProvidedIm
On 08/07/2014 01:12 PM, Steve Ebersole wrote:
> We only check whether the thread is different from the "application
> thread". As I have mentioned to you about a bazillion times now (give
> or take ;) this is all a best effort. As you well know, we simply do
> not have all the pertinent informati
There are two annotations clashing for same responsibilities:
- org.infinispan.query.Transformable
- org.hibernate.search.annotations.ProvidedId
as documented at the following link, these two different ways to apply "Id
indexing options" in Infinispan Query, IMHO quite unclear when a user
should
We only check whether the thread is different from the "application
thread". As I have mentioned to you about a bazillion times now (give or
take ;) this is all a best effort. As you well know, we simply do not have
all the pertinent information we need to know what the nature of the
various thre
Don't y'all believe in summarization? ;)
I'll read through this tonight/tomorrow...
On Thu, Aug 7, 2014 at 10:02 AM, Sanne Grinovero
wrote:
> Steve,
> we had a conversation about this on IRC, I think we came to a
> hopefully
> nice
>
> solution
> .
>
> [15:18] andrigtmiller: I still thi
Also, detecting that the background thread may of violated the Hibernate
session concurrency requirements for only one thread to use it at a
time, is not as good as preventing the concurrency violation.
If anyone wants to also give feedback on the Transaction Manager side of
this, the forum thr
Sanne,
One question that I didn't ask before, when the Hibernate
Synchronization.afterCompletion(int) is called (with rolledback TX
status), how does Hibernate know if the transaction was rolled back from
the transaction reaper thread? I tried checking the thread name in
WildFly integration c
Hi,
every now and then I run into usages of raw types in our code bases:
* Class entityType (instead of Class)
* Set querySpaces (instead of Set)
...
I first thought that'd be left-overs from ancient times but apparently this
is also done in newly written code. I don't like it as in some cases i
Steve,
we had a conversation about this on IRC, I think we came to a
hopefully
nice
solution
.
[15:18] andrigtmiller: I still think you're locking out
the TXM, not making it possible to legitimately timeout queries..
[15:19] (but I don't have the full picture.. not really my
area)
[15:19]
Hi Emmanuel et al.,
My apologies for the log radio silence. I've taken a look at the code-base
on Jon Halliday's repo, and have set up a nick on freenode - #jlesinge.
On the time-series question I was wondering how you envisaged the data
stored: I tend to think of a single row under an primary ke
11 matches
Mail list logo
