Re: [infinispan-dev] Query.getResultSize() to be available on the simplified DSL?

2014-03-12 Thread Emmanuel Bernard
I find checking null a bit cleaner. -1 is so C :) but that's relatively minor and we can go either way. On 11 mars 2014, at 21:59, Randall Hauch rha...@redhat.com wrote: Maybe a Long rather than an Integer? Ints are so last year. :-) And, what about using a primitive that returns -1

[infinispan-dev] Never push with --force

2014-03-12 Thread Sanne Grinovero
Yesterday I pushed a fix from Dan upstream, and this morning the fix wasn't there anymore. Some unrelated fix was merged in the meantime. I only realized this because I was updating my personal origin and git wouldn't allow me to push the non-fast-forward branch, so in a sense I could detect it

Re: [infinispan-dev] Never push with --force

2014-03-12 Thread Erik Salter
wget -q -O- http://infinispan.org/hallofshame | grep -c Erik Salter count: 0 Whew! -Original Message- From: infinispan-dev-boun...@lists.jboss.org [mailto:infinispan-dev-boun...@lists.jboss.org] On Behalf Of Emmanuel Bernard Sent: Wednesday, March 12, 2014 6:05 AM To: infinispan -Dev

Re: [infinispan-dev] Never push with --force

2014-03-12 Thread Adrian Nistor
Sanne, is it possible that you forgot to push his changes upstream when closing his PR? This is what the github news feed of infinispan repo tells me: 1. Dan opened the PR #2433 yesterday (about 20 hrs ago) 2. you closed his PR after a few hours (15 hrs ago) and commented 'Merged', but I cannot

Re: [infinispan-dev] Infinispan HotRod C# Client 7.0.0.Alpha1

2014-03-12 Thread Galder Zamarreño
Nice work Ion :) On 05 Mar 2014, at 13:20, Ion Savin isa...@redhat.com wrote: Hi all, Infinispan HotRod C# Client 7.0.0.Alpha1 is now available. This new version is a C# wrapper over the native client and brings support for L2 and L3 client intelligence levels in addition to L1. As

Re: [infinispan-dev] Never push with --force

2014-03-12 Thread Sanne Grinovero
On 12 March 2014 16:01, Adrian Nistor anis...@redhat.com wrote: Sanne, is it possible that you forgot to push his changes upstream when closing his PR? Maybe that's what happened. I use a script though which pushes to both so I think it's unlikely, and my own repo is second in order, it's

Re: [infinispan-dev] Design change in Infinispan Query

2014-03-12 Thread Galder Zamarreño
On 04 Mar 2014, at 19:02, Emmanuel Bernard emman...@hibernate.org wrote: /snip To anecdotally answer your specific example, yes different configs for different entities is an interesting benefit but it has to outweigh the drawbacks. Using a single cache for all the types is practical

Re: [infinispan-dev] Design change in Infinispan Query

2014-03-12 Thread Galder Zamarreño
On 05 Mar 2014, at 18:16, Mircea Markus mmar...@redhat.com wrote: Sanne came with a good follow up to this email, just some small clarifications: On Mar 4, 2014, at 6:02 PM, Emmanuel Bernard emman...@hibernate.org wrote: If you have to do a map reduce for tasks so simple as age 18, I

Re: [infinispan-dev] Design change in Infinispan Query

2014-03-12 Thread Galder Zamarreño
Just saw Sanne’s follow up reply, it’s pretty much the same I suggest. Cheers, On 12 Mar 2014, at 18:45, Galder Zamarreño gal...@redhat.com wrote: On 05 Mar 2014, at 18:16, Mircea Markus mmar...@redhat.com wrote: Sanne came with a good follow up to this email, just some small

Re: [infinispan-dev] Design change in Infinispan Query

2014-03-12 Thread Paul Ferraro
On Wed, 2014-03-12 at 18:45 +0100, Galder Zamarreño wrote: On 05 Mar 2014, at 18:16, Mircea Markus mmar...@redhat.com wrote: Sanne came with a good follow up to this email, just some small clarifications: On Mar 4, 2014, at 6:02 PM, Emmanuel Bernard emman...@hibernate.org wrote:

Re: [infinispan-dev] Design change in Infinispan Query

2014-03-12 Thread William Burns
On Wed, Mar 12, 2014 at 3:12 PM, Paul Ferraro paul.ferr...@redhat.com wrote: On Wed, 2014-03-12 at 18:45 +0100, Galder Zamarreño wrote: On 05 Mar 2014, at 18:16, Mircea Markus mmar...@redhat.com wrote: Sanne came with a good follow up to this email, just some small clarifications: On