[JBoss JIRA] (ISPN-9963) Restructure Documentation Titles
by Don Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-9963?page=com.atlassian.jira.plugin.... ]
Don Naro updated ISPN-9963:
---------------------------
Description:
Restructure the layout of the documentation directory and set up new titles. Part 1 to adopt flexible customer content.
The goal is to have a buildable set of titles created from existing content. The current chapter files from ISPN 9.x books are moved into the /topics directory where they can be divided into sections and topics (discrete units of reusable information).
Also requires changes to the docs layout on the community website.
was:
This enhancement is to restructure the layout of the documentation directory and set up the titles for the 10.0 community release.
The goal is to have a buildable set of titles created from existing content. The current chapter files from ISPN 9.x books are moved into the /topics directory where they can start to be broken down into sections and smaller units of reusable information.
Definition of done for this issue:
- Community and productized titles build successfully.
- Community website updated to handle new titles.
> Restructure Documentation Titles
> --------------------------------
>
> Key: ISPN-9963
> URL: https://issues.jboss.org/browse/ISPN-9963
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Core
> Reporter: Don Naro
> Assignee: Don Naro
> Priority: Major
>
> Restructure the layout of the documentation directory and set up new titles. Part 1 to adopt flexible customer content.
> The goal is to have a buildable set of titles created from existing content. The current chapter files from ISPN 9.x books are moved into the /topics directory where they can be divided into sections and topics (discrete units of reusable information).
> Also requires changes to the docs layout on the community website.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (ISPN-9963) Restructure Documentation Titles
by Don Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-9963?page=com.atlassian.jira.plugin.... ]
Don Naro updated ISPN-9963:
---------------------------
Affects Version/s: (was: 10.0.0.Beta1)
> Restructure Documentation Titles
> --------------------------------
>
> Key: ISPN-9963
> URL: https://issues.jboss.org/browse/ISPN-9963
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Core
> Reporter: Don Naro
> Assignee: Don Naro
> Priority: Major
>
> This enhancement is to restructure the layout of the documentation directory and set up the titles for the 10.0 community release.
> The goal is to have a buildable set of titles created from existing content. The current chapter files from ISPN 9.x books are moved into the /topics directory where they can start to be broken down into sections and smaller units of reusable information.
> Definition of done for this issue:
> - Community and productized titles build successfully.
> - Community website updated to handle new titles.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (ISPN-10014) Deprecate Key2StringMapper
by Dan Berindei (Jira)
Dan Berindei created ISPN-10014:
-----------------------------------
Summary: Deprecate Key2StringMapper
Key: ISPN-10014
URL: https://issues.jboss.org/browse/ISPN-10014
Project: Infinispan
Issue Type: Bug
Components: Configuration, Core, Loaders and Stores
Affects Versions: 10.0.0.Beta2, 9.4.8.Final
Reporter: Dan Berindei
ISPN-3471 is still valid: {{Key2StringMapper}} is too low-level, as it has to deal with user objects or {{WrappedByteArray}} depending on the memory configuration.
For the vast majority of cases, a key mapper implementation that uses the same marshalling for the keys as for the values should be good enough. It may also use base64 encoding for databases that don't have a `VARBINARY` equivalent, but I'm not sure there are any.
The only use case I see for a custom {{Key2StringMapper}} and a {{VARCHAR}} key column is for external tools to look at the database directly, but we never supported that.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months