March 2015 - infinispan-issues - Jboss List Archives

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

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5332?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5332: ---------------------------------- Status: Open (was: New) > 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.Beta2 > > > 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)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5333) Delete methods which have long been deprecated in Infinispan Query

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5333?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5333: ---------------------------------- Priority: Blocker (was: Major) > Delete methods which have long been deprecated in Infinispan Query > ------------------------------------------------------------------ > > Key: ISPN-5333 > URL: https://issues.jboss.org/browse/ISPN-5333 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Sanne Grinovero > Priority: Blocker > Fix For: 8.0.0.Final > > > For example: > - {{org.infinispan.query.SearchManager.getQueryFactory()}} > - {{org.infinispan.query.SearchManager.getSearchFactory()}} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5333) Delete methods which have long been deprecated in Infinispan Query

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-5333: ------------------------------------- Summary: Delete methods which have long been deprecated in Infinispan Query Key: ISPN-5333 URL: https://issues.jboss.org/browse/ISPN-5333 Project: Infinispan Issue Type: Enhancement Components: Embedded Querying Reporter: Sanne Grinovero Fix For: 8.0.0.Final For example: - {{org.infinispan.query.SearchManager.getQueryFactory()}} - {{org.infinispan.query.SearchManager.getSearchFactory()}} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

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

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5332?page=com.atlassian.jira.plugin.... ] Sanne Grinovero reassigned ISPN-5332: ------------------------------------- Assignee: Sanne Grinovero (was: Gustavo Fernandes) > 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.Beta2 > > > 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)

10 years, 6 months

1
0
0 / 0

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

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5332?page=com.atlassian.jira.plugin.... ] Sanne Grinovero reassigned ISPN-5332: ------------------------------------- Assignee: Gustavo Fernandes > 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: Gustavo Fernandes > Fix For: 7.2.0.Beta2 > > > 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)

10 years, 6 months

1
0
0 / 0

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

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5332?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5332: ---------------------------------- Fix Version/s: 7.2.0.Beta2 > 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 > Fix For: 7.2.0.Beta2 > > > 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)

10 years, 6 months

1
0
0 / 0

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

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-5332: ------------------------------------- Summary: 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 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)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5264) Optimize PutAll operations (library mode)

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5264?page=com.atlassian.jira.plugin.... ] William Burns reassigned ISPN-5264: ----------------------------------- Assignee: William Burns > Optimize PutAll operations (library mode) > ----------------------------------------- > > Key: ISPN-5264 > URL: https://issues.jboss.org/browse/ISPN-5264 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Zapata > Assignee: William Burns > > - PutAll: to ensure that users can load massive amount of data into the grid quickly, both in Library mode and over Hot Rod. > - Performance improvement over large data sets. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5264) Optimize PutAll operations (library mode)

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5264?page=com.atlassian.jira.plugin.... ] Work on ISPN-5264 started by William Burns. ------------------------------------------- > Optimize PutAll operations (library mode) > ----------------------------------------- > > Key: ISPN-5264 > URL: https://issues.jboss.org/browse/ISPN-5264 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Zapata > Assignee: William Burns > > - PutAll: to ensure that users can load massive amount of data into the grid quickly, both in Library mode and over Hot Rod. > - Performance improvement over large data sets. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2183) Add the ability to fetch a set of keys at once (getAll)

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-2183?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-2183: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3344 > Add the ability to fetch a set of keys at once (getAll) > ------------------------------------------------------- > > Key: ISPN-2183 > URL: https://issues.jboss.org/browse/ISPN-2183 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Mircea Markus > Assignee: William Burns > Priority: Minor > Labels: 64QueryBlockers > > When a transaction knows in advance about the set of keys it needs to read, this cache.getAll(k1,k2,..kn) method can bring a some performance improvement: > 1. all the keys can be fetched from remote nodes in parallel > 2. keys that map to the same node can be grouped and fetched in the same RPC request > > Note that 1. can be be achieved even at this time by using Cache.getAsync(K) method - that's not as elegant though as it requires the user to write the code the code that waits on the Future objects that are returned. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2015