April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6464) Possibility to get black (login) background in all console pages

by Martin Vrabel (JIRA)

[ https://issues.jboss.org/browse/ISPN-6464?page=com.atlassian.jira.plugin.... ] Martin Vrabel updated ISPN-6464: -------------------------------- Summary: Possibility to get black (login) background in all console pages (was: Possibility to get back (login) background in all console pages ) > Possibility to get black (login) background in all console pages > ----------------------------------------------------------------- > > Key: ISPN-6464 > URL: https://issues.jboss.org/browse/ISPN-6464 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > > Way to reproduce: > 1. Log into console: > 2. press back button (pic. 1 , navbar should not be shown ) > 3. press forward button (background from this point on is the same as at login) > !https://drive.google.com/open?id=0B2kBhkKzkRIlTkV1eldad2pRUkE! > !https://drive.google.com/open?id=0B2kBhkKzkRIlR0dUTGgwMHhNdkk! > !https://drive.google.com/open?id=0B2kBhkKzkRIleWVjYUc5UDBZcFE! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6430) Remote Queries do not allow per-entity index configurations

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6430?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-6430: ------------------------------------- Hibernate Search will drop dynamic factory reconfiguration sooner or later. So we'll have to do without it. I'm wondering how are they supporting dynamic entities. We'll have to use that too. > Remote Queries do not allow per-entity index configurations > ----------------------------------------------------------- > > Key: ISPN-6430 > URL: https://issues.jboss.org/browse/ISPN-6430 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Reporter: Gustavo Fernandes > > When using Infinispan in library mode, it's possible to define a per-entity index configuration, so this is possible: > {code:java} > cacheCfg.indexing().index(Index.ALL) > .addIndexedEntity(Car.class) > .addIndexedEntity(Person.class) > .addProperty("hibernate.search.person.directory_provider", "ram") > .addProperty("hibernate.search.car.indexmanager","org.infinispan.query.indexmanager.InfinispanIndexManager") > {code} > Different entities can live in different indexes, with a complete different storage and index manager. > Since when using remote queries there is a synthetic entity being created, this capability is lost. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6458) DistTopKeyTest.testLockLockFailed random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6458?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6458: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > DistTopKeyTest.testLockLockFailed random failures > ------------------------------------------------- > > Key: ISPN-6458 > URL: https://issues.jboss.org/browse/ISPN-6458 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.2.0.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.0.0.Alpha1 > > > Random failures due to the async nature of the top key collection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6430) Remote Queries do not allow per-entity index configurations

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6430?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-6430: ----------------------------------------- bq. I'm not against it but we should find a good reason to have it. One reason would be symmetry: library mode config when transposed to server behaves differently at the moment (see forum reference). Other reason would be performance. What if one indexed cache has only a handful of entries and other index cache millions? bq. and this spares us from the problems generated by creating indexes dynamically. We'll have to declare all indexed protobuf types at startup Right, that would be necessary if one wishes to control config on a per index basis. Hibernate Search by default names indexes using the class name of the entity, I'm wondering if it'd be possible to do something similar when indexing protobuf entities, i.e., take the type name and pass it to hibernate search. > Remote Queries do not allow per-entity index configurations > ----------------------------------------------------------- > > Key: ISPN-6430 > URL: https://issues.jboss.org/browse/ISPN-6430 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Reporter: Gustavo Fernandes > > When using Infinispan in library mode, it's possible to define a per-entity index configuration, so this is possible: > {code:java} > cacheCfg.indexing().index(Index.ALL) > .addIndexedEntity(Car.class) > .addIndexedEntity(Person.class) > .addProperty("hibernate.search.person.directory_provider", "ram") > .addProperty("hibernate.search.car.indexmanager","org.infinispan.query.indexmanager.InfinispanIndexManager") > {code} > Different entities can live in different indexes, with a complete different storage and index manager. > Since when using remote queries there is a synthetic entity being created, this capability is lost. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6463) Enable Checkstyle run during the build

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6463?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6463: -------------------------------------- Status: Open (was: New) > Enable Checkstyle run during the build > -------------------------------------- > > Key: ISPN-6463 > URL: https://issues.jboss.org/browse/ISPN-6463 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Trivial > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6463) Enable Checkstyle run during the build

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6463?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6463: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4210 > Enable Checkstyle run during the build > -------------------------------------- > > Key: ISPN-6463 > URL: https://issues.jboss.org/browse/ISPN-6463 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Trivial > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6463) Enable Checkstyle run during the build

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6463?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-6463: ----------------------------------------- Assignee: Sebastian Łaskawiec > Enable Checkstyle run during the build > -------------------------------------- > > Key: ISPN-6463 > URL: https://issues.jboss.org/browse/ISPN-6463 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Trivial > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6463) Enable Checkstyle run during the build

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6463: ----------------------------------------- Summary: Enable Checkstyle run during the build Key: ISPN-6463 URL: https://issues.jboss.org/browse/ISPN-6463 Project: Infinispan Issue Type: Enhancement Reporter: Sebastian Łaskawiec Priority: Trivial -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6445) PreloadingWithWriteBehindTest.testIfCanLoadKeysConcurrently random failures

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6445?page=com.atlassian.jira.plugin.... ] Work on ISPN-6445 started by Gustavo Fernandes. ----------------------------------------------- > PreloadingWithWriteBehindTest.testIfCanLoadKeysConcurrently random failures > --------------------------------------------------------------------------- > > Key: ISPN-6445 > URL: https://issues.jboss.org/browse/ISPN-6445 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Gustavo Fernandes > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Alpha1, 9.0.0.Final > > > The test assumes that the {{AdvancedAsyncCacheLoader.size()}} is accurate, but the implementation actually ignores the in-memory changes and just delegates to the real loader's {{size()}}. > Also, the method doesn't really belong in this test, because it doesn't use preloading. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6445) PreloadingWithWriteBehindTest.testIfCanLoadKeysConcurrently random failures

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6445?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes resolved ISPN-6445. ------------------------------------- Resolution: Done > PreloadingWithWriteBehindTest.testIfCanLoadKeysConcurrently random failures > --------------------------------------------------------------------------- > > Key: ISPN-6445 > URL: https://issues.jboss.org/browse/ISPN-6445 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Gustavo Fernandes > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Alpha1, 9.0.0.Final > > > The test assumes that the {{AdvancedAsyncCacheLoader.size()}} is accurate, but the implementation actually ignores the in-memory changes and just delegates to the real loader's {{size()}}. > Also, the method doesn't really belong in this test, because it doesn't use preloading. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2016