[JBoss JIRA] (ISPN-10463) Server uses disabled features
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10463?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10463:
-----------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33 (was: DataGrid Sprint #32)
> Server uses disabled features
> -----------------------------
>
> Key: ISPN-10463
> URL: https://issues.jboss.org/browse/ISPN-10463
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Server
> Affects Versions: 10.0.0.Beta4, 9.4.15.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.CR1, 9.4.17.Final
>
>
> Some Infinispan features are disabled in the product, e.g. data segmentation.
> This is done with a file META-INF/infinispan-features.properties added by the productization script in infinispan-commons:
> org.infinispan.feature.data-segmentation=false
> The properties file is read and the feature is disabled in library mode, but somehow the server doesn't find the properties file and the feature is enabled.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ISPN-10465) Duplicate Jgroups stack causes erroneous warning
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10465?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10465:
-----------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33 (was: DataGrid Sprint #32)
> Duplicate Jgroups stack causes erroneous warning
> ------------------------------------------------
>
> Key: ISPN-10465
> URL: https://issues.jboss.org/browse/ISPN-10465
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Server
> Affects Versions: 10.0.0.Beta5
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> If a {{<stack-file ../>}} is specified with the same name as an existing stack, then the resulting error message indicates that the stack file cannot be found instead of relaying that a duplicate stack exists.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ISPN-10480) Docs: Attributes to remove symlinks
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10480?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10480:
-----------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33 (was: DataGrid Sprint #32)
> Docs: Attributes to remove symlinks
> -----------------------------------
>
> Key: ISPN-10480
> URL: https://issues.jboss.org/browse/ISPN-10480
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Core
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> This task removes some files for simplicity and adds attributes to get around the need for symlinks in downstream source for RH docs tooling.
> No need to have both stories.adoc and topics.adoc for each title.
> Add attributes for community and product:
> * :images_dir: resolves to the images directory. For community, images are in the same directory as the main asciidoc file. For product, need to symlink images in the directory for master.adoc.
> * :stories: resolves to the directory that contains assembly files. Community this is ../../stories. Product is a symlink to the stories directory.
> * :topics: resolves to the directory that contains adoc topic files. Community this is ../../topics. Product is a symlink to the topics directory.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ISPN-10418) java.lang.UnsupportedOperationException: FieldDescriptor.getDefaultValue() called on an embedded message field (only scalars can have a default value)
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10418?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10418:
-----------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: DataGrid Sprint #31, DataGrid Sprint #32)
> java.lang.UnsupportedOperationException: FieldDescriptor.getDefaultValue() called on an embedded message field (only scalars can have a default value)
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-10418
> URL: https://issues.jboss.org/browse/ISPN-10418
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 10.0.0.Beta4
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.Beta5
>
>
> This started to happen after upgrading to protostream 4.3 which introduces some asserts in FieldDescriptor.getDefaultValue() with the recently fixed IPROTO-80.
> This happens mainly due to IndexingTagHandler.indexMissingFields calling getDefaultValue() regardless of the type.
> {code}
> org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=686 returned server error (status=0x85): org.infinispan.remoting.RemoteException: ISPN000217: Received exception from RemoteContinuousQueryTest-NodeD-22902, see cause for remote stack trace
> org.hibernate.search.bridge.BridgeException: Exception while calling bridge#set
> entity class: org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper
> field bridge: org.infinispan.query.remote.impl.indexing.ProtobufValueWrapperFieldBridge@1b9bf39c
> java.lang.UnsupportedOperationException: FieldDescriptor.getDefaultValue() called on an embedded message field (only scalars can have a default value).
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:340)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:177)
> at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:138)
> at org.infinispan.client.hotrod.impl.transport.netty.HintedReplayingDecoder.callDecode(HintedReplayingDecoder.java:94)
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:278)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ISPN-10419) RocksDB purge should not utilise ArrayList to store multiple expired keys
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10419?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10419:
-----------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: DataGrid Sprint #31, DataGrid Sprint #32)
> RocksDB purge should not utilise ArrayList to store multiple expired keys
> -------------------------------------------------------------------------
>
> Key: ISPN-10419
> URL: https://issues.jboss.org/browse/ISPN-10419
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Beta4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> Currently the RocksDB purge method stores multiple keys that expire at the same time in a ArrayList associated with the expiry time. This is currently marshallable because ArrayList is serializable and we utilise Jboss-marshalling, however ISPN-10354 means this is no longer possible in embedded mode when `infinispan-jboss-marshalling` is not present. Therefore, we should create a `ExpiryBucket` that can be marshalled via the persistence marshaller i.e. protobuf based.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ISPN-10422) Deprecate MediaType::parse in favour of MediaType::fromString
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10422?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10422:
-----------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: DataGrid Sprint #31, DataGrid Sprint #32)
> Deprecate MediaType::parse in favour of MediaType::fromString
> -------------------------------------------------------------
>
> Key: ISPN-10422
> URL: https://issues.jboss.org/browse/ISPN-10422
> Project: Infinispan
> Issue Type: Enhancement
> Components: API
> Affects Versions: 10.0.0.Beta4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta5
>
>
> Currently {{org.infinispan.commons.dataconversion.MediaType}} exposes both {{fromString}} and {{parse}} methods to create an instance from a String. We should deprecate the latter in favour of the former and update all internal code references.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months