On Wed, Oct 2, 2013 at 12:48 PM, Pedro Ruivo pe...@infinispan.org wrote:
On 10/02/2013 12:03 AM, Sanne Grinovero wrote:
I'd love to brainstorm about the clear() operation and what it means
on Infinispan.
I'm not sure to what extent, but it seems that clear() is designed to
work in a
On 3 October 2013 10:29, Dan Berindei dan.berin...@gmail.com wrote:
On Wed, Oct 2, 2013 at 12:48 PM, Pedro Ruivo pe...@infinispan.org wrote:
On 10/02/2013 12:03 AM, Sanne Grinovero wrote:
I'd love to brainstorm about the clear() operation and what it means
on Infinispan.
I'm not sure
I would suggest renaming the old one :))
On 10/02/2013 11:13 PM, Sanne Grinovero wrote:
It seems we have now 2 different interfaces both names QueryBuilder
when using Infinispan Query.
One is coming from Hibernate Search, and represents the classic way
to build queries for Infinispan Query in
It's already productized code.
On Thu 2013-10-03 14:16, Adrian Nistor wrote:
I would suggest renaming the old one :))
On 10/02/2013 11:13 PM, Sanne Grinovero wrote:
It seems we have now 2 different interfaces both names QueryBuilder
when using Infinispan Query.
One is coming from
I know, was just joking. Anyway, I don't see any confusion having two
classes with the same name.
On 10/03/2013 02:29 PM, Emmanuel Bernard wrote:
It's already productized code.
On Thu 2013-10-03 14:16, Adrian Nistor wrote:
I would suggest renaming the old one :))
On 10/02/2013 11:13 PM,
On 3 October 2013 14:10, Adrian Nistor anis...@redhat.com wrote:
I know, was just joking. Anyway, I don't see any confusion having two
classes with the same name.
It's going to be hard enough to explain to people why we are providing
two different approaches, if we can't even think of a
Hi,
just a heads up that I've been moving some APIs around from
org.infinispan.query:
https://github.com/infinispan/infinispan/pull/2131
In particular I think that CapeDwarf is using some methods from
org.infinispan.query.SearchManager
which are no longer exposed; the fix is simple, cast any
Hello,
I just tried to undust an old test I had shelved. When I run it I got
an exception about the configuration having an unexpected header:
infinispan
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=urn:infinispan:config:5.2
You need the 52x compatibility jar.
Tristan
On 10/03/2013 06:53 PM, Sanne Grinovero wrote:
Hello,
I just tried to undust an old test I had shelved. When I run it I got
an exception about the configuration having an unexpected header:
infinispan
Ok, as long as it's expected I guess it's fine.
Thanks!
Sanne
On 3 October 2013 18:32, Tristan Tarrant ttarr...@redhat.com wrote:
You need the 52x compatibility jar.
Tristan
On 10/03/2013 06:53 PM, Sanne Grinovero wrote:
Hello,
I just tried to undust an old test I had shelved. When I run
Ok, noted.
-Ales
On Oct 3, 2013, at 17:44, Sanne Grinovero sa...@infinispan.org wrote:
Hi,
just a heads up that I've been moving some APIs around from
org.infinispan.query:
https://github.com/infinispan/infinispan/pull/2131
In particular I think that CapeDwarf is using some methods
Currently if a cache is configured with indexing enabled, but the
Query module isn't on classpath, you get a simple warning.
I think this should fail with a configuration validation error; it's
not just safer but also consistent with many other validations.
I've created ISPN-3583 and patch is
12 matches
Mail list logo
