Emmanuel posted this on the Hibernate list, some interesting ideas in it :)
http://blog.42floors.com/thirty-percent-feedback/
Cheers,
--
Galder Zamarreño
gal...@redhat.com
twitter.com/galderz
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org
On 10 March 2014 17:09, Mircea Markus mmar...@redhat.com wrote:
On Mar 10, 2014, at 15:12, Sanne Grinovero sa...@infinispan.org wrote:
Ok you make some good points, and I've no doubts of it being useful.
My only concern is that this could slow us down significantly in
providing other
On Mar 11, 2014, at 8:46, Galder Zamarreño gal...@redhat.com wrote:
Emmanuel posted this on the Hibernate list, some interesting ideas in it :)
http://blog.42floors.com/thirty-percent-feedback/
Very interesting
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
I think that technical trickiness is also required for implementing
pagination, and would probably also suffer from same
limitations/approximations.
Should we remove pagination too from the api?
On 03/11/2014 10:47 AM, Sanne Grinovero wrote:
On 10 March 2014 17:09, Mircea Markus
To be more precise, by pagination I'm referring to methods
QueryBuilder.startOffset/maxResults. Since our remote protocol are
stateless we would need to re-execute the query to fetch the next page.
That leads to the same problem of approximation.
On 03/11/2014 03:11 PM, Adrian Nistor wrote:
I
I’m struggling with this same question in ModeShape. The JCR API exposes a
method that returns the number of results, but at least the spec allows the
implementation to return -1 if the size is not known (or very expensive to
compute). Yet this still does not satisfy all cases.
Depending upon
On Mar 7, 2014, at 17:11, cotton-ben ben.cot...@alumni.rutgers.edu wrote:
Thanks Peter. The plan is for Dmitry and I to at first extend
VanillaSharedHashMap and groom it into an ISPN7 join via their DataContainer
API bridge.
Ben, at this stage you already have an JCache implementation
/ Ben, at this stage you already have an JCache implementation backed by the
DataContainer, by using the JCache implementation provided by ISPN an
configuring Infinispan with the new custom data container.
/
*Thanks Mircea. We now see it and are proceeding accordingly. We have
removed all
Providing methods that work sometimes and don't work other times is
generally a bad idea.
No matter how much you document it, users *will* try to use it and
expect it to always work
(either because they didn't read the docs that say otherwise, they think
they'll stick to a configuration where
I disagree. Most developers have access to the JavaDoc, and if even moderately
well-written, they will find out what the method returns and when. It’s no
different than a method sometimes returning null rather than an object
reference.
On Mar 11, 2014, at 12:16 PM, Dennis Reed
I agree with Randall.
I tend to be very conservative about my public APIs. And offering an API that I
think will block me in the future is something I tend to avoid.
Something like .guessNbrOfMatchingElements() / .guessResultSize() would provide
a better clue about the gamble the user takes.
what about we call it
int getEstimatedResultSize() ?
Having such a method occasionally return null looks very bad to me,
I'd rather remove the functionality.
-- Sanne
On 11 March 2014 19:08, Emmanuel Bernard emman...@hibernate.org wrote:
I agree with Randall.
I tend to be very conservative
It does not work, I think, because if you implement your query via some map
reduce and you do pagination, it will be costly to compute the size and you
might want not to return it.
Hence my Accuracy idea to clarify the intend to the API user.
On 11 Mar 2014, at 19:18, Sanne Grinovero
I got the OOM in the hotrod client testsuite as well today, and I have a
fix: https://github.com/infinispan/infinispan/pull/2433
On Fri, Mar 7, 2014 at 6:35 PM, Sanne Grinovero sa...@infinispan.orgwrote:
today core passed, but: the Infinispan Hot Rod Client seems to fail
because of an
Maybe a Long rather than an Integer? Ints are so last year. :-)
And, what about using a primitive that returns -1 when the method cannot
determine the size (if allowed by the parameter). Just as easy to check -1 than
it is to check null, IMO.
On Mar 11, 2014, at 2:21 PM, Emmanuel Bernard
On 11 March 2014 20:20, Dan Berindei dan.berin...@gmail.com wrote:
I got the OOM in the hotrod client testsuite as well today, and I have a
fix: https://github.com/infinispan/infinispan/pull/2433
Thanks Dan!
integrated that.
___
infinispan-dev mailing
16 matches
Mail list logo
