April 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5332) Make sure the Query API exposes IndexReader(s) in some way

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5332?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5332: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated. Thanks [~sannegrinovero]! > Make sure the Query API exposes IndexReader(s) in some way > ---------------------------------------------------------- > > Key: ISPN-5332 > URL: https://issues.jboss.org/browse/ISPN-5332 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 7.2.0.CR1 > > > Referring to the mailing list thread "Grouping lucene query on Infinispan", since we're planning to remove method {{org.infinispan.query.SearchManager.getSearchFactory()}}, and alternative should be provider at least to access IndexReader. > Note that the plan to remove this had good reasons: to abstract the user from the indexes and so make sure we could have different types of underlying indexes.. so this would need to be exposed at best in form of "advanced API", and clarify the restrictions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5346) QueryInterceptor::shouldRemove is too strict

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5346?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5346: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > QueryInterceptor::shouldRemove is too strict > -------------------------------------------- > > Key: ISPN-5346 > URL: https://issues.jboss.org/browse/ISPN-5346 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Ales Justin > Assignee: Gustavo Fernandes > Fix For: 7.2.0.CR1 > > > http://lists.jboss.org/pipermail/hibernate-dev/2015-April/012474.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5346) QueryInterceptor::shouldRemove is too strict

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5346?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5346: ------------------------------------ Status: Pull Request Sent (was: Open) > QueryInterceptor::shouldRemove is too strict > -------------------------------------------- > > Key: ISPN-5346 > URL: https://issues.jboss.org/browse/ISPN-5346 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Ales Justin > Assignee: Gustavo Fernandes > Fix For: 7.2.0.CR1 > > > http://lists.jboss.org/pipermail/hibernate-dev/2015-April/012474.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5346) QueryInterceptor::shouldRemove is too strict

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5346?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5346: ------------------------------------ Status: Open (was: New) > QueryInterceptor::shouldRemove is too strict > -------------------------------------------- > > Key: ISPN-5346 > URL: https://issues.jboss.org/browse/ISPN-5346 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Ales Justin > Assignee: Gustavo Fernandes > Fix For: 7.2.0.CR1 > > > http://lists.jboss.org/pipermail/hibernate-dev/2015-April/012474.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5085) Convert REST server to using RESTEasy's Netty container integration

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5085?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-5085: ---------------------------------------- Promising work so far, basic tests working with {code}resteasy-netty4{code} artifact, but upgrade to Resteasy 3.0.10 needed to get around an issue with empty content length when sending back empty responses. > Convert REST server to using RESTEasy's Netty container integration > ------------------------------------------------------------------- > > Key: ISPN-5085 > URL: https://issues.jboss.org/browse/ISPN-5085 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Fix For: 7.2.0.CR1, 7.2.0.Final > > > REST server is currently based on RESTEasy which relies on having a web container underneath to do its job. So, we're depending on jbossweb/undertow to provide the container capabilities. Instead, we should switch to a Netty based container to better control our dependencies. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5085) Convert REST server to using RESTEasy's Netty container integration

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5085?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5085: ----------------------------------- Status: Open (was: New) > Convert REST server to using RESTEasy's Netty container integration > ------------------------------------------------------------------- > > Key: ISPN-5085 > URL: https://issues.jboss.org/browse/ISPN-5085 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Fix For: 7.2.0.CR1, 7.2.0.Final > > > REST server is currently based on RESTEasy which relies on having a web container underneath to do its job. So, we're depending on jbossweb/undertow to provide the container capabilities. Instead, we should switch to a Netty based container to better control our dependencies. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5085) Convert REST server to using RESTEasy's Netty container integration

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5085?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-5085: -------------------------------------- Assignee: Galder Zamarreño > Convert REST server to using RESTEasy's Netty container integration > ------------------------------------------------------------------- > > Key: ISPN-5085 > URL: https://issues.jboss.org/browse/ISPN-5085 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.2.0.CR1, 7.2.0.Final > > > REST server is currently based on RESTEasy which relies on having a web container underneath to do its job. So, we're depending on jbossweb/undertow to provide the container capabilities. Instead, we should switch to a Netty based container to better control our dependencies. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5085) Convert REST server to using RESTEasy's Netty container integration

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5085?page=com.atlassian.jira.plugin.... ] Galder Zamarreño edited comment on ISPN-5085 at 4/7/15 11:10 AM: ----------------------------------------------------------------- Promising work so far, basic tests working with `resteasy-netty4` artifact, but upgrade to Resteasy 3.0.10 needed to get around an issue with empty content length when sending back empty responses. was (Author: galder.zamarreno): Promising work so far, basic tests working with {code}resteasy-netty4{code} artifact, but upgrade to Resteasy 3.0.10 needed to get around an issue with empty content length when sending back empty responses. > Convert REST server to using RESTEasy's Netty container integration > ------------------------------------------------------------------- > > Key: ISPN-5085 > URL: https://issues.jboss.org/browse/ISPN-5085 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.2.0.CR1, 7.2.0.Final > > > REST server is currently based on RESTEasy which relies on having a web container underneath to do its job. So, we're depending on jbossweb/undertow to provide the container capabilities. Instead, we should switch to a Netty based container to better control our dependencies. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5346) QueryInterceptor::shouldRemove is too strict

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5346?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-5346: --------------------------------------- Assignee: Gustavo Fernandes (was: Sanne Grinovero) > QueryInterceptor::shouldRemove is too strict > -------------------------------------------- > > Key: ISPN-5346 > URL: https://issues.jboss.org/browse/ISPN-5346 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Ales Justin > Assignee: Gustavo Fernandes > Fix For: 7.2.0.CR1 > > > http://lists.jboss.org/pipermail/hibernate-dev/2015-April/012474.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5354) HotRod putAll send proper CH routing

by William Burns (JIRA)

William Burns created ISPN-5354: ----------------------------------- Summary: HotRod putAll send proper CH routing Key: ISPN-5354 URL: https://issues.jboss.org/browse/ISPN-5354 Project: Infinispan Issue Type: Enhancement Components: Remote Protocols Reporter: William Burns We need to enable putAll operation on hot rod to send multiple commands where each owner receives the keys it owns. This way the embedded server has less routing to do. This requires having some sort of thread pool for use on the client though, as doing each request sequentially seems it would probably be slower than just sending 1 request. This relates to ISPN-5266 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2015