ailman/listinfo/infinispan-dev
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> --
&
On 04/06/2017 12:15 AM, Katia Aresti wrote:
>
>
> On Wed, Apr 5, 2017 at 9:56 AM, Radim Vansa <rva...@redhat.com
> <mailto:rva...@redhat.com>> wrote:
>
> On 04/04/2017 06:40 PM, William Burns wrote:
> >
> >
> > On Tue, Apr 4, 2
, and
it seems that segments are suspected after any unsuccessful response.
Which components should react to topology changes?
Thanks!
Radim
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev mailing list
infinispan-dev@lists.jbo
boss.org/meeting/irc.freenode.org/infinispan/2017/infinispan.2017-04-10-14.00.html
>>
>> Cheers
>> Dan
>> ___
>> infinispan-dev mailing list
>> infinispan-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinf
d but I don't know for sure.
>
> On Mon, Apr 10, 2017 at 6:41 AM Radim Vansa <rva...@redhat.com
> <mailto:rva...@redhat.com>> wrote:
>
> Hi Will,
>
> rebasing scattered cache PR I've found a test failure when handling
> streams, and I'd like to a
s citizen API-wise.
> For this reason I propose that we extract the query API to
> infinispan-commons, put the query SPI in infinispan-core together with
> the non-indexed implementation and have the hibernate-search backend as
> a pluggable
> > infinispan-dev mailing list
> > infinispan-dev@lists.jboss.org
> <mailto:infinispan-dev@lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
he optimistic exclusion is acceptable.
>
> Thanks,
>
> - Will
>
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
b.com/ugol/infinispan-go).
>
> And in my opinion, a final version of this document go to infinispan
> design repository: https://github.com/infinispan/infinispan-designs
>
> Apart from that, that's huge effort and really great job!
>
> On Tue, Apr 11, 2017 at 5:05 PM Radim Vansa &l
>> some unexpected nulls among other valid results. The fix was to just
>> filter out those nulls. We could enhance that to double check that the
>> returned entry is indeed of the requested type, to also cover the issue
>> that you encountered.
>>
>>
was not correct, though.
[1]
https://github.com/rvansa/infinispan/commit/1d62c9b84888c7ac21a9811213b5657aa44ff546
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
e, to also cover
> the issue that you encountered.
It's not just entity type, criteria may be invalidated by any field
change. Would a full criteria check on the returned entities be too
expensive? Can you even check e.g. native queries against provided set
of objects?
Radim
>
> Adria
nd-partit
>>>>>> ion.html
>>>>>>
>>>>>> Cheers
>>>>>> Ryan
>>>>>> ___
>>>>>> infinispan-dev mailing list
>>>>>> infinispan-dev@lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>>
>>> ___
>>> infinispan-dev mailing list
>>> infinispan-dev@lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>> ___
>> infinispan-dev mailing list
>> infinispan-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
, Red Hat
>
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
__
[1] https://checkerframework.org/jsr308/
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
On 06/29/2017 02:36 PM, Dan Berindei wrote:
> On Thu, Jun 29, 2017 at 2:19 PM, Radim Vansa <rva...@redhat.com> wrote:
>> On 06/29/2017 11:16 AM, Dan Berindei wrote:
>>> On Thu, Jun 29, 2017 at 11:53 AM, Radim Vansa <rva...@redhat.com> wrote:
>>>>
answered in the user documentation, that would be
> fine but I feel these are things that should be explained/clarified in the
> blog post itself.
>
> Cheers,
>
> [1] http://blog.infinispan.org/2017/07/scattered-cache.html
> --
> Galder Zamarreño
> Infinispan, Red Hat
>
>
On 06/28/2017 10:40 AM, Dan Berindei wrote:
> On Wed, Jun 28, 2017 at 10:17 AM, Radim Vansa <rva...@redhat.com> wrote:
>> On 06/27/2017 03:54 PM, Dan Berindei wrote:
>>> On Tue, Jun 27, 2017 at 2:43 PM, Adrian Nistor <anis...@redhat.com> wrote:
>>>> I've s
On 06/28/2017 04:20 PM, Dan Berindei wrote:
> On Wed, Jun 28, 2017 at 2:17 PM, Radim Vansa <rva...@redhat.com> wrote:
>> On 06/28/2017 10:40 AM, Dan Berindei wrote:
>>> On Wed, Jun 28, 2017 at 10:17 AM, Radim Vansa <rva...@redhat.com> wrote:
>>>>
On 06/29/2017 10:23 AM, Dan Berindei wrote:
> On Wed, Jun 28, 2017 at 5:25 PM, Radim Vansa <rva...@redhat.com> wrote:
>> On 06/28/2017 01:17 PM, Radim Vansa wrote:
>>> On 06/28/2017 10:40 AM, Dan Berindei wrote:
>>>> On Wed, Jun 28, 2017 at 10:17 AM, R
On 06/29/2017 11:16 AM, Dan Berindei wrote:
> On Thu, Jun 29, 2017 at 11:53 AM, Radim Vansa <rva...@redhat.com> wrote:
>> On 06/28/2017 04:20 PM, Dan Berindei wrote:
>>> On Wed, Jun 28, 2017 at 2:17 PM, Radim Vansa <rva...@redhat.com> wrote:
>>>>
On 06/28/2017 01:17 PM, Radim Vansa wrote:
> On 06/28/2017 10:40 AM, Dan Berindei wrote:
>> On Wed, Jun 28, 2017 at 10:17 AM, Radim Vansa <rva...@redhat.com> wrote:
>>> On 06/27/2017 03:54 PM, Dan Berindei wrote:
>>>> On Tue, Jun 27, 2017 at 2:43 PM, Adri
dhat.com/>
>>
>> <https://red.ht/sig>
>>
>>
>> ___
>> infinispan-dev mailing list
>> infinispan-dev@lists.jboss.org
>> <mailto:infinispan-dev@lists.jboss.org>
>
keen on trying to find a potential solution using 2), but wondered if you
> have other ideas.
>
> Cheers,
>
> [1] https://gist.github.com/galderz/0bce6dce16de018375e43e25c0cf3913
> --
> Galder Zamarreño
> Infinispan, Red Hat
>
--
Radim Vansa <rva...@re
gt; --
> Galder Zamarreño
> Infinispan, Red Hat
>
>> On 11 Apr 2017, at 15:57, Radim Vansa <rva...@redhat.com> wrote:
>>
>> Since these tests use real server(s), many of them test not only the
>> client behaviour (generating correct commands according to th
g if
>> most people think like Radim because working on commands has helped me to
>> learn and understand more about infinispan internals, so this hasn't been a
>> waste of time for me.
>>
>> Katia
>>
>> [1] https://issues.jboss.org/browse/ISPN-5728
>> [2] https://github.com
gt; that steve had since master was focused on 5.x
>>> pferraro: i've no idea when/where we'll integrate this, but one
>> thing is for sure: it's nowhere near backwards compatible
>>> actually, fixed one this morning, so down to 15 failures
>>> pferraro: any suggestions/wishes?
>>> is anyone out there? ;)
>> Cheers,
>> --
>> Galder Zamarreño
>> Infinispan, Red Hat
>>
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
is ran without a fancy setup,
though, but it's asking for trouble.
WDYT?
Radim
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infi
return 200 & entity or 204 and no
response)
* Do we handle OPTIONS in any way?
Radim
>
> Thanks,
> Sebastian
>
> --
>
> SEBASTIANŁASKAWIEC
>
> INFINISPAN DEVELOPER
>
> Red HatEMEA <https://www.redhat.com/>
>
> <https://red.ht/sig>
>
>
t; <https://lists.jboss.org/mailman/listinfo/infinispan-dev>
>
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> <mailto:infinispan-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> <https://lists.jboss.org/mailman/listinfo/infinispan-dev>
>
> --
>
> SEBASTIANŁASKAWIEC
>
> INFINISPAN DEVELOPER
>
> Red HatEMEA <https://www.redhat.com/>
>
> <https://red.ht/sig>
>
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> <mailto:infinispan-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> <https://lists.jboss.org/mailman/listinfo/infinispan-dev>
>
>
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org <mailto:infinispan-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> <https://lists.jboss.org/mailman/listinfo/infinispan-dev>
>
>
>
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
it
>>> to compile and the tests to pass
>>>> pferraro: need to switch to async interceptor stack in 2lc
>>> integration and get all the subtle changes right
>>>> pferraro: it's a painstaking job basically
>>>>
On 05/24/2017 10:44 AM, Sebastian Laskawiec wrote:
>
>
> On Tue, May 23, 2017 at 5:06 PM Radim Vansa <rva...@redhat.com
> <mailto:rva...@redhat.com>> wrote:
>
> On 05/16/2017 11:05 AM, Sebastian Laskawiec wrote:
> > Hey guys!
> >
> &
;
> [3]
> https://github.com/slaskawi/external-ip-proxy/tree/master/benchmark
> <https://github.com/slaskawi/external-ip-proxy/tree/master/benchmark>
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists
bedded also needs to depend on core.
>>> >
>>> > Any more details behind this decision?
>>> >
>>> > Cheers,
>>> > --
>>> > Galder Zamarreño
>>> > Infinispan, Red Hat
>>> >
>>> > --
>>> > SEBASTIAN ŁASKAWIEC
>>> > INFINISPAN DEVELOPER
>>> > Red Hat EMEA
>>> >
>>>
>>>
>>> ___
>>> infinispan-dev mailing list
>>> infinispan-dev@lists.jboss.org <mailto:infinispan-dev@lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>> <https://lists.jboss.org/mailman/listinfo/infinispan-dev>
>>>
>>>
>>>
>>>
>>> ___
>>> infinispan-dev mailing list
>>> infinispan-dev@lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>>
>> --
>> Tristan Tarrant
>> Infinispan Lead
>> JBoss, a division of Red Hat
>> ___
>> infinispan-dev mailing list
>> infinispan-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
On 06/12/2017 04:52 PM, William Burns wrote:
>
>
> On Sat, Jun 10, 2017 at 12:56 AM Radim Vansa <rva...@redhat.com
> <mailto:rva...@redhat.com>> wrote:
>
> Hi guys,
>
> when the functional API has been outline, the interfaces were put into
>
On 06/13/2017 03:07 PM, William Burns wrote:
>
>
> On Tue, Jun 13, 2017, 3:54 AM Radim Vansa <rva...@redhat.com
> <mailto:rva...@redhat.com>> wrote:
>
> On 06/12/2017 04:52 PM, William Burns wrote:
> >
> >
> > On Sat, Jun 10,
nd out that
SerializableFunction et all are only in infinispan-core (for good).
Please let me know if you have objections/if there something I have missed.
Radim
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev mailing list
in
I did not, I swear to Ctulhu!
On 06/09/2017 03:10 PM, Tristan Tarrant wrote:
> I told you not to read it.
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
e it the default and add a method
> AdvancedCache.forceReturnPreviousValues()?
Please don't derail the thread.
>
>>
>>
>> On 06/27/2017 01:28 PM, Sanne Grinovero wrote:
>>
>>
>>
>> On 27 Jun 2017 10:13, "Radim Vansa" <rva...
broken)
>>>
>>>
>>> Might be useful for making a POC work, but I believe query will be very
>>> likely to be often enabled.
>>> Having an either / or switch for different features in Infinispan will make
>>> it harder to use and understand, so
i-value to @EntryCreated on the new value) would appear less crude.
R.
>
> 1/ is easy, but do you think 2/ could be added in 9.2?
>
> Thank you,
> Thomas
>
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.o
On 10/10/2017 11:08 AM, Thomas SEGISMONT wrote:
>
>
> 2017-10-09 18:30 GMT+02:00 Radim Vansa <rva...@redhat.com
> <mailto:rva...@redhat.com>>:
>
> On 10/09/2017 03:04 PM, Thomas SEGISMONT wrote:
> > Hi,
> >
> > I've created a b
> Thanks,
> Sebastian
>
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinis
us. Checking CI failures should apply to ALL PRs.
> [On Ice] PR should be closed and reopened when relevant again.
>
> Comments/suggestions ?
>
> Tristan
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev ma
On 12/01/2017 10:04 AM, Radim Vansa wrote:
> On 12/01/2017 09:26 AM, Tristan Tarrant wrote:
>> Hello people,
>>
>> I'd like to rationalize the PR labels because I believe some of them are
>> useless:
>>
>> [Ready for review] - Any PR without the [Preview]
lists.jboss.org
> <mailto:infinispan-dev@lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> _______
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org <mailto:infinispan-dev@lists.jboss.org>
> https://lists.jbo
; infinispan-dev@lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>> ___
>> infinispan-dev mailing list
>> infinispan-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-d
of allowed users
>
> Cheers,
> Galder
>
>
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Radim Vansa <rva...@redhat.com>
>
> In which case the client will need to compute the hash before it can
> hint the network layer were to connect to.
>
> Thanks,
> Sanne
>
>> On 05/30/2018 02:47 PM, Radim Vansa wrote:
>>> On 05/30/2018 12:46 PM, Adrian Nistor wrote:
>>>> Thanks for cl
fit in a grpc architecture?
>>>>
>>>> Thank you
>>>> Vittorio
>>>>
>>>> [1] https://github.com/rigazilla/ispn-grpc
>>>> [2] https://github.com/rigazilla/ispn-grpc/issues
>>>>
>>>> --
>>
stening for that and in the other case we should
still drop the connection.
Radim
>
> Cheers
>
> On Mon, Jun 25, 2018 at 2:47 PM Radim Vansa <mailto:rva...@redhat.com>> wrote:
>
> You mean that the writes are executed by the Netty thread instead of
> r
/concurrent/locks/impl/DefaultLockManager.java#L115
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
somehow distinguishable from the 'online' ones?
Given all the non-reliability with listeners failover I don't think this
is needed, but I'll rather check in the crowd.
Radim
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinisp
suggest the Intrinsics.
Radim
On 08/20/2018 02:43 PM, Galder Zamarreno wrote:
> Header is just one part of the operation. Individual operation
> parameters, like version in replaceWithVersion are not logged
>
> On Tue, Aug 14, 2018 at 6:22 PM Radim Vansa <mailto:rva...@red
ss.org>
> > https://lists.jboss.org/mailman/listinfo/infinispan-dev
> >
>
> --
> Bela Ban | http://www.jgroups.org
>
> ___
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org <
t;>
>> Here's our XML config:
>> https://github.com/vert-x3/vertx-infinispan/blob/ispn92/src/main/resources/default-infinispan.xml
>>
>> Does that ring a bell? Do you need more info?
>>
>> Regards,
>> Thomas
>>
>>
>>
>&
9.2.1.Final next
> week.
>
>
> [1] https://github.com/infinispan/infinispan/pull/5746
> [2] https://github.com/infinispan/infinispan/pull/5803
--
Radim Vansa <rva...@redhat.com>
JBoss Performance Team
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
On 12/12/2018 03:30 PM, Sebastian Laskawiec wrote:
> On Tue, Dec 11, 2018 at 11:13 AM Radim Vansa <mailto:rva...@redhat.com>> wrote:
>
> I dislike having any logic based on the port number in some range;
> it's
> not common that behaviour would change
osed on different
> port (like ) or Hot Rod exposed on port that starts with 8.
>
> What do you think about such simplification?
>
> Thanks,
> Sebastian
>
>
>
>
> _______
> infinispan-d
On 12/14/2018 11:49 AM, Sebastian Laskawiec wrote:
>
>
> On Thu, Dec 13, 2018 at 4:42 PM Radim Vansa <mailto:rva...@redhat.com>> wrote:
>
> Hey Sebastian,
>
> I am sorry that you took my comment about errors between chair and
> keyboard completely wro
erz/infinispan/commit/2934e0b3e8ab9af5fb1471c5fdbb0716e5a11c31
> [2]
>
> https://github.com/infinispan/infinispan/blob/master/hibernate/cache-v53/src/main/java/org/infinispan/hibernate/cache/v53/impl/Sync.java
>
--
Radim Vansa
JBoss Performance Team
301 - 361 of 361 matches
Mail list logo
