On 22 Jan 2014, at 14:48, Mircea Markus mmar...@redhat.com wrote:
On Jan 22, 2014, at 1:26 PM, Emmanuel Bernard emman...@hibernate.org wrote:
Conceptually I like the grouping API better than AtomicMap as I don’t have
to rely on a specific Infinispan type.
We do use
On 22 Jan 2014, at 15:11, Emmanuel Bernard emman...@hibernate.org wrote:
So you don't use the AtomicMap(vs FGAM) at all? Is there any place in which
you require a lock in the whole map to be acquired?
I will be not right now.
Hum, it should read: It will be. But not right now
requested?
Emmanuel
On 14 Jan 2014, at 12:59, Sanne Grinovero sa...@infinispan.org wrote:
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
On Thu 2013-12-19 9:46, Galder Zamarreño wrote:
== Example of continuous query atop remote listeners
Thinking about how to implement continuous query atop this
infrastructure I am missing a few things.
The primary problem is that I don't want to enlist a filter id per
continuous
On Thu 2013-12-19 19:57, Dan Berindei wrote:
On Thu, Dec 19, 2013 at 2:15 PM, Emmanuel Bernard
emman...@hibernate.orgwrote:
On Thu 2013-12-19 9:46, Galder Zamarreño wrote:
== Example of continuous query atop remote listeners
Thinking about how to implement continuous query atop
Much better. Some more feedback.
== Filter and converter
I am wondering if there is a benefit in separating filters and
converters. It does add some understanding complexity so a single
ServerListener with the methods from RemoteFilter / RemoveConverter
might be better.
Should filter /
Cool, I was afraid you had sent my feedback to /dev/null :)
On Wed 2013-11-27 8:35, Galder Zamarreño wrote:
In that use case the listener code runs a filtering logic server side
and only send keys that are impacted by the query plus some flag
defining whether it's added to changed or
Hey there,
Here are a few comments based on a quick reading.
I might have totally misread or misinterpreted what was exposed, feel
free to correct me.
## General
I think you are restricting the design to listeners:
* that only listen to raw entry changes
* whose processing is remote
* with no
a JIRA for that?
For now I guess you can sacrifice performance and always sending the entire
object across on every update instead of only the deltas?
On Nov 18, 2013, at 9:56 AM, Emmanuel Bernard emman...@hibernate.org wrote:
Someone mentioned the grouping API as some sort of alternative
This message was a response to a different email discussing the composite
key approach k1 - a1 k1 - a2.
The actual JIRAs are opened :
* https://issues.jboss.org/browse/ISPN-3732
* https://issues.jboss.org/browse/ISPN-3733
Emmanuel
On Tue 2013-11-19 11:22, Emmanuel Bernard wrote:
It's
.
On Tue 2013-11-19 10:41, Sanne Grinovero wrote:
We could rely on remote queries?
On 19 November 2013 10:31, Emmanuel Bernard emman...@hibernate.org wrote:
This message was a response to a different email discussing the composite
key approach k1 - a1 k1 - a2.
The actual JIRAs are opened
On Tue 2013-11-19 12:23, Radim Vansa wrote:
On 11/19/2013 09:48 AM, Emmanuel Bernard wrote:
I wish the design document was showing how we can achieve a general
purpose remote listener approach but have a step 1 that is only
targeting a restricted set of listeners if you feel that it's too
Grinovero wrote:
On 12 November 2013 14:54, Emmanuel Bernard emman...@hibernate.org wrote:
On the transaction side, we can start without them.
+1 on omitting transactions for now.
And on the missing AtomicMaps, I hope the Infinispan will want to implement
it?
Would be good to eventually
On the transaction side, we can start without them.
On Tue 2013-11-12 14:34, Davide D'Alto wrote:
Hi,
I'm working on the integration between HotRod and OGM.
We already have a dialect for Inifinispan and I'm trying to follow the same
logic.
At the moment I'm having two problems:
1) In
If you use MarkKonami, you get a hidden bonus.
On Thu 2013-10-31 10:39, Manik Surtani wrote:
On 30 October 2013 19:26, Mircea Markus mmar...@redhat.com wrote:
On Oct 30, 2013, at 4:49 PM, Manik Surtani ma...@infinispan.org wrote:
I only suggested AsciiDoc to be consistent with the
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
OData, RDF and to some extend GData try to offer a schema, API and query
capability atop HTTP and other web techs.
It would be an interesting project to build OData support on top of
Infinispan and see where that goes in the community. That support would
live alongside memcache and HotRod.
But
On 21 sept. 2013, at 18:32, William Burns mudokon...@gmail.com wrote:
[Technically it would be awesome to be able to be able to rely on RR
but it doesn't work as in databases - it doesn't snapshot the version
of entries not touched yet - so we have to compensate at a higher
layer..]
The
I sort of see how we could replace it but we do make use of the FGAM to
represent an Hibernate OGM dehydrated entity with one property per map
entry.
From what you are describing we would get an alternative solution but
that would mean more memory strain and object creation. That will
negatively
On 31 août 2013, at 12:33, Pierre Sutra pierre.su...@unine.ch wrote:
^ It'll be easier for you to keep up with the latest master changes in
upstream if you work on topic branches instead of your fork's master [1]
If I understand correctly, this does not provide me with a copy on a
remote
This is not quite true. There are constraints on what a Red Hat
sponsored project can use infrastructure wise.
Most of them are fairly reasonable, I encourage you to have a look at
it before going further.
https://docspace.corp.redhat.com/docs/DOC-133222
In particular there are business reasons
everything could work automagically provided that
class field names match the field name in the proto file and also field types
match so no value convertor needs to be specified. If they don't, then
annotate.
Does this seem a little better?
On 07/15/2013 06:57 PM, Emmanuel Bernard wrote
Mircea, Adrian and I had an IRC chat on ProtoStream and ProtoStuff.
check out
http://transcripts.jboss.org/channel/irc.freenode.org/%23infinispan/2013/%23infinispan.2013-07-15.log.html
starting at 11:00 and finishing at 12:30
A short summary of what has been discussed:
- ProtoStream is a good
to express field indexes wich would
amke the annotation approach more verbose.
On Mon 2013-07-15 16:04, Manik Surtani wrote:
I'm sorry I missed this. Is there an example of each API somewhere?
On 15 Jul 2013, at 14:01, Emmanuel Bernard emman...@hibernate.org wrote:
Mircea, Adrian and I had
On Wed 2013-07-10 16:18, Mircea Markus wrote:
On 9 Jul 2013, at 14:20, Emmanuel Bernard emman...@hibernate.org wrote:
Ah it's quite sad protostuff does not live up to the expectation :(
Compared to the google libs, streamlike is definitely a nice approach but
I feel a bit sad
On 8 juil. 2013, at 21:06, Mircea Markus mmar...@redhat.com wrote:
On 1 Jul 2013, at 09:29, Emmanuel Bernard emman...@hibernate.org wrote:
Ah it's quite sad protostuff does not live up to the expectation :(
Compared to the google libs, streamlike is definitely a nice approach but I
to be written by humans or other applications?
--Gunnar
2013/6/11 Emmanuel Bernard emman...@hibernate.org
Hey everyone,
Sanne and I discussed Hibernate Search queries and serialization in
general. I did play around that to represent Hibernate Search DSL
queries into JSON
:44, Emmanuel Bernard emman...@hibernate.org wrote:
A few comments in no particular order
- nice work
- try and cover all future possible extensions of the language to be
sure you are not heading to a trap
- no cross type support
I suspect some kind of Union query could be useful
(from
Hehe yes http://emmanuelbernard.com/blog/2013/05/28/autocompletion-is-crap/
On 12 juin 2013, at 18:07, Sanne Grinovero sa...@hibernate.org wrote:
wish: please try them in Eclipse too as sometimes the usage experience is not
the same.
On 12 Jun 2013 18:05, Emmanuel Bernard emman
The reading experience is mostly unaffected though.
Only Indentation matters.
On 12 juin 2013, at 18:17, Emmanuel Bernard emman...@hibernate.org wrote:
Hehe yes http://emmanuelbernard.com/blog/2013/05/28/autocompletion-is-crap/
On 12 juin 2013, at 18:07, Sanne Grinovero sa...@hibernate.org
Hey everyone,
Sanne and I discussed Hibernate Search queries and serialization in
general. I did play around that to represent Hibernate Search DSL
queries into JSON.
https://gist.github.com/emmanuelbernard/5760676
It is a very first draft (not reviewed). What is really nice is that I did not
I'm personally more aligned with Sanne's concerns. In particular, you should be
able to release really quickly and the release cycle separation seems like a
sign that you cannot achieve that today.
We had a very bad experience with Hibernate around a matrix of compatibility
between core,
No, it is one RPC call for every put or delete in the grid. I'm sure the
test makes a bunch of them.
On Fri 2013-04-12 12:40, Bela Ban wrote:
I might have misunderstood something: if this is *one* sync RPC, then
enabling or disabling of bundling won't have an impact; as 60ms added to
50 secs
On Apr 12, 2013, at 2:12 PM, Emmanuel Bernard emman...@hibernate.org wrote:
No, it is one RPC call for every put or delete in the grid. I'm sure the
test makes a bunch of them.
On Fri 2013-04-12 12:40, Bela Ban wrote:
I might have misunderstood something: if this is *one* sync RPC
Dan worked to understand the problem, here is where we stand without
Sanne's additional knowledge.
The test failing is the following:
tx1.start();
cache.remove(key);
tx1.commit();
assert queryDeletedKey.getResults().size() == 0;
Surprisingly, the entity is still found in the
The question is: what does 107 plan to gain from this? If that's
virtually nothing, then the move is not necessary.
Emmanuel
On Fri 2013-02-08 9:29, Galder Zamarreño wrote:
Thoughts?
Begin forwarded message:
From: Brian Oliver brian.oli...@oracle.com
Subject: Moving to Java 7?
Date:
to
sign a contributor agreement first[1].
Thank you!
[1] https://cla.jboss.org/index.seam
On 31 Oct 2012, at 00:18, Emmanuel Bernard wrote:
Hey,
I'll try and channel the team as they are busy on too many fronts these
days.
The contribution looks cool. I am not sure what
Hey,
I'll try and channel the team as they are busy on too many fronts these days.
The contribution looks cool. I am not sure what is the strategy going to be on
the various clients. Hosted under the Infinispan org or left separate. My guess
is hosting in the org makes more sense.
Can you
Correct, the DocumentExtractor contract expects the absolute index. It
looks like a bug in how ISPN's Query module use it.
Emmanuel
On Fri 2012-10-26 16:09, Ales Justin wrote:
After searching for the needed in haystack, I finally found the problem.
(not to mention complete lack of tests for
hide the offset (and max) into impl
details.
-Ales
On Oct 29, 2012, at 11:14 AM, Emmanuel Bernard emman...@hibernate.org wrote:
Correct, the DocumentExtractor contract expects the absolute index. It
looks like a bug in how ISPN's Query module use it.
Emmanuel
On Fri 2012-10-26
On Wed 2012-10-24 12:21, Dan Berindei wrote:
On Tue, Oct 23, 2012 at 11:42 PM, Emmanuel Bernard
emman...@hibernate.orgwrote:
On Tue 2012-10-23 22:42, Dan Berindei wrote:
I was probably overreacting, but I just wouldn't want us to end up with
rules like 'all method parameters must
On Tue 2012-09-25 15:00, Sanne Grinovero wrote:
While at it, it would be nice to see if we can change the signature
from extends IterableObject to return an iterator on the types
compatible with the values of the cache, since the Cache supports
proper generics.
Projection doesn't allow you to
Good news. You could have OracleDB bundled too ;)
On 31 mars 2012, at 08:12, Tristan Tarrant ttarr...@redhat.com wrote:
Galder and I chatted on IRC about it just before he did the 5.1.3.FINAL
release, and he convinced me that the -all distribution would be for
people who don't use Maven.
I do tend to commit often and rebase/amend if needed. It helps minimize context
switching.
The big plus for me is that I can work on the next thing while tests are
running.
I never have my command line in the cloned repo so I can never commit to the
wrong repo.
Btw you can ask IntelliJ to
On 7 déc. 2011, at 17:37, Sanne Grinovero wrote:
On 7 December 2011 16:15, Manik Surtani ma...@jboss.org wrote:
Sanne,
+1 to consistency. I suggest we
repurpose https://issues.jboss.org/browse/ISPN-1429 to a consistent logging
scheme. My preference is for a static final boolean trace =
How do you recognize Infinispan discussions from other projects discussions?
They use 4 letters acronyms instead of the traditional 3 letters acronyms :)
On 4 nov. 2011, at 17:27, Vladimir Blagojevic wrote:
After completing and integrating LIRS rework I am currently looking into
FGAM
On 9 sept. 2011, at 15:32, Sanne Grinovero wrote:
I think both the pull-requestor and the reviewer should run a full
build before allowing any change to be pushed upstream; with a script
like this one:
https://gist.github.com/789588
it won't even prevent you to work on a different branch
On 1 août 2011, at 18:16, Mircea Markus wrote:
Hi,
These is a draft of the config changes I plan to add with ISPN-1131, can you
please comment?
1.
transaction lockingMode=optimistic/
The lockingMode attribute can have two values: optimistic(default) and
pessimistic. If pessimistic
Email summary:
Number of lines: 188
Number of useful lines (Strict): 1 (0,53%)
Number of useful line (contextual): 12 (6.3%)
Position of the useful line in the amount of data: 57 (had to scroll 30% of the
data to find it and the addition 70% as I was not sure another one wasn't lost
somewhere
Back from the dead
On Jun 13, 2011, at 8:25 PM, Sanne Grinovero wrote:
While reviewing ISPN-200 it's clear that Israel needed to copy over
some code from Hibernate Search in Infinispan Query, to make some
small changes to internal classes; All the changes I spotted so far
are around making
Your description explains a use case / pattern but wo code showing how to
implement it properly.
In this case what's the best way for me to verify that the new data has indeed
been pushed to the cache?
put and then immediate get
Put, wait, get
Put all entries, then get all entries, and loop
:
cache.withFlags(Flag.SKIP_REMOTE_LOOKUP, Flag.SKIP_CACHE_LOAD).put( .. )
I guess that nobody knows that :)
Sanne
2011/5/16 Emmanuel Bernard emman...@hibernate.org:
Yes I think something use case driven would make a nice portal.
On 16 mai 2011, at 17:22, Galder Zamarreño wrote
I don't enjoy using JBoss Logging for that reason :)
I always have to get down to the JavaDoc or figure out the list of available
params to understand what debug* does for example and which one I need.
I guess that's taste and for something like JBoss Logging, a fluent API is
costly
Quick question.
In case of 2.a (ie setting the TCCL), this is a requirement for frameworks and
libraries using Infinispan, right? Not / never for a user application using
Infinispan (in this case it seems that the application class loader will do the
right thing and is set as the TCCL by the AS
the
underlying map but that's for sure surprising and can lead to weird bugs for
ATM users. Is that necessary?
Emmanuel
On 14 avr. 2011, at 10:30, Manik Surtani wrote:
Apologies for the late response.
On 13 Apr 2011, at 10:38, Emmanuel Bernard wrote:
In exchange for answers, I will improve
hits an event adding a new type, the
Search engine is reconfigured.
thoughts?
Sanne
2011/4/5 Emmanuel Bernard emman...@hibernate.org:
On 5 avr. 2011, at 13:38, Sanne Grinovero wrote:
2011/4/5 Emmanuel Bernard emman...@hibernate.org:
On 5 avr. 2011, at 12:20, Galder Zamarreño wrote
On 27 avr. 2011, at 08:57, Sanne Grinovero wrote:
2011/4/27 Emmanuel Bernard emman...@hibernate.org:
Users can put indexed or nit indexed superclasses in the query target type.
That would not work for you as you can't discover known subtypes wo scanning
or having a closure of types
In exchange for answers, I will improve at least the JavaDoc and maybe create a
wiki from this info.
(note that this has nothing to do with the ongoing discussion on key-levle
locks for a sister of AtomicMap)
I've tried to search the wiki but found nothing on AtomicMap (only forum posts)
and
Yes I think that would fit the bill. Let me give some more background
Background
In Hibernate OGM, we store collections in a single key essentially as a
SetMapString,Object ie as a set of tuples, esch tuple representing the
equivalent of one row of an association table in a relational database.
On 4 avr. 2011, at 19:24, Sanne Grinovero wrote:
thanks for the quick and comprehensive feedback.
diving inline:
2011/4/4 Emmanuel Bernard emman...@hibernate.org:
Nice job :)
- getBasicQuery methods are deprecated. That's from the previous design
right? Was it a tech preview
On 5 avr. 2011, at 12:03, Galder Zamarreño wrote:
- I'm not a big fan of the constructor approach to get QueryFactory for
various reasons (including the fact that it forces a concrete type and no
interfaces) but it seems to be an ISPN-wide design decision
That's definitely something that
On 5 avr. 2011, at 12:20, Galder Zamarreño wrote:
On Apr 4, 2011, at 6:23 PM, Sanne Grinovero wrote:
/snip
there's one catch:
when searching for a class type, it will only include results from
known subtypes. The targeted type is automatically added to the known
classes, but
Nice job :)
- getBasicQuery methods are deprecated. That's from the previous design right?
Was it a tech preview or was it named as full fledged API?
In the former case I'd get rid of them.
- buildQueryBuilderForClass is that really needed?
qf.buildQueryBuilderForClass( Car.class ).get();
The
As David pointed out %1$ is superior to %s for internationalization.
On 15 mars 2011, at 18:13, Manik Surtani wrote:
Yeah, I currently do:
throw new ConfigurationException(String.format(you 're not allowed to
use %s and %s together, that, other));
but we could overload the
BTW why not transaction timeout=/
what is the reasoning behind cacheStop?
On 4 févr. 2011, at 11:53, Manik Surtani wrote:
Yeah that works.
On 3 Feb 2011, at 19:29, Galder Zamarreño wrote:
In this end I went for transaction cacheStopTimeout=3/ - in case you
wanna make any comments
In some languages, param 2 needs to be put before param 1. How do you solve
that wo positional params?
On 25 janv. 2011, at 15:52, Pete Muir wrote:
On 25 Jan 2011, at 20:29, Manik Surtani wrote:
Guys,
Our current Log impl allows for string formatting, using params like
Or release a 4.3.
On 14 janv. 2011, at 09:32, Bela Ban wrote:
I would fix the existing MurmurHash; IMO backward compat doesn't extend
to consistent hashing...
Does leaving the 1 bit out create extreme anomalies wrt hashing
distribution ? I wouldn't think so...
I'm fine with the other
After being gently reminded by Manik several times, I've finally sat down and
wrote a page on Hibernate OGM.
http://community.jboss.org/wiki/HibernateOGMGeneralInformations
It contains several sections:
- how to use
- how to contribute
- what is supported
- architecture
The wiki went wild,
101 - 168 of 168 matches
Mail list logo
