[
https://issues.apache.org/jira/browse/IGNITE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-946:
-------------------------------
Comment: was deleted
(was: Valentin, several questions/thoughts so far cause the task is not fully
clear for now.
1) Do you mean {{GridCacheVersionedEntry}} interface under "versioned entry"?
This interface is implemented by two classes that are used by DR only.
If you mean this interface, then I would better introduce another interface
{{VersionedEntry}} that will have only those methods that should be in public
API.
{{GridCacheVersionedEntry}} is kind of DR-oriented mess.
{{GridCacheVersionedEntry}} will extend {{VersionedEntry}} and will be kept
internal.
2) From your description I see that it will be useful to make version
information public. Why do we need to make {{GridCacheVersionedEntry}} public
then? Why can't we make {{GridCacheVersion}} public instead?
My design view is the following:
- adding {{CacheVersion}} class that will have the same public API methods as
{{GridCacheVersion}} has excluding DR-oriented. {{GridCacheVersion}} will
extend {{CacheVersion}};
- adding, if needed, {{VersionedEntry}} that will return {{CacheVersion}}.
{{GridCacheVersionedEntry}} should be refactored cause in reality it's a DR
cache entry version.
Thoughts?
)
> Need to expose versioned cache entry to public API
> --------------------------------------------------
>
> Key: IGNITE-946
> URL: https://issues.apache.org/jira/browse/IGNITE-946
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: sprint-4
> Reporter: Valentin Kulichenko
> Assignee: Denis Magda
> Priority: Critical
> Labels: Usability
>
> Currently we have versioned entry, but it's not available on public API, but
> knowing version can be useful in some cases. Need to make it accessible via
> {{unwrap}} method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
