November 2015 - infinispan-issues

[JBoss JIRA] (ISPRK-16) Support connecting to secured Infinispan servers

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-16?page=com.atlassian.jira.plugin.s... ] Gustavo Fernandes updated ISPRK-16: ----------------------------------- Affects Version/s: 0.1 > Support connecting to secured Infinispan servers > ------------------------------------------------ > > Key: ISPRK-16 > URL: https://issues.jboss.org/browse/ISPRK-16 > Project: Infinispan Spark > Issue Type: Feature Request > Affects Versions: 0.1 > Reporter: Gustavo Fernandes > > Security configuration would be custom credentials, key/trust stores, sasl configurations and others -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-16) Support connecting to secured Infinispan servers

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-16?page=com.atlassian.jira.plugin.s... ] Gustavo Fernandes updated ISPRK-16: ----------------------------------- Component/s: RDD SQL Streaming > Support connecting to secured Infinispan servers > ------------------------------------------------ > > Key: ISPRK-16 > URL: https://issues.jboss.org/browse/ISPRK-16 > Project: Infinispan Spark > Issue Type: Feature Request > Components: RDD, SQL, Streaming > Affects Versions: 0.1 > Reporter: Gustavo Fernandes > > Security configuration would be custom credentials, key/trust stores, sasl configurations and others -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-16) Support connecting to secured Infinispan servers

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPRK-16: -------------------------------------- Summary: Support connecting to secured Infinispan servers Key: ISPRK-16 URL: https://issues.jboss.org/browse/ISPRK-16 Project: Infinispan Spark Issue Type: Feature Request Reporter: Gustavo Fernandes Security configuration would be custom credentials, key/trust stores, sasl configurations and others -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-3) Infinispan Query DSL from my Spark application

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-3?page=com.atlassian.jira.plugin.sy... ] Gustavo Fernandes updated ISPRK-3: ---------------------------------- Status: Open (was: New) > Infinispan Query DSL from my Spark application > ---------------------------------------------- > > Key: ISPRK-3 > URL: https://issues.jboss.org/browse/ISPRK-3 > Project: Infinispan Spark > Issue Type: Feature Request > Components: RDD > Reporter: Pedro Zapata > Assignee: Gustavo Fernandes > Labels: jdg7 > > As an application developer, I want to use Infinispan Query DSL from my Spark application written in Java. > Once Java is supported, Scala can be supported as well, no extra effort required -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-3) Infinispan Query DSL from my Spark application

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-3?page=com.atlassian.jira.plugin.sy... ] Gustavo Fernandes updated ISPRK-3: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-spark/pull/13 > Infinispan Query DSL from my Spark application > ---------------------------------------------- > > Key: ISPRK-3 > URL: https://issues.jboss.org/browse/ISPRK-3 > Project: Infinispan Spark > Issue Type: Feature Request > Components: RDD > Reporter: Pedro Zapata > Assignee: Gustavo Fernandes > Labels: jdg7 > > As an application developer, I want to use Infinispan Query DSL from my Spark application written in Java. > Once Java is supported, Scala can be supported as well, no extra effort required -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5860) ComponentRegistry should cache the VersionGenerator in a field

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5860?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5860: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1272390|https://bugzilla.redhat.com/show_bug.cgi?id=1272390] from ON_QA to VERIFIED > ComponentRegistry should cache the VersionGenerator in a field > -------------------------------------------------------------- > > Key: ISPN-5860 > URL: https://issues.jboss.org/browse/ISPN-5860 > Project: Infinispan > Issue Type: Bug > Components: Core, Server > Affects Versions: 8.0.1.Final, 8.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Alpha2, 8.1.0.Final > > > The {{VersionGenerator}} component is read by the HotRod server for each write operation, and we can optimize it by caching the component in a field. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5859) HotRod server should not use privileged actions for common stuff

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5859?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5859: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1272390|https://bugzilla.redhat.com/show_bug.cgi?id=1272390] from ON_QA to VERIFIED > HotRod server should not use privileged actions for common stuff > ---------------------------------------------------------------- > > Key: ISPN-5859 > URL: https://issues.jboss.org/browse/ISPN-5859 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.0.1.Final, 8.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Alpha2, 8.1.0.Final > > > The HotRod server uses privileged actions to perform operations that are needed for each request, like reading the cache mode to decide what kind (if any) topology update to send to the client. Since privileged actions use thread-locals, we should try to avoid them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5858) ValueMatcher and AvailabilityMode should have externalizers

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5858?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5858: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1272390|https://bugzilla.redhat.com/show_bug.cgi?id=1272390] from ON_QA to VERIFIED > ValueMatcher and AvailabilityMode should have externalizers > ----------------------------------------------------------- > > Key: ISPN-5858 > URL: https://issues.jboss.org/browse/ISPN-5858 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.0.1.Final, 8.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Alpha2, 8.1.0.CR1 > > > The default enum serialization is pretty bad, it writes both the enum name and value name as strings. > {{ValueMatcher}} is needed in each write command, so we should optimize it. > {{AvailabilityMode}} doesn't matter that much, except when the coordinator changes, and the new coordinator has to retrieve the status of all the caches on all the nodes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5857) HotRod client should use the consistent hash in replicated mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5857?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5857: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1272390|https://bugzilla.redhat.com/show_bug.cgi?id=1272390] from ON_QA to VERIFIED > HotRod client should use the consistent hash in replicated mode > --------------------------------------------------------------- > > Key: ISPN-5857 > URL: https://issues.jboss.org/browse/ISPN-5857 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.0.1.Final, 8.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: hotrod > Fix For: 8.1.0.Alpha2, 8.1.0.Final > > > The HotRod server assumes that in replicated mode the server accessed by the client doesn't matter, so it doesn't send a consistent hash in the topology updates. > However, since replicated mode is now implemented on top of distributed mode, hitting the primary owner or another node makes a big difference. We should change the server to send the consistent hash for replicated caches as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5958) Functional Listeners modified inconsistency

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-5958: -------------------------------------- Summary: Functional Listeners modified inconsistency Key: ISPN-5958 URL: https://issues.jboss.org/browse/ISPN-5958 Project: Infinispan Issue Type: Bug Affects Versions: 8.1.0.Beta1, 8.0.1.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño When an entry is modified and a RW listener is registered, you can get output like this: {code} [node2-event] modified, before: Optional[multi1-value-cluster] [node2-event] modified, after: Optional[new-multi1-value-cluster] [node1-event] modified, before: Optional.empty [node1-event] modified, after: Optional[new-multi1-value-cluster] {code} This is not right, if node1's going to print the event, it needs to have all information. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2015