January 2021 - infinispan-issues - Jboss List Archives

[Red Hat JIRA] (ISPN-11986) Resolve unqualified type names in queries

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11986?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11986: ----------------------------------- Fix Version/s: 12.1.0.Final (was: 12.0.0.Final) > Resolve unqualified type names in queries > ----------------------------------------- > > Key: ISPN-11986 > URL: https://issues.redhat.com/browse/ISPN-11986 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Labels: SearchNG > Fix For: 12.1.0.Final > > > When type names are known in advance (indexed cache) we should be able to resolve non-FQN name in queries. We should allow such queries if the name can be resolved unambiguously. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-11850) Only a subset of server tests work with driver=CONTAINER

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11850?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11850: ----------------------------------- Fix Version/s: 12.1.0.Final (was: 12.0.0.Final) > Only a subset of server tests work with driver=CONTAINER > -------------------------------------------------------- > > Key: ISPN-11850 > URL: https://issues.redhat.com/browse/ISPN-11850 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite > Affects Versions: 11.0.0.Dev05 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.1.0.Final > > > Several of the {{server/tests}} are not executed when the container driver is set, i.e.{{-Dorg.infinispan.test.server.driver=CONTAINER}}. Furthermore, many of the tests when executed do not work as expected with this driver. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12396) Deprecate org.infinispan.commons.dataconversion.Encoder

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12396?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12396: ----------------------------------- Fix Version/s: 12.1.0.Final (was: 12.0.0.Final) > Deprecate org.infinispan.commons.dataconversion.Encoder > ------------------------------------------------------- > > Key: ISPN-12396 > URL: https://issues.redhat.com/browse/ISPN-12396 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 12.0.0.Dev04 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 12.1.0.Final > > > Encoders are not exposed to remote clients, not used internally anymore and their functionality overlap with Transcoders -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12113) HTTP authentication with only Digest SHA mechanisms fails

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12113?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12113: ----------------------------------- Fix Version/s: 12.1.0.Final (was: 12.0.0.Final) > HTTP authentication with only Digest SHA mechanisms fails > --------------------------------------------------------- > > Key: ISPN-12113 > URL: https://issues.redhat.com/browse/ISPN-12113 > Project: Infinispan > Issue Type: Bug > Reporter: Francisco De Melo Junior > Assignee: Francisco De Melo Junior > Priority: Minor > Labels: authentication, encryption, rest > Fix For: 12.1.0.Final > > > {code:xml} > <cache-container name="clustered" default-cache="sessionCache" statistics="true"> > <transport stack="tcp-stack" site="z9" cluster="clustered" node-name="rhdgserver" /> > <security> > <authorization> > <identity-role-mapper /> > <role name="admin" permissions="ALL" /> > <role name="reader" permissions="READ" /> > <role name="writer" permissions="WRITE" /> > </authorization> > </security> > <metrics gauges="true" histograms="true" /> > </cache-container> > (...) > <endpoints socket-binding="default" security-realm="default"> > <hotrod-connector name="hotrod"> > <authentication> > <sasl server-name="rhdgserver" mechanisms="DIGEST-SHA-256" qop="auth" /> > </authentication> > </hotrod-connector> > <rest-connector name="rest"> > <authentication mechanisms="DIGEST-SHA-256"/> > </rest-connector> > </endpoints> > {code} -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12037) JUnit-friendly replacement for MultipleCacheManagerTest

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12037?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12037: ----------------------------------- Fix Version/s: 12.1.0.Final (was: 12.0.0.Final) > JUnit-friendly replacement for MultipleCacheManagerTest > ------------------------------------------------------- > > Key: ISPN-12037 > URL: https://issues.redhat.com/browse/ISPN-12037 > Project: Infinispan > Issue Type: Task > Components: Core, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.1.0.Final > > > Core tests that need one more more cache managers extend either {{SingleCacheManagerTest}} or {{MultipleCacheManagersTest}}. Many other modules' tests do the same for convenience. > We would like to eventually move all modules to JUnit, and having an alternative to MCMT that can be used from either JUnit or TestNG and can support an incremental migration is the first step. > The starting plan is for a {{TestCluster}} class for building and interacting with clusters including features from MCMT/TestingUtil/TestCacheManagerFactory/BasePartitionHandlingTest. > Assertions like {{assertLocked()}}, {{assertIsInL1()}} etc. would be in separate classes, ideally with AssertJ-like {{assertThat}} static methods. > -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12051) REST Client URI support

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12051?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12051: ----------------------------------- Fix Version/s: 12.1.0.Final (was: 12.0.0.Final) > REST Client URI support > ----------------------- > > Key: ISPN-12051 > URL: https://issues.redhat.com/browse/ISPN-12051 > Project: Infinispan > Issue Type: Enhancement > Components: REST > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.1.0.Final > > > This should be as close as possible to ISPN-11960 -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12115) CacheContainerAdmin should allow defining configurations

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12115?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12115: ----------------------------------- Fix Version/s: 12.1.0.Final (was: 12.0.0.Final) > CacheContainerAdmin should allow defining configurations > -------------------------------------------------------- > > Key: ISPN-12115 > URL: https://issues.redhat.com/browse/ISPN-12115 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Hot Rod, Server > Affects Versions: 11.0.1.Final > Reporter: Dan Berindei > Priority: Major > Fix For: 12.1.0.Final > > > {{EmbeddedCacheManagerAdmin}} and {{RemoteCacheManagerAdmin}} allow creating a cache with a complete configuration or with an existing configuration template. > It should be possible to define a configuration (template?) without a cache, so users/applications can define a common configuration and then reference it by name. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12048) Improve Cross-Site statistics

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12048?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12048: ----------------------------------- Fix Version/s: 12.1.0.Final (was: 12.0.0.Final) > Improve Cross-Site statistics > ----------------------------- > > Key: ISPN-12048 > URL: https://issues.redhat.com/browse/ISPN-12048 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 11.0.0.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 12.1.0.Final > > > Improve the cross-site statistics by adding a per-cache/site pair. Example: > * sender site > ** Cache_A > *** Site_b (min/avg/max rtt, nr_requests_sent) > ** Cache_B > *** Site_b (min/avg/max rtt, nr_requests_sent) > *** Site_c (min/avg/max rtt, nr_requests_sent) > * Receiver site > ** Cache_C > *** Site_a (nr_requests_received) > *** Site_c (nr_requests_received) -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-11993) Allow automatic registration of Protobuf schemas and marshallers

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11993?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11993: ----------------------------------- Fix Version/s: 12.1.0.Final (was: 12.0.0.Final) > Allow automatic registration of Protobuf schemas and marshallers > ---------------------------------------------------------------- > > Key: ISPN-11993 > URL: https://issues.redhat.com/browse/ISPN-11993 > Project: Infinispan > Issue Type: Feature Request > Components: Hot Rod, Marshalling > Affects Versions: 11.0.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.1.0.Final > > > Currently it's necessary for users to automatically add {{SerializationContextIntializer}} instances to the client via {{addContextInitializers}} and for .proto files to be registered like so: > {code:java} > Path proto = Paths.get(Query.class.getClassLoader().getResource("proto/sheep.proto").toURI()); > cacheManager.getCache(ProtobufMetadataManagerConstants.PROTOBUF_METADATA_CACHE_NAME).put("sheep.proto", Files.readString(proto)); > {code} > Instead we should allow users to configure the client so that: > # {{SerializationContextInitalizer}} services are automatically registerd if {{builder.autoAddAllContextInitializers()}} is configured. > # {{*.proto}} files on the classpath and in available {{SerializationContextInitializers}} are automatically registered with the server if {{.autoRegisterSchemas()}} is configured. > ProtoStreams {{AutoProtoSchemaBuilder}} already provides a `service` attribute to generate the service files for {{SerializationContextInitiailizer}}, however this is false by default. We should update this to true so that users have one less knob to confgure. > NOTE: {{autoRegisterSchemas()}} will fail if authorization is enabled and the client does not have the ___schema_manager role. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12114) Server defaults and embeddedd defaults should be the same

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12114?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12114: ----------------------------------- Fix Version/s: 12.1.0.Final (was: 12.0.0.Final) > Server defaults and embeddedd defaults should be the same > --------------------------------------------------------- > > Key: ISPN-12114 > URL: https://issues.redhat.com/browse/ISPN-12114 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.1.0.Final > > > The server has an {{infinispan-defaults.xml}} file with some configuration templates that are available by default in the server and are automatically applied to all the caches defined in the server configuration XML. > These configuration templates change e.g. the lock acquisition timeout and state transfer timeout to match the old WildFly server's defaults, but these default values are not documented. > {{EmbeddedCacheManagerAdmin}} and {{RemoteCacheManagerAdmin}} also mention "the configuration marked as default on the container/server", but we don't really have that any more, as the default cache's configuration is no longer used as a template. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2021