On 13 Mar 2014, at 10:48, Mircea Markus mmar...@redhat.com wrote:
On Mar 12, 2014, at 17:45, Galder Zamarreño gal...@redhat.com wrote:
On 05 Mar 2014, at 18:16, Mircea Markus mmar...@redhat.com wrote:
If anything, this model reduces type safety and reusability. E.g. say you
want a
On Mar 12, 2014, at 17:45, Galder Zamarreño gal...@redhat.com wrote:
On 05 Mar 2014, at 18:16, Mircea Markus mmar...@redhat.com wrote:
If anything, this model reduces type safety and reusability. E.g. say you
want a M/R task to see how many Persons speak French. With the single cache
On Mar 12, 2014, at 17:37, Galder Zamarreño gal...@redhat.com wrote:
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
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
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
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
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:
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
On Mar 6, 2014, at 9:21 AM, Emmanuel Bernard emman...@hibernate.org wrote:
On Wed 2014-03-05 17:16, Mircea Markus 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
On 7 March 2014 14:54, Mircea Markus mmar...@redhat.com wrote:
On Mar 6, 2014, at 9:21 AM, Emmanuel Bernard emman...@hibernate.org wrote:
On Wed 2014-03-05 17:16, Mircea Markus wrote:
Sanne came with a good follow up to this email, just some small
clarifications:
On Mar 4, 2014, at 6:02
On Mar 7, 2014, at 3:21 PM, Sanne Grinovero sa...@infinispan.org wrote:
On 7 March 2014 14:54, Mircea Markus mmar...@redhat.com wrote:
On Mar 6, 2014, at 9:21 AM, Emmanuel Bernard emman...@hibernate.org wrote:
On Wed 2014-03-05 17:16, Mircea Markus wrote:
Sanne came with a good follow up
On 07 Mar 2014, at 16:21, Sanne Grinovero sa...@infinispan.org wrote:
Is it possible to use an index for x-cache joins with linear index update
time and query?
Index update cost is not linear but LogN: approximates to a constant
cost. And we could cut this constant by 4 orders of
On 7 March 2014 15:27, Mircea Markus mmar...@redhat.com wrote:
On Mar 7, 2014, at 3:21 PM, Sanne Grinovero sa...@infinispan.org wrote:
On 7 March 2014 14:54, Mircea Markus mmar...@redhat.com wrote:
On Mar 6, 2014, at 9:21 AM, Emmanuel Bernard emman...@hibernate.org wrote:
On Wed 2014-03-05
On 7 March 2014 15:55, Emmanuel Bernard emman...@hibernate.org wrote:
On 07 Mar 2014, at 16:21, Sanne Grinovero sa...@infinispan.org wrote:
Is it possible to use an index for x-cache joins with linear index update
time and query?
Index update cost is not linear but LogN: approximates to a
On Wed 2014-03-05 17:16, Mircea Markus 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 think
you system
On 6 March 2014 09:21, Emmanuel Bernard emman...@hibernate.org wrote:
On Wed 2014-03-05 17:16, Mircea Markus 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
On Mar 4, 2014, at 10:03 PM, Sanne Grinovero sa...@infinispan.org wrote:
My impression is that this thread is boiling down to an identity
problem of the project.
It is a key/value store with some properties which make it a great fit
for a Cache; I don't think there are doubts that
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 think you
system better have to be prepared to run gazillions of M/R
On 28 Feb 2014, at 22:14, Mircea Markus mmar...@redhat.com wrote:
On Feb 26, 2014, at 5:14 PM, Emmanuel Bernard emman...@hibernate.org wrote:
On 25 Feb 2014, at 16:08, Mircea Markus mmar...@redhat.com wrote:
On Feb 25, 2014, at 9:28 AM, Emmanuel Bernard emman...@hibernate.org
On Feb 26, 2014, at 5:14 PM, Emmanuel Bernard emman...@hibernate.org wrote:
On 25 Feb 2014, at 16:08, Mircea Markus mmar...@redhat.com wrote:
On Feb 25, 2014, at 9:28 AM, Emmanuel Bernard emman...@hibernate.org wrote:
On 24 févr. 2014, at 17:39, Mircea Markus mmar...@redhat.com wrote:
Added a correction:
On Feb 28, 2014, at 9:14 PM, Mircea Markus mmar...@redhat.com wrote:
On 24 févr. 2014, at 17:39, Mircea Markus mmar...@redhat.com wrote:
On Feb 17, 2014, at 10:13 PM, Emmanuel Bernard emman...@hibernate.org
wrote:
By the way, Mircea, Sanne and I had quite a long
On Feb 25, 2014, at 5:08 PM, Sanne Grinovero sa...@infinispan.org wrote:
There also is the opposite problem to be considered, as Emmanuel
suggested on 11/04/2012:
you can't forbid the user to store the same object (same type and same
id) in two different caches, where each Cache might be
On Wed, Feb 26, 2014 at 3:12 PM, Mircea Markus mmar...@redhat.com wrote:
On Feb 25, 2014, at 5:08 PM, Sanne Grinovero sa...@infinispan.org wrote:
There also is the opposite problem to be considered, as Emmanuel
suggested on 11/04/2012:
you can't forbid the user to store the same object
On Feb 26, 2014, at 2:13 PM, Dan Berindei dan.berin...@gmail.com wrote:
On Wed, Feb 26, 2014 at 3:12 PM, Mircea Markus mmar...@redhat.com wrote:
On Feb 25, 2014, at 5:08 PM, Sanne Grinovero sa...@infinispan.org wrote:
There also is the opposite problem to be considered, as Emmanuel
On 02/26/2014 04:20 PM, Mircea Markus wrote:
On Feb 26, 2014, at 2:13 PM, Dan Berindei dan.berin...@gmail.com wrote:
On Wed, Feb 26, 2014 at 3:12 PM, Mircea Markus mmar...@redhat.com wrote:
On Feb 25, 2014, at 5:08 PM, Sanne Grinovero sa...@infinispan.org wrote:
There also is the opposite
On Feb 26, 2014, at 2:33 PM, Adrian Nistor anis...@redhat.com wrote:
On 02/26/2014 04:20 PM, Mircea Markus wrote:
On Feb 26, 2014, at 2:13 PM, Dan Berindei dan.berin...@gmail.com wrote:
On Wed, Feb 26, 2014 at 3:12 PM, Mircea Markus mmar...@redhat.com wrote:
On Feb 25, 2014, at 5:08
On 25 Feb 2014, at 16:08, Mircea Markus mmar...@redhat.com wrote:
On Feb 25, 2014, at 9:28 AM, Emmanuel Bernard emman...@hibernate.org wrote:
On 24 févr. 2014, at 17:39, Mircea Markus mmar...@redhat.com wrote:
On Feb 17, 2014, at 10:13 PM, Emmanuel Bernard emman...@hibernate.org
On 24 févr. 2014, at 17:39, Mircea Markus mmar...@redhat.com wrote:
On Feb 17, 2014, at 10:13 PM, Emmanuel Bernard emman...@hibernate.org
wrote:
By the way, Mircea, Sanne and I had quite a long discussion about this one
and the idea of one cache per entity. It turns out that the
On Feb 25, 2014, at 9:28 AM, Emmanuel Bernard emman...@hibernate.org wrote:
On 24 févr. 2014, at 17:39, Mircea Markus mmar...@redhat.com wrote:
On Feb 17, 2014, at 10:13 PM, Emmanuel Bernard emman...@hibernate.org
wrote:
By the way, Mircea, Sanne and I had quite a long discussion
On Feb 25, 2014, at 3:46 PM, Adrian Nistor anis...@gmail.com wrote:
They can do what they please. Either put multiple types in one basket or put
them in separate caches (one type per cache). But allowing / recommending is
one thing, mandating it is a different story.
There's no reason to
On Feb 17, 2014, at 5:35 PM, Galder Zamarreño gal...@redhat.com wrote:
On 30 Jan 2014, at 20:51, Mircea Markus mmar...@redhat.com wrote:
On Jan 30, 2014, at 9:42 AM, Galder Zamarreño gal...@redhat.com wrote:
On Jan 21, 2014, at 11:52 PM, Mircea Markus mmar...@redhat.com wrote:
On Feb 17, 2014, at 10:13 PM, Emmanuel Bernard emman...@hibernate.org wrote:
By the way, Mircea, Sanne and I had quite a long discussion about this one
and the idea of one cache per entity. It turns out that the right (as in
easy) solution does involve a higher level programming model like
On Feb 18, 2014, at 12:02 PM, Adrian Nistor anis...@redhat.com wrote:
Well, OGM and Infinispan are different species :) So, Infinispan being what
it is today - a non-homogenous, schema-less KV store, without support for
entity associations (except embedding) - which simplifies the whole
On Feb 24, 2014, at 5:39 PM, Sanne Grinovero sa...@infinispan.org wrote:
On 24 February 2014 16:51, Mircea Markus mmar...@redhat.com wrote:
Just to recap the main reason for the JPA cache store is to be a replacement
for the JDBCacheStore, nothing more than that.
And it certainly has
On Feb 17, 2014, at 5:36 PM, Galder Zamarreño gal...@redhat.com wrote:
On 31 Jan 2014, at 09:28, Emmanuel Bernard emman...@hibernate.org wrote:
On 30 janv. 2014, at 20:51, Mircea Markus mmar...@redhat.com wrote:
On Jan 30, 2014, at 9:42 AM, Galder Zamarreño gal...@redhat.com
Well, OGM and Infinispan are different species :) So, Infinispan being
what it is today - a non-homogenous, schema-less KV store, without
support for entity associations (except embedding) - which simplifies
the whole thing a lot, should we or should we not provide transparent
On Tue 2014-02-18 14:02, Adrian Nistor wrote:
Well, OGM and Infinispan are different species :) So, Infinispan being what
it is today - a non-homogenous, schema-less KV store, without support for
entity associations (except embedding) - which simplifies the whole thing a
lot, should we or
On 18 February 2014 13:01, Emmanuel Bernard emman...@hibernate.org wrote:
On Tue 2014-02-18 14:02, Adrian Nistor wrote:
Well, OGM and Infinispan are different species :) So, Infinispan being what
it is today - a non-homogenous, schema-less KV store, without support for
entity associations
On Tue 2014-02-18 13:27, Sanne Grinovero wrote:
On 18 February 2014 13:01, Emmanuel Bernard emman...@hibernate.org wrote:
On Tue 2014-02-18 14:02, Adrian Nistor wrote:
There were some points raised previously like /if you search for more than
one cache transparently, then you probably need
On 30 Jan 2014, at 20:51, Mircea Markus mmar...@redhat.com wrote:
On Jan 30, 2014, at 9:42 AM, Galder Zamarreño gal...@redhat.com wrote:
On Jan 21, 2014, at 11:52 PM, Mircea Markus mmar...@redhat.com wrote:
On Jan 15, 2014, at 1:42 PM, Emmanuel Bernard emman...@hibernate.org
On 05 Feb 2014, at 17:30, Emmanuel Bernard emman...@hibernate.org wrote:
On Wed 2014-02-05 15:53, Mircea Markus wrote:
On Feb 3, 2014, at 9:32 AM, Emmanuel Bernard emman...@hibernate.org wrote:
Sure searching for any cache is useful. What I was advocating is that if
you search for more
On Mon 2014-02-17 18:43, Galder Zamarreño wrote:
On 05 Feb 2014, at 17:30, Emmanuel Bernard emman...@hibernate.org wrote:
On Wed 2014-02-05 15:53, Mircea Markus wrote:
On Feb 3, 2014, at 9:32 AM, Emmanuel Bernard emman...@hibernate.org
wrote:
Sure searching for any cache is
On 31 Jan 2014, at 09:28, Emmanuel Bernard emman...@hibernate.org wrote:
On 30 janv. 2014, at 20:51, Mircea Markus mmar...@redhat.com wrote:
On Jan 30, 2014, at 9:42 AM, Galder Zamarreño gal...@redhat.com wrote:
On Jan 21, 2014, at 11:52 PM, Mircea Markus mmar...@redhat.com wrote:
By the way, Mircea, Sanne and I had quite a long discussion about this one and
the idea of one cache per entity. It turns out that the right (as in easy)
solution does involve a higher level programming model like OGM provides. You
can simulate it yourself using the Infinispan APIs but it is
On Wed 2014-02-05 21:40, Mircea Markus wrote:
On Feb 5, 2014, at 7:34 PM, Emmanuel Bernard emman...@hibernate.org wrote:
On Wed 2014-02-05 17:44, Radim Vansa wrote:
On 02/05/2014 05:30 PM, Emmanuel Bernard wrote:
On Wed 2014-02-05 15:53, Mircea Markus wrote:
On Feb 3, 2014, at 9:32
On Feb 3, 2014, at 9:32 AM, Emmanuel Bernard emman...@hibernate.org wrote:
Sure searching for any cache is useful. What I was advocating is that if you
search for more than one cache transparently, then you probably need to CRUD
for more than one cache transparently as well. And this is not
On Wed 2014-02-05 15:53, Mircea Markus wrote:
On Feb 3, 2014, at 9:32 AM, Emmanuel Bernard emman...@hibernate.org wrote:
Sure searching for any cache is useful. What I was advocating is that if
you search for more than one cache transparently, then you probably need to
CRUD for more
On 02/05/2014 05:30 PM, Emmanuel Bernard wrote:
On Wed 2014-02-05 15:53, Mircea Markus wrote:
On Feb 3, 2014, at 9:32 AM, Emmanuel Bernard emman...@hibernate.org wrote:
Sure searching for any cache is useful. What I was advocating is that if
you search for more than one cache transparently,
On Feb 5, 2014, at 4:30 PM, Emmanuel Bernard emman...@hibernate.org wrote:
On Wed 2014-02-05 15:53, Mircea Markus wrote:
On Feb 3, 2014, at 9:32 AM, Emmanuel Bernard emman...@hibernate.org wrote:
Sure searching for any cache is useful. What I was advocating is that if
you search for
On Wed 2014-02-05 17:44, Radim Vansa wrote:
On 02/05/2014 05:30 PM, Emmanuel Bernard wrote:
On Wed 2014-02-05 15:53, Mircea Markus wrote:
On Feb 3, 2014, at 9:32 AM, Emmanuel Bernard emman...@hibernate.org
wrote:
Sure searching for any cache is useful. What I was advocating is that if
On Feb 5, 2014, at 1:34 PM, Emmanuel Bernard emman...@hibernate.org wrote:
What I am saying is that the idea of search across caches as
appealing as it is is is not the whole story.
People search, read, navigate and M/R their data in interleaved ways.
You need to project and think about a
On Feb 5, 2014, at 7:34 PM, Emmanuel Bernard emman...@hibernate.org wrote:
On Wed 2014-02-05 17:44, Radim Vansa wrote:
On 02/05/2014 05:30 PM, Emmanuel Bernard wrote:
On Wed 2014-02-05 15:53, Mircea Markus wrote:
On Feb 3, 2014, at 9:32 AM, Emmanuel Bernard emman...@hibernate.org
wrote:
On Jan 31, 2014, at 7:30 AM, Radim Vansa rva...@redhat.com wrote:
On 01/30/2014 08:51 PM, Mircea Markus wrote:
On Jan 30, 2014, at 9:42 AM, Galder Zamarreño gal...@redhat.com wrote:
On Jan 21, 2014, at 11:52 PM, Mircea Markus mmar...@redhat.com wrote:
On Jan 15, 2014, at 1:42 PM,
On Jan 21, 2014, at 11:52 PM, Mircea Markus mmar...@redhat.com wrote:
On Jan 15, 2014, at 1:42 PM, Emmanuel Bernard emman...@hibernate.org wrote:
By the way, people looking for that feature are also asking for a unified
Cache API accessing these several caches right? Otherwise I am not
On Jan 30, 2014, at 9:42 AM, Galder Zamarreño gal...@redhat.com wrote:
On Jan 21, 2014, at 11:52 PM, Mircea Markus mmar...@redhat.com wrote:
On Jan 15, 2014, at 1:42 PM, Emmanuel Bernard emman...@hibernate.org wrote:
By the way, people looking for that feature are also asking for a
On 01/30/2014 08:51 PM, Mircea Markus wrote:
On Jan 30, 2014, at 9:42 AM, Galder Zamarreño gal...@redhat.com wrote:
On Jan 21, 2014, at 11:52 PM, Mircea Markus mmar...@redhat.com wrote:
On Jan 15, 2014, at 1:42 PM, Emmanuel Bernard emman...@hibernate.org
wrote:
By the way, people looking
By the way, people looking for that feature are also asking for a unified Cache
API accessing these several caches right? Otherwise I am not fully
understanding why they ask for a unified query.
Do you have written detailed use cases somewhere for me to better understand
what is really
Up this: it was proposed again today ad a face to face meeting.
Apparently multiple parties have been asking to be able to run
cross-cache queries.
Sanne
On 11 April 2012 12:47, Emmanuel Bernard emman...@hibernate.org wrote:
On 10 avr. 2012, at 19:10, Sanne Grinovero wrote:
Hello all,
On 10 Apr 2012, at 18:10, Sanne Grinovero wrote:
Hello all,
currently Infinispan Query is an interceptor registering on the
specific Cache instance which has indexing enabled; one such
interceptor is doing all what it needs to do in the sole scope of the
cache it was registered in.
If
Hello all,
currently Infinispan Query is an interceptor registering on the
specific Cache instance which has indexing enabled; one such
interceptor is doing all what it needs to do in the sole scope of the
cache it was registered in.
If you enable indexing - for example - on 3 different caches,
60 matches
Mail list logo
