August 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9659) Document the Docker image and how to use it in Kubernetes/OpenShift

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9659?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9659: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Document the Docker image and how to use it in Kubernetes/OpenShift > ------------------------------------------------------------------- > > Key: ISPN-9659 > URL: https://issues.jboss.org/browse/ISPN-9659 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Priority: Major > > Expand/modernize https://blog.infinispan.org/2016/08/running-infinispan-cluster-on-kuberne... and push it to the main docs. > Also document how to run the simple tutorials against this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9498) Index filesystem paths in server should point to data directory

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9498?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9498: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Index filesystem paths in server should point to data directory > --------------------------------------------------------------- > > Key: ISPN-9498 > URL: https://issues.jboss.org/browse/ISPN-9498 > Project: Infinispan > Issue Type: Bug > Components: Indexing, OpenShift, Server > Affects Versions: 9.4.0.CR1, 9.3.3.Final > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > Priority: Major > > Certain indexing configurations result in using filesystem as index storage. > When running such configurations in a server environment, filesystem path should be somewhere within the server's data directory. This is the natural place for such data. > When running in OpenShift, server's data folder can be backed by a persistent volume. This means that the fileystem volume survives after restarts. > Plugging server's data directory is already happening for [file-store|https://github.com/infinispan/infinispan/blob/master/server/in...] and [rocksdb-store|https://github.com/infinispan/infinispan/blob/master/server...]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9960) JavaDocs cleanups

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9960?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9960: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31) > JavaDocs cleanups > ----------------- > > Key: ISPN-9960 > URL: https://issues.jboss.org/browse/ISPN-9960 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1 > > > The JavaDocs contain several broken entities (espcially > < and variations) as well as a number of broken links/sees (caused by prior refactorings). -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9946) ServerNG

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9946?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9946: ---------------------------------- Sprint: DataGrid Sprint #29, DataGrid Sprint #31, DataGrid Sprint #32 (was: DataGrid Sprint #29, DataGrid Sprint #31) > ServerNG > -------- > > Key: ISPN-9946 > URL: https://issues.jboss.org/browse/ISPN-9946 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9976) Query still has a hard dependency on Elasticsearch

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9976?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9976: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Query still has a hard dependency on Elasticsearch > -------------------------------------------------- > > Key: ISPN-9976 > URL: https://issues.jboss.org/browse/ISPN-9976 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1 > > > ISPN-9795 Made the {{org.hibernate.search.elasticsearch}} module optional in our feature-packs, however in `infinispan-query`there is an unchecked call to {{org.hibernate.search.elasticsearch.bridge.builtin.impl.ElasticsearchDateBridge}} regardless of whether Elasticsearch is actually available on the classpath. This results in a {{NoClassDefFoundError}} whenever {{HibernateSearchPropertyHelper#convertToPropertyType}} is called and Elasticsearch is not available. For example when deploying the wfly-modules to a wfly instance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9893) New Reactive API

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9893?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9893: ---------------------------------- Sprint: DataGrid Sprint #29, DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32 (was: DataGrid Sprint #29, DataGrid Sprint #30, DataGrid Sprint #31) > New Reactive API > ---------------- > > Key: ISPN-9893 > URL: https://issues.jboss.org/browse/ISPN-9893 > Project: Infinispan > Issue Type: Enhancement > Components: API > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > See sub-talks. This is an umbrella issue -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9865) Query is failing if custom classes are used inside of the cache

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9865?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9865: ---------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32 (was: DataGrid Sprint #31) > Query is failing if custom classes are used inside of the cache > --------------------------------------------------------------- > > Key: ISPN-9865 > URL: https://issues.jboss.org/browse/ISPN-9865 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, WildFly modules > Affects Versions: 9.4.5.Final > Environment: Wildfly server with ISPN modules and ISPN subsystem to configure caches > Reporter: Wolf-Dieter Fink > Assignee: Nistor Adrian > Priority: Major > Attachments: install1-standalone-local.cli, install2-standalone-local.cli > > > A simple query for a cache which contains User classes will fail for queries with the error below. > UserData class for the cache: > public class Test implements Serializable { > private int testId; > public Test(){} > public Test(int myId) {this.testId = myId;} > public int getTestId() {return animalId;} > public void setTestId(int testId) { this.testId = testId;} > } > Simple EJB for test > @Singleton > @Startup > public class TestInfinispanQuery4EAPConfig { > @Resource(lookup = "java:jboss/datagrid-infinispan/container/jdg-container/cache/EAPcache") > private Cache<String, Object> cache; > > @PostConstruct > public void LoadDBToMemory() { > cache.put("1", new Test(2, 0)); > cache.put("2", new Test(2, 0)); > cache.put("3", new Test(1, 0)); > QueryFactory queryFactory = Search.getQueryFactory(cache); > > Query q = queryFactory.from(Test.class).having("testId").eq(2).build(); > > int size = q.getResultSize(); > System.out.println("result = " + size); > } > } > Caused by: java.lang.IllegalStateException: ISPN028510: Unknown entity name org.infinispan.wfink.web.Test > at org.infinispan.objectfilter.impl.syntax.parser.QueryResolverDelegateImpl.registerPersisterSpace(QueryResolverDelegateImpl.java:60) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.entityName(QueryResolver.java:6683) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.persisterSpaceRoot(QueryResolver.java:1302) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.persisterSpace(QueryResolver.java:1203) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.persisterSpaces(QueryResolver.java:1144) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.fromClause(QueryResolver.java:1060) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.selectFrom(QueryResolver.java:969) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.querySpec(QueryResolver.java:487) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.queryStatement(QueryResolver.java:388) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.queryStatementSet(QueryResolver.java:308) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.statement(QueryResolver.java:241) > at org.infinispan.objectfilter.impl.ql.QueryParser.resolve(QueryParser.java:81) > at org.infinispan.objectfilter.impl.ql.QueryParser.parseQuery(QueryParser.java:69) > at org.infinispan.objectfilter.impl.syntax.parser.IckleParser.parse(IckleParser.java:19) > at org.infinispan.query.dsl.embedded.impl.QueryEngine.lambda$parse$1(QueryEngine.java:695) > at org.infinispan.query.dsl.embedded.impl.QueryCache.lambda$get$ab3121d1$1(QueryCache.java:73) > at org.infinispan.compat.FunctionMapper.apply(FunctionMapper.java:40) > at org.infinispan.commands.write.ComputeIfAbsentCommand.perform(ComputeIfAbsentCommand.java:104) > at org.infinispan.interceptors.impl.CallInterceptor.visitCommand(CallInterceptor.java:29) > at org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextThenAccept(BaseAsyncInterceptor.java:100) > at org.infinispan.interceptors.impl.EntryWrappingInterceptor.setSkipRemoteGetsAndInvokeNextForDataCommand(EntryWrappingInterceptor.java:672) -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-106) OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/IPROTO-106?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated IPROTO-106: ----------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32 (was: DataGrid Sprint #31) > OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar > ------------------------------------------------------------------------------------------------------ > > Key: IPROTO-106 > URL: https://issues.jboss.org/browse/IPROTO-106 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9 > > > The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome. > This is already leading to failures in Infinispan https://ci.infinispan.org/job/Infinispan/job/master/1304/consoleFull#1277... -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-105) Accept annotated 'getters' that are not named according to the javabeans standard

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/IPROTO-105?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated IPROTO-105: ----------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32 (was: DataGrid Sprint #31) > Accept annotated 'getters' that are not named according to the javabeans standard > --------------------------------------------------------------------------------- > > Key: IPROTO-105 > URL: https://issues.jboss.org/browse/IPROTO-105 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9, 4.3.0.Final > > > While 'getLifespan()' is an accepted getter for 'lifespan' property, 'lifespan()' is not, but it would be very useful to add support for this case, also for such setter. > See infinispan's EmbeddedLifespanExpirableMetadata -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10161) ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10161?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10161: ----------------------------------- Sprint: DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32 (was: DataGrid Sprint #30, DataGrid Sprint #31) > ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports > ------------------------------------------------------------------------------ > > Key: ISPN-10161 > URL: https://issues.jboss.org/browse/ISPN-10161 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.12.Final, 10.0.0.Final > Reporter: Diego Lovison > Assignee: Dan Berindei > Priority: Critical > > When we have Leaked threads we are throwing a new RuntimeException that is preventing the next listener to be running. > From `master` execute `rm -rf hibernate/cache-v51/target/surefire-reports/ && rm -rf hibernate/cache-v53/target/surefire-reports/ && mvn verify -pl hibernate/cache-v51,hibernate/cache-v53 -Dtest=MultiTenancyTest -fae` > After that, check the hibernate/cache-v53/target/surefire-reports/ folder, you will see no reports there. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2019