Re: [infinispan-dev] QueryIterator inconsistencies
Ales,
+1 for removing it all: your vote is valuable as our most interesting user.
@Manik, I think rewriting CacheQuery is a much bigger change as I'd
expect most people to use the simpler
org.infinispan.query.CacheQuery.list() output.
Also if we deprecate the old methods, we'll need to implement them
correctly for clustered queries as well which is a massive amount of
work, not worth it since we agreed the API is useless in its current
form.
@Luksa you seem to have a solid understanding of what need to be
done.. do whatever you need to make this API make sense.
Iterable<Object> looks like the contract to go.
@Emmanuel great point, I was about screwing projections up again :-)
Cheers,
Sanne
On 26 September 2012 14:49, Ales Justin <ales.justin(a)gmail.com> wrote:
Can we please get a decision on this,
so we try to get something *workable* into next 5.2. release?
-Ales
p.s. since it looks like nobody is using this, apart from CapeDwarf,
my vote goes into replacing/removing the methods
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev