[JBoss JIRA] (ISPN-10452) Remove AsElementAttributeSerializer
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-10452?page=com.atlassian.jira.plugin... ]
Gustavo Fernandes updated ISPN-10452:
-------------------------------------
Description:
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) classes, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON Object rather than a field (property name/value pair) inside a JSON object.
Sometimes it's not always clear what will be the …
[View More]rendered JSON when attributes can be objects and vice-versa, so JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes.
was:
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON Object rather than a field (property name/value pair) inside a JSON object.
Sometimes it's not always clear what will be the rendered JSON when attributes can be objects and vice-versa, so JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes.
> Remove AsElementAttributeSerializer
> -----------------------------------
>
> Key: ISPN-10452
> URL: https://issues.jboss.org/browse/ISPN-10452
> Project: Infinispan
> Issue Type: Bug
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) classes, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON Object rather than a field (property name/value pair) inside a JSON object.
> Sometimes it's not always clear what will be the rendered JSON when attributes can be objects and vice-versa, so JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
5 years, 8 months
[JBoss JIRA] (ISPN-10452) Remove AsElementAttributeSerializer
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-10452?page=com.atlassian.jira.plugin... ]
Work on ISPN-10452 started by Gustavo Fernandes.
------------------------------------------------
> Remove AsElementAttributeSerializer
> -----------------------------------
>
> Key: ISPN-10452
> URL: https://issues.jboss.org/browse/ISPN-10452
> Project: Infinispan
> Issue Type: Bug
> Reporter: Gustavo Fernandes
> …
[View More] Assignee: Gustavo Fernandes
> Priority: Major
>
> The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON Object rather than a field (property name/value pair) inside a JSON object.
> Sometimes it's not always clear what will be the rendered JSON when attributes can be objects and vice-versa, so JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
5 years, 8 months
[JBoss JIRA] (ISPN-10452) Remove AsElementAttributeSerializer
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-10452?page=com.atlassian.jira.plugin... ]
Gustavo Fernandes updated ISPN-10452:
-------------------------------------
Description:
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON Object rather than a field (property name/value pair) inside a JSON object.
Sometimes it's not always clear what will be the …
[View More]rendered JSON when attributes can be objects and vice-versa, so JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes.
was:
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON object rather than a field inside a JSON object.
For the sake of simplicity and less mental gymnastics, JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes collections.
> Remove AsElementAttributeSerializer
> -----------------------------------
>
> Key: ISPN-10452
> URL: https://issues.jboss.org/browse/ISPN-10452
> Project: Infinispan
> Issue Type: Bug
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON Object rather than a field (property name/value pair) inside a JSON object.
> Sometimes it's not always clear what will be the rendered JSON when attributes can be objects and vice-versa, so JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
5 years, 8 months
[JBoss JIRA] (ISPN-10452) Remove AsElementAttributeSerializer
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-10452?page=com.atlassian.jira.plugin... ]
Gustavo Fernandes updated ISPN-10452:
-------------------------------------
Description:
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON object rather than a field inside a JSON object.
For the sake of simplicity and less mental gymnastics, JSON objects should be …
[View More]generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes collections.
was:
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON object rather than a field inside an object.
For the sake of simplicity and less mental gymnastics, JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes collections.
> Remove AsElementAttributeSerializer
> -----------------------------------
>
> Key: ISPN-10452
> URL: https://issues.jboss.org/browse/ISPN-10452
> Project: Infinispan
> Issue Type: Bug
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON object rather than a field inside a JSON object.
> For the sake of simplicity and less mental gymnastics, JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes collections.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
5 years, 8 months
[JBoss JIRA] (ISPN-10452) Remove AsElementAttributeSerializer
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-10452?page=com.atlassian.jira.plugin... ]
Gustavo Fernandes updated ISPN-10452:
-------------------------------------
Status: Open (was: New)
> Remove AsElementAttributeSerializer
> -----------------------------------
>
> Key: ISPN-10452
> URL: https://issues.jboss.org/browse/ISPN-10452
> Project: Infinispan
> Issue Type: Bug
> Reporter: Gustavo Fernandes
> …
[View More] Assignee: Gustavo Fernandes
> Priority: Major
>
> The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON object rather than a field inside an object.
> For the sake of simplicity and less mental gymnastics, JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes collections.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
5 years, 8 months
[JBoss JIRA] (ISPN-10453) RocksDB ReadOptions memory leak
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-10453:
-----------------------------------
Summary: RocksDB ReadOptions memory leak
Key: ISPN-10453
URL: https://issues.jboss.org/browse/ISPN-10453
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 10.0.0.Beta4, 9.4.15.Final
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 10.0.0.Beta5, 9.4.16.Final
…
[View More]Currently our rocksdb store impl creates a new ReadOptions instance per iterator created. As per the RocksDB we should be calling {{dispose()}} on this once it goes out of scope, so that the c++ underlying impl can free the memory. Currently we're not doing this, resulting in a memory leak.
As we only ever use the same ReadOptions for all iterators, we should simply re-use a singleton for all iterators and then dispose of this on shutdown.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
5 years, 8 months
[JBoss JIRA] (ISPN-10452) Remove AsElementAttributeSerializer
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-10452?page=com.atlassian.jira.plugin... ]
Gustavo Fernandes updated ISPN-10452:
-------------------------------------
Description:
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON object rather than a fields inside an object.
For the sake of simplicity and less mental gymnastics, JSON objects should be …
[View More]generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes collections.
was:
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON object.
For the sake of simplicity and less mental gymnastics, JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes collections.
> Remove AsElementAttributeSerializer
> -----------------------------------
>
> Key: ISPN-10452
> URL: https://issues.jboss.org/browse/ISPN-10452
> Project: Infinispan
> Issue Type: Bug
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON object rather than a fields inside an object.
> For the sake of simplicity and less mental gymnastics, JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes collections.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
5 years, 8 months
[JBoss JIRA] (ISPN-10452) Remove AsElementAttributeSerializer
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-10452?page=com.atlassian.jira.plugin... ]
Gustavo Fernandes updated ISPN-10452:
-------------------------------------
Description:
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON object rather than a field inside an object.
For the sake of simplicity and less mental gymnastics, JSON objects should be …
[View More]generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes collections.
was:
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON object rather than a fields inside an object.
For the sake of simplicity and less mental gymnastics, JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes collections.
> Remove AsElementAttributeSerializer
> -----------------------------------
>
> Key: ISPN-10452
> URL: https://issues.jboss.org/browse/ISPN-10452
> Project: Infinispan
> Issue Type: Bug
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> The JSON rendering currently is based on inspecting Attributes in Configuration(Builder) class, and it's also possible to plug-in an AttributeSerializer that will emit the Attribute as a JSON object rather than a field inside an object.
> For the sake of simplicity and less mental gymnastics, JSON objects should be generated from Configuration objects and JSON fields should be generated from the Configuration's Attributes collections.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
5 years, 8 months