October 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4488) Verify performance impact of Lucene 4 and checksumming logic in the Lucene Directory

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4488?page=com.atlassian.jira.plugin.... ] Sanne Grinovero resolved ISPN-4488. ----------------------------------- Resolution: Done This is done, there doesn't seem to be any measurable impact. > Verify performance impact of Lucene 4 and checksumming logic in the Lucene Directory > ------------------------------------------------------------------------------------ > > Key: ISPN-4488 > URL: https://issues.jboss.org/browse/ISPN-4488 > Project: Infinispan > Issue Type: Task > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 7.0.0.CR2 > > > We recently moved to Lucene 4, and also the Lucene Directory is now wrapping output to allow to calculate checksums. > Before going Final we need to verify the performance impact, QA mentioned a significant regression compared to Lucene v3 w/o checksums. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4488) Verify performance impact of Lucene 4 and checksumming logic in the Lucene Directory

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4488?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-4488: ---------------------------------- Fix Version/s: (was: 7.0.0.CR2) > Verify performance impact of Lucene 4 and checksumming logic in the Lucene Directory > ------------------------------------------------------------------------------------ > > Key: ISPN-4488 > URL: https://issues.jboss.org/browse/ISPN-4488 > Project: Infinispan > Issue Type: Task > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > > We recently moved to Lucene 4, and also the Lucene Directory is now wrapping output to allow to calculate checksums. > Before going Final we need to verify the performance impact, QA mentioned a significant regression compared to Lucene v3 w/o checksums. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4488) Verify performance impact of Lucene 4 and checksumming logic in the Lucene Directory

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4488?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-4488: ---------------------------------- Fix Version/s: 7.0.0.CR2 > Verify performance impact of Lucene 4 and checksumming logic in the Lucene Directory > ------------------------------------------------------------------------------------ > > Key: ISPN-4488 > URL: https://issues.jboss.org/browse/ISPN-4488 > Project: Infinispan > Issue Type: Task > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 7.0.0.CR2 > > > We recently moved to Lucene 4, and also the Lucene Directory is now wrapping output to allow to calculate checksums. > Before going Final we need to verify the performance impact, QA mentioned a significant regression compared to Lucene v3 w/o checksums. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2826) CacheQuery.list() returns List<Object>, which is hard to cast

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2826?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-2826: ---------------------------------- Fix Version/s: (was: 7.0.0.CR2) > CacheQuery.list() returns List<Object>, which is hard to cast > ------------------------------------------------------------- > > Key: ISPN-2826 > URL: https://issues.jboss.org/browse/ISPN-2826 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Ray Tsang > Assignee: Sanne Grinovero > Priority: Minor > > In example for Books in https://docs.jboss.org/author/display/ISPN/Querying+Infinispan > ~~ snip snip ~~ > CacheQuery query = searchManager.getQuery(luceneQuery, Book.class); > // and there are your results! > List<Book> objectList = query.list(); > ~~ snip snip ~~ > This doesn't actually work. CacheQuery.list() returns List<Object> > Thus, you will need to cast: List<Book> books = (List<Book>) cq.list(); > But this wouldn't work... Instead you'll end up doing: List<Book> books = (List<Book>)(List<?>) cq.list(); -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2141) Better configuration options for Infinispan Query

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2141?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2141: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Better configuration options for Infinispan Query > ------------------------------------------------- > > Key: ISPN-2141 > URL: https://issues.jboss.org/browse/ISPN-2141 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 7.0.0.CR2 > > > Rethink the configuration options for Query. > See also https://community.jboss.org/wiki/InfinispanQuery-DesignAndPlanning -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2342) Cross-Site Replication: State Transfer between sites

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2342?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2342: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Cross-Site Replication: State Transfer between sites > ---------------------------------------------------- > > Key: ISPN-2342 > URL: https://issues.jboss.org/browse/ISPN-2342 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Affects Versions: 6.0.1.Final > Reporter: Erik Salter > Assignee: Pedro Ruivo > Labels: roadmap > Fix For: 7.0.0.CR2, 7.0.0.Final > > > To bring up a new site or recover a failed site, I need an inter-site state transfer mechanism for synchronizing keys. > Note that initially, this should a manual process that is invoked on one site to one of its configured backups. > This should be based on the non-blocking state transfer mechanism for consistency. > The pseudo-design may look similar to the following: > - Manually invokable, background thread > - Since the bridge end is open, there are writes happening to keys. Keep track of the puts/removes on the main data owner. > - Iterate through the key set. > - If the key has already been modified since the process started, discard. > - Else synchronously write the key value in a TX context -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2324) Add user documentation for NSBT

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2324?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2324: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Add user documentation for NSBT > -------------------------------- > > Key: ISPN-2324 > URL: https://issues.jboss.org/browse/ISPN-2324 > Project: Infinispan > Issue Type: Feature Request > Components: Documentation-Core > Affects Versions: 5.2.0.Alpha3 > Reporter: Mircea Markus > Assignee: Dan Berindei > Labels: documentation > Fix For: 7.0.0.CR2 > > > To be linked from the user guide page:https://docs.jboss.org/author/display/ISPN/User+Guide -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2528) Verify and document Query functionality with programmatically defined indexes

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2528?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2528: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Verify and document Query functionality with programmatically defined indexes > ----------------------------------------------------------------------------- > > Key: ISPN-2528 > URL: https://issues.jboss.org/browse/ISPN-2528 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Fix For: 7.0.0.CR2 > > > Hibernate Search supports programmatic configuration of indexes, we should add some tests in Infinispan Query to verify the looks of such an API and if it works. > Then document it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2577) Silence SuspectExceptions

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2577?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2577: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Silence SuspectExceptions > ------------------------- > > Key: ISPN-2577 > URL: https://issues.jboss.org/browse/ISPN-2577 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.2.0.Beta4, 6.0.0.Final > Reporter: Michal Linhard > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.0.0.CR2, 7.0.0.Final > > > There are lots of SuspectExceptions in resilience test run: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... > We managed to keep these under cover for 5.1.x branch. > This is of course a cosmetic problem, but it polutes the log with unnecessary ERRORs. > Parsed logs here: > http://www.qa.jboss.com/~mlinhard/test_results/run54-parsed/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2820) POST request with multipart/form-data encoding stores wrong content type

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2820?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2820: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > POST request with multipart/form-data encoding stores wrong content type > ------------------------------------------------------------------------ > > Key: ISPN-2820 > URL: https://issues.jboss.org/browse/ISPN-2820 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 5.2.1.Final > Reporter: Dan Berindei > Assignee: Tristan Tarrant > Fix For: 7.0.0.CR2 > > > The REST server uses the {{Content-Type}} header of the POST request to determine the content type of the stored entry. But with {{Content-Type: multipart/form-data}}, each parameter can have its own content type (and {{multipart/form-data}} is definitely not any parameter's content type). > This seems to be the way to do get the content type of each parameter: http://www.mkyong.com/webservices/jax-rs/file-upload-example-in-resteasy/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 October 2014