I think that the failure is caused by HHH-7898 fix. The put is executed
only after the current transaction is finished (as synchronization),
until then the query is cached only for the current session and
therefore not reflected in statistics.
Radim
On 07/29/2015 09:02 PM, Scott Marlow wrote:
Hi Sanne,
Good idea. I'm not sure exactly what about the test is failing. ORM
currently doesn't have all of the same components as WildFly, so tests
don't always translate (e.g. ORM doesn't have a EJB container). We need
to understand the cause and then maybe we can talk about an ORM test.
S
Hi Scott,
do you think you could merge those tests in Hibernate ORM?
Thanks,
Sanne
On 29 July 2015 at 20:02, Scott Marlow wrote:
> I missed a WildFly second level query cache failure yesterday in my
> testing http://pastebin.com/kg3YhxxL
>
> Test steps:
>
> - creates an entity
>
> - queries
I missed a WildFly second level query cache failure yesterday in my
testing http://pastebin.com/kg3YhxxL
Test steps:
- creates an entity
- queries for the entity
- verify that the query cache hit count is zero.
- query again for the entity
- verify that the query cache hit count is
Thanks Steve,
just tested Hibernate Search with it and it's all working fine.
On 29 July 2015 at 16:37, Steve Ebersole wrote:
> The release is done minus announcing and SF upload. Also I decided to not
> upload the docs yet since they are still incomplete and i still have work
> to do there prio
The release is done minus announcing and SF upload. Also I decided to not
upload the docs yet since they are still incomplete and i still have work
to do there prior to Final.
On Wed, Jul 29, 2015 at 10:06 AM Steve Ebersole wrote:
> per $subject
>
__
per $subject
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
You might remember that running a full-text Query on a field always
required some specific care;
since the beginning of Hibernate Search the user had to make sure the
field was not tokenized, or tokenized but generating a single token.
This was a "soft requirement": if you didn't know, you'd get
i
On 29 July 2015 at 11:12, Gunnar Morling wrote:
>
>
> 2015-07-28 16:07 GMT+02:00 Sanne Grinovero :
>>
>> Hi all,
>> with Infinispan in embedded mode we used AtomicMaps and
>> FineGrainedAtomicMaps as an alternative way to map attributes and
>> relations.
>>
>> In particular the relations are inter
2015-07-28 16:07 GMT+02:00 Sanne Grinovero :
> Hi all,
> with Infinispan in embedded mode we used AtomicMaps and
> FineGrainedAtomicMaps as an alternative way to map attributes and
> relations.
>
> In particular the relations are interesting because in SQL world one
> would run a query on junction
On 29 July 2015 at 10:35, Davide D'Alto wrote:
>> I think that in the case of Hot Rod clients we should not use
>> AtomicMaps
>
> Out of curiosity, what about the grouping API?
> We asked the Infinispan team to add some methods to it because we might use
> them
> to implement the dialect over HotR
> I think that in the case of Hot Rod clients we should not use
> AtomicMaps
Out of curiosity, what about the grouping API?
We asked the Infinispan team to add some methods to it because we might use
them
to implement the dialect over HotRod. These methods are still missing in
the HotRod protocol,
12 matches
Mail list logo
